Skip to main content

Upgrading from Nexus Repository Manager 2

Nexus Repository 3 is a complete redesign of the repository manager and does not include any legacy code from Nexus Repository 2.

While Nexus Repository 2 was based on a Maven repository design that was dependant on how components were stored on the file system, Nexus Repository 3 uses blob storage, moving away from the idea of a repository being a folder in a file system. This makes Nexus Repository 3 far more scalable to different ecosystems and deployment environments, avoiding the file system limitations that some Nexus Repository 2 deployments encountered with flat directories containing tens of thousands of components common in some repositories.

Upgrading from Nexus Repository 2 to Nexus Repository 3 requires creating an upgrade plan:

  1. Begin by Determining and Planning Your Upgrade Path

    1. Built-in Upgrade Wizard (Always Preferred)

    2. Manual Import/Export (Preferred if Cannot Use Wizard)

    3. Manually Proxying Old Repositories

  2. Understand Nexus Repository 2 vs. Nexus Repository 3 feature equivalency

  3. Consider any IQ Server or Firewall integration impacts, especially if using a manual method

  4. Plan to replace custom plugins and scripts using the Nexus Repository 3 API

  5. If not already complete, upgrade your Nexus Repository 2 instance to the latest Nexus Repository version using these instructions

  6. If using the Upgrade Wizard, decide on a data transfer method

    1. Whether using the Upgrade Wizard or Import, hard linking is always preferred; consider if you can remove any barriers to hard linking

  7. If using the Upgrade Wizard, complete optimization steps

  8. Ensure you meet all prerequisites

    1. Upgrade Wizard Prerequisites

    2. Manual Method Prerequisites

Once you have made the above decisions and created a plan, you are ready to upgrade!


Nexus Repository Pro customers can also take advantage of support team assistance.