# Workflow for pulling data added to project using dvc import
**URL:** https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078
**Category:** Questions
**Created:** [May 7, 2024, 4:31pm UTC](https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078 "2024-05-07T16:31:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@lusk](https://discuss.dvc.org/u/lusk)
#### Post date: [May 7, 2024, 4:31pm UTC](https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078/1 "2024-05-07T16:31:44Z")
Hi all, I’m having trouble wrapping my head around how to combine `dvc import` and `dvc pull`.
I have two DVC projects. One project is a **registry** , and the other project is a separate, standalone project that relies on some data in the **registry**. Let’s call this **project**.
On **Computer A** , I used `dvc import` to import some data from **registry** into **project**. **registry** and **project** do not share a cache, so the imported data was then copied into **project** ’s cache. I also created some DVC pipeline stages, ran them, and the outputs were checked into DVC as well.
I then added a DVC Google Cloud Storage remote and ran `dvc push` from **Computer A** to push the data to the cloud. I also pushed the code and all DVC-related files to my git remote.
On **Computer B** I pulled the code (`git pull`) and then attempted to `dvc pull`. It pulled the outputs of the pipeline stages, but not the data that I had imported to **project** from **registry** on **Computer A**.
Am I missing a part of the puzzle here? I expected this combination of `git push` + `dvc push` from **Computer A** along with `git pull` and `dvc pull` on **Computer B** to enable me to relatively seamlessly replicate the project across machines, but that doesn’t seem to be the case. Should I have added the **registry** data to **project** using `dvc get` instead of `dvc import`? Is there a way to ensure that data added using `dvc import` is also able to be pulled to other machines in the future?
---
### Author:  [@gregstarr](https://discuss.dvc.org/u/gregstarr)
#### Post date: [May 7, 2024, 7:24pm UTC](https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078/2 "2024-05-07T19:24:32Z")
`dvc import` should create a `xyz.dvc` file right? Is this file in git and pulled to computer B?
---
### Author:  [@lusk](https://discuss.dvc.org/u/lusk)
#### Post date: [May 7, 2024, 9:22pm UTC](https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078/3 "2024-05-07T21:22:52Z")
Yes, but it seems like the issue is that the `repo` defined in the `.dvc` files points to the **registry** on the same filesystem of **Computer A**. I suppose that the solution was probably to import the files from the **registry** Github URL as opposed to directly from the local folder, or to set multiple remotes for those files such that they could be specified when pulling the data later…
---
### Author:  [@dberenbaum](https://discuss.dvc.org/u/dberenbaum)
#### Post date: [May 8, 2024, 12:20pm UTC](https://discuss.dvc.org/t/workflow-for-pulling-data-added-to-project-using-dvc-import/2078/4 "2024-05-08T12:20:16Z")
`dvc pull` should pull imported data as well, although it will try to pull it from the **registry** remote rather than make another copy of it on **project** remote. Take a look at [example-get-started/data/data.xml.dvc at main · iterative/example-get-started · GitHub](https://github.com/iterative/example-get-started/blob/main/data/data.xml.dvc). This is an import from [GitHub - iterative/dataset-registry: Dataset registry DVC project](https://github.com/iterative/dataset-registry). If you clone [GitHub - iterative/example-get-started: Get started DVC project (NLP, random forest)](https://github.com/iterative/example-get-started) and do `dvc pull`, you will see that it pulls the imported data.
> I suppose that the solution was probably to import the files from the **registry** Github URL as opposed to directly from the local folder
Yes, this could be the issue. **Computer B** also needs to be able to access the URL you used in `dvc import`.