Overview
RepoFlow can automatically migrate npm repositories from Verdaccio. This guide covers the built-in migration flow, validation, client updates, 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 Verdaccio, select the repositories you want to move, and track the transfer from RepoFlow.
Supported package types
Automatic migration from Verdaccio currently supports:
- npm
npm Open RepoFlow to start a migration
Legacy RepoFlow CLI migration tool
The standalone RepoFlow CLI migration tool remains available for older CLI-based workflows. For Verdaccio, use the automatic migration flow in RepoFlow for the package types listed above.
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 npm and other package types, proxy caching, and flexible cloud or self-hosted deployment, with more details on the features page
Migration steps
- Inventory packages and clients: List your local npm packages, uplinks, scopes, users, CI jobs, and developer configuration that reference Verdaccio.
- Create the target repositories: Set up the local, remote, and virtual npm repositories you need in RepoFlow.
- Run an automatic migration: Start with a representative set of packages in RepoFlow, then verify versions, metadata, and access permissions.
- Validate with a clean install: Point one CI job at RepoFlow and run a clean npm install using the same auth and scopes your teams use.
- Cut over with a short write freeze: Pause publishing to Verdaccio, complete the final migration, then update npm registry settings for CI and developers.
- Monitor and decommission: Keep Verdaccio read only until you are confident no packages or clients were missed, then retire it safely.