Overview
This guide gives you a clear Artifactory migration plan with early validation, a short cutover window, client updates, and the RepoFlow CLI migration flow for the transfer step.
RepoFlow CLI migration supported package types
The RepoFlow CLI migration flow currently supports migrating these package types from Artifactory:
- npm
- PyPI
- Maven
- NuGet
- Go
- Helm
- RPM
npm
PyPI
Maven'%3e%3cpath%20fill-rule='evenodd'%20clip-rule='evenodd'%20d='M7.99608%206.54145C7.99608%207.39349%207.32496%208.0836%206.49804%208.0836C5.67037%208.0836%205%207.39349%205%206.54145C5%205.69018%205.67037%204.9993%206.49804%204.9993C7.32496%204.9993%207.99608%205.69018%207.99608%206.54145Z'%20fill='%23004880'%20/%3e%3c/g%3e%3c/svg%3e){kind=icon}
NuGet
Go
Helm
RPMNeed help migrating a different package type? Contact us and we can help you migrate, or provide a custom migration script. You can also email hello@repoflow.io.
Open RepoFlow CLI migration docs
Why migrate to RepoFlow
RepoFlow gives you one platform for package types, proxy caching, and flexible cloud or self-hosted deployment, with more details on the features page
Migration steps
- Audit what you have: Inventory local, remote, and virtual repositories, then list the build jobs and tools that use each endpoint.
- Design the target layout in RepoFlow: Create the repositories you need in RepoFlow and decide how clients should consume them, including whether you want to proxy upstream registries with remote repositories.
- Pick a dry run target: Choose a smaller repo that still represents real usage, then migrate it with the RepoFlow CLI migration flow.
- Validate with a real build: Point one CI job at RepoFlow, run a clean build, and confirm dependency resolution and auth behave as expected.
- Cut over with a short write freeze: Pause publishing to Artifactory for a defined window, run the final sync, then switch CI and developer endpoints to RepoFlow.
- Monitor and decommission: Keep Artifactory read only until you are confident, then archive and retire it safely.