Overview
RepoFlow can automatically migrate supported repositories from Nexus Repository 3. 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 Nexus 3, select the repositories you want to move, and track the transfer from RepoFlow.
Supported package types
Automatic migration from Nexus 3 currently supports:
- npm
- PyPI
- Maven (maven2)
- NuGet
- Cargo
- Go
- Helm
- Docker
- RPM (yum)
- Gems (rubygems)
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 
Cargo 
Go 
Helm 
Docker 
RPM (yum) 
Gems (rubygems) 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 Nexus 3:
- npm
- PyPI
- Maven (maven2)
- Go
- Helm
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 repositories and endpoints: Inventory hosted, proxy, and group repositories, then map them to the teams and CI pipelines that use them.
- Design the target layout in RepoFlow: Create local, remote, and virtual repositories that match your intended structure and decide how clients should consume them.
- Dry run a representative repo: Migrate a smaller repo first using automatic migration in RepoFlow, then validate with a clean build in CI. Existing CLI workflows can continue using the legacy tool.
- Plan the cutover window: Choose a short window to freeze publishing during the final sync, and communicate the timing to teams.
- Cut over and validate: Run the final sync, update CI and developer endpoints, then run your validation pipelines.
- Monitor and decommission: Keep Nexus read only while you watch for missing package and auth issues, then retire it safely.