Overview
RepoFlow can automatically migrate supported repositories from Artifactory. This guide covers the built-in migration flow, the legacy RepoFlow CLI option, validation, cutover, and decommissioning.
Automatic migration in RepoFlow
RepoFlow now includes automatic repository migration in the product. For new migrations, use the guided RepoFlow migration flow to connect Artifactory, select the repositories you want to move, and track the transfer from RepoFlow.
Supported package types
Automatic migration from Artifactory currently supports:
- npm
- PyPI
- Maven (maven2)
- NuGet
- Go
- Helm
- Docker
- RPM (yum)
- Gems (rubygems)
- Cargo
npm 
PyPI 
Maven (maven2) '%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 
Docker 
RPM (yum) 
Gems (rubygems) 
Cargo Open RepoFlow to start a migration
Legacy RepoFlow CLI migration tool
The standalone RepoFlow CLI migration tool remains available for existing scripts and CLI-based workflows. It is the legacy option. Use automatic migration in RepoFlow for new migrations when possible.
The legacy CLI migration flow supports these package types from Artifactory:
- npm
- PyPI
- Maven (maven2)
- NuGet
- Go
- Helm
- RPM (yum)
Open legacy RepoFlow CLI migration docs
Need help with another package type or a complex repository layout? Contact us or email hello@repoflow.io.
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 automatic migration in RepoFlow. If you have an existing CLI workflow, you can continue using the legacy tool.
- 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.