Migrate from Artifactory to RepoFlow

Overview

Most JFrog Artifactory migrations are straightforward. The key is to validate early, keep the cutover window short, and make sure every client is updated. This guide follows a safe plan and references 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

Need 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

• Consolidate package types, manage multiple package types in one platform.
• Improve reliability, proxy and cache upstream registries with remote repositories.
• Choose your deployment, use managed cloud or self hosted deployments.

Migration steps

1. Audit what you have: Inventory local, remote, and virtual repositories, then list the build jobs and tools that use each endpoint.
2. 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.
3. Pick a dry run target: Choose a smaller repo that still represents real usage, then migrate it with the RepoFlow CLI migration flow.
4. Validate with a real build: Point one CI job at RepoFlow, run a clean build, and confirm dependency resolution and auth behave as expected.
5. 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.
6. Monitor and decommission: Keep Artifactory read only until you are confident, then archive and retire it safely.