Upgrade Compatibility - Repository Manager 2 to 3

Tip

When upgrading Nexus Repository Manager 2 to 3, Sonatype always recommends having the latest version 2 upgrading to the latest version 3 (as well as IQ Server for applicable users).  This gives you the latest bug fixes , especially important for ones regarding the upgrade process, and features for Nexus Repository Manager 3. Upgrading to an older NXRM3 then subsequently updating to the latest NXRM3 is not equivalent, as it hits the old upgrade bugs.

The latest Nexus Repository Manager version 2 can be downloaded here.

The latest Nexus Repository Manager version 3 can be downloaded here.

Tip

When upgrading from NXRM2 to NXRM3, both versions must have the same licensing setup. In other words, OSS upgrades to OSS and PRO upgrades to PRO. The same license file can be used in NXRM2 and NXRM3 or a license can always be applied at a later time.

In the event you cannot use the latest version of NXRM2, below is a matrix of what version is minimally associated with what. Versions up to the row above it should also be supported. Not upgrading to an associated version will have failures.

Version 2 Version 3 Minimum Lifecycle Firewall compatible IQ Server
2.14.8 3.12.1 1.46.0
2.14.6 3.8.0 1.42.0
2.14.5 3.7.1 1.33.0
2.14.4 3.4.0 Not Supported
2.14.3 3.2.1 Not Supported
2.14.2 3.2 Not Supported
2.14.1 3.1 Not Supported

Supported Nexus Repository Manager Upgrade Paths

Source Nexus Repository Manager Required Upgrade Procedure
3.1.0 and newer
  1. Upgrade to latest available 3.x version
3.0.0 to 3.0.2
  1. Learn about important directory layout changes introduced in 3.1.0
  2. Upgrade to latest available 3.x version
3 milestone 7
  1. Upgrade to 3.0.0
  2. Learn about important directory layout changes introduced in 3.1.0
  3. Upgrade to latest available 3.x version
3 milestone 1 to milestone 6 Upgrading these versions is not supported.
Latest 2.x version
  1. Upgrade to latest available 3.x version
2.0 or any later 2.x version
  1. Upgrade to latest available 2.x version
  2. Upgrade to latest available 3.x version
1.x
  1. Upgrade to any 2.x version up to 2.7.2 1
  2. Upgrade to latest available 2.x version
  3. Upgrade to latest available 3.x version

1 Versions after 2.7.2 do not include support for upgrading 1.x versions