# Migration path from Artifactory to NXRM3
**URL:** https://community.sonatype.com/t/migration-path-from-artifactory-to-nxrm3/2989
**Category:** Sonatype Nexus Repository
**Tags:** nxrm3, artifactory, migrate
**Created:** [November 20, 2019, 3:24pm UTC](https://community.sonatype.com/t/migration-path-from-artifactory-to-nxrm3/2989 "2019-11-20T15:24:08Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@richard.fedoriuk](https://community.sonatype.com/u/richard.fedoriuk)
#### Post date: [November 20, 2019, 3:24pm UTC](https://community.sonatype.com/t/migration-path-from-artifactory-to-nxrm3/2989/1 "2019-11-20T15:24:08Z")
Hello, I’m currently working on migrating Artifactory 6.11 to NXRM3. There is a doc outlining the migration path from Nexus-2, however I can’t seem to find anything wrt migrating to NXRM3.
At this point I’m looking into simply manually (via API) uploading artifacts from Artifactory into similarly-named _readonly_ repos in NXRM3. A new repo structure will be created in NXRM3 going forward for new work.
I’d appreciate hearing from anyone who’s tried this migration before, or any suggestions anyone can offer.
Thanks,
- Richard
---
### Author:  [@fcremer](https://community.sonatype.com/u/fcremer)
#### Post date: [November 20, 2019, 3:47pm UTC](https://community.sonatype.com/t/migration-path-from-artifactory-to-nxrm3/2989/2 "2019-11-20T15:47:40Z")
Hi Richard,
I think you are on the right track. The first thing I recommend is to differentiate between dependencies and applications.
When it comes to dependencies, I also recommend differentiating between internally developed dependencies and public, open source ones.
For public, open source ones, you can simply create proxy repositories in Nexus to point to public registries like Central, NPM, etc… and for internally developed dependencies, you can create proxy repositories that point to your Artifactory instance. As builds ask for these components through Nexus, it should start caching these artifacts in Nexus.
For your applications, since these are not dependencies and can’t be called by a build, the API upload is probably your best option. Check out the examples in the below URL:
> [@Nexus Repository - Artifact Import Scripts](http://community.sonatype.com/t/nexus-repository-artifact-import-scripts/1254):
>
> How do I use it? Wut does it do? Imports artifacts into a Nexus Repository 3 Maven2, NuGet or npm hosted repo. Wut does it not do? Literally anything else. You want security? Better set it up yourself. How do I use it? Maven cd rootdirectorywithallyourartifacts ./mavenimport.sh -u admin -p admin123 -r [http://localhost:8084/repository/maven-releases/](http://localhost:8084/repository/maven-releases/) Watch a bunch of verbose output from curl If need be, change -u to user, -p to password, and -r (I bet you’ll have to change this) to the repo…