Login Contact Us Book a Demo
Resources Videos
How to Migrate Sonatype Nexus Repository OSS to Community Edition

Migrate Nexus Repository OSS to Community Edition

Watch this step-by-step walkthrough to migrate a Sonatype Nexus Repository OSS instance to Nexus Repository Community Edition using Sonatype’s Repository Instance Migrator. This video covers a typical migration process: verifying your environment, transferring configuration and hosted repository content, and enabling polling to keep new artifacts synchronized during the migration window.

 

glyph bracket orange
glyph bracket orange

Migration Checklist

Use this checklist to prepare your environments, guide each stage of the migration, and account for key considerations before you begin.

Before You Begin

Upgrade the source Nexus Repository OSS instance to version 3.70.5.
Confirm the target Nexus Repository Community Edition instance has default settings and is running, accessible, and ready to receive the migration.
Verify network access and valid credentials for both source and target instances.
Download the Repository Instance Migrator CLI.
Evaluate if your environment is complex and reach out to Sonatype Professional Services if assistance is needed.

Migration Process

Verify the source OSS and target Community Edition instances.
Configure and connect the Repository Instance Migrator CLI.
Read the source repository, admin, and security configuration.
Review and, if needed, adjust the generated migration configuration file.
Write the configuration to the Community Edition target.
Validate repositories and migrated admin and security settings in the target.
Migrate hosted repository components and assets.
Confirm that migrated content is available in the target repository.
Enable content polling to synchronize new or updated artifacts during the migration window.

Need Assistance with Your Migration?

Explore available migration services from the Sonatype Professional Services team. If your environment is complex, we can help you every step of the migration process.

Frequently Asked Questions

What does this migration walkthrough cover?

This video shows the core process for migrating a Nexus Repository OSS instance to Nexus Repository Community Edition using Sonatype’s Repository Instance Migrator. It covers environment validation, configuration migration, hosted content migration, validation, and content polling.

What version of Nexus Repository OSS is required?

Your source Nexus Repository OSS instance must be running version 3.70.5 before you begin. If you are using an earlier version, upgrade to 3.70.5 first.

What do I need before running the migrator?

You will need the Repository Instance Migrator CLI, network access to both source and target instances, valid credentials for each instance, and the required connection and migration settings configured for the CLI.

What configuration does the migrator transfer?

The migrator can transfer repository configuration along with related administrative and security objects, such as content selectors, cleanup policies, routing rules, privileges, roles, and users. You can review the generated JSON configuration file before applying it to the target.

What is content migration polling?

Content polling lets the migrator detect and synchronize new or updated hosted content from the source instance while the migration is still underway. This helps keep the target current when users continue publishing artifacts during the migration window.

How do I confirm the migration was successful?

After writing the configuration, verify the migrated repository and related admin and security objects in the Community Edition UI. After running the content migration, refresh the target repository and confirm that its components and assets are available.

When should I contact Sonatype Professional Services?

Reach out to Sonatype Professional Services if your environment has complex requirements, if you need help planning or executing the migration, or if you are migrating to Nexus Repository Cloud.