Overview
RepoFlow can automatically migrate supported repositories from Nexus Repository 2. 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 2, select the repositories you want to move, and track the transfer from RepoFlow.
Supported package types
Automatic migration from Nexus 2 currently supports:
- npm
- Maven (maven2)
- NuGet
- Gems (rubygems)
npm 
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 
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 2:
- npm
- Maven (maven2)
- NuGet
- Gems (rubygems)
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
- Inventory repositories and clients: List hosted, proxy, and group repositories, then find every CI job and script that references Nexus endpoints. If you use group URLs, note which ones need a replacement.
- Create the RepoFlow repository layout: Create the local, remote, and virtual repositories you need. If you rely on a single Nexus group URL, use a RepoFlow virtual repository so clients can keep one stable read URL.
- Dry run a representative repository: Migrate a smaller repo with real usage patterns using automatic migration in RepoFlow. Existing CLI workflows can continue using the legacy tool.
- Validate in CI: Point a single pipeline at RepoFlow and run a clean build that restores dependencies from scratch.
- Cut over with a short write freeze: Freeze publishing to Nexus 2, run the final sync, then switch endpoints to RepoFlow.
- Keep Nexus read only while you monitor: After a stable window, archive and decommission safely.