Nexus Repository Manager Migration to JFrog Artifactory

Artifactory provides you the freedom of choice, hybrid environment support, automation, exhaustive and easily searchable metadata, storage flexibility, and so much more in comparison with Nexus Repository. If your team has decided to switch from Nexus Repository Manager to Artifactory, we have the a tool to make the transition quick and seamless for you. Read on to learn all about it.

The migrator tool supports migration to JFrog Artifactory 7.x from Nexus Repository Manager OSS and Nexus Repository Manager Pro. The current migrator version is 0.9.13.

What the Migrator Tool Handles

Migrated	Not Migrated
Local and proxy repositories	Hosted repository group configurations
Repository metadata	Build information and CI/CD pipeline data
Security entities (users, roles)	Nexus-specific plugins
Artifact checksums	Repository routing rules

❗️
Important
You must run the migrator tool from the Nexus Repository Manager machine

✅
Download Nexus Migrator
Download the migrator tool from here.

If there are checksum issues after migration, refer to the KB article to fix the issues.

Get Started

Nexus Migrator Release Notes

Release notes for the JFrog Nexus Migrator tool, listing fixes, improvements, and new features across all published versions.

Migrator Tool Overview

The migrator tool uses Docker, installed on the Nexus Repository Manager machine, to facilitate the migration of repositories and security entities.

Before You Begin

Review prerequisites and system requirements before beginning migration, including Nexus script execution requirements and network considerations.

Run the Migration

Migration Process

Run the Nexus-to-JFrog Artifactory migration script in a single stage or as separate sequential stages to migrate repositories, artifacts, and security settings.

Migration Tool Run in a Single Step

Migrate all Nexus entities to JFrog Artifactory in a single step by running the migration script with the "all" argument and providing Artifactory connection details.

Migration Tool Run in Multiple Stages

Run the JFrog Nexus migrator tool in multiple stages to migrate artifacts incrementally, executing config, security, and artifact stages separately.

Optional Customization

Edit Migration Configuration [OPTIONAL]

After running the migrator with the config option, customize the generated migrationConfig.yaml file to control migration behavior.

Edit Repository Names [OPTIONAL]

After running the migrator with the getconfig option, edit the repositories.list file to customize repository naming during migration.

Edit Security Entities [OPTIONAL]

After running the migrator with the getconfig option, edit the securityRegexMap.list file to customize security entity mapping.

Avoid Repositories from Migration [OPTIONAL]

After running the migrator with the getconfig option, edit the repositories.yaml file to exclude specific repositories from migration.

Avoid Security Entities from Migration [OPTIONAL]

After running the migrator with the getconfig option, edit the security.json file to exclude specific security entities from migration.

Repository Migration Status

Monitor the status of repository migration from Sonatype Nexus to JFrog Artifactory using the repositories.yaml file maintained by the migrator tool.

Frequently Asked Questions

❓Can I migrate all Nexus repository types to Artifactory?

A: The migrator tool supports local and proxy repositories from Nexus Repository Manager OSS and Pro. Group repositories, Nexus-specific plugins, and build information are not migrated automatically. Review the migration scope table above before starting your migration.

❓How long does a Nexus to Artifactory migration take?

A: Migration time depends on the size of your Nexus repository and network bandwidth. The migrator tool must be run from the Nexus Repository Manager machine. For large repositories, plan for several hours and schedule the migration during a maintenance window.

❓What happens to existing artifact data during migration?

A: The migrator tool copies artifacts from Nexus to JFrog Artifactory 7.x. Your original Nexus data is not deleted or modified. After verifying the migration, you can decommission the Nexus instance. If checksum issues occur after migration, use the JFrog KB article to fix them.