OrientDB to Postgres Migration Guide for Nexus Repository

At Sonatype, we’re well aware that migrations can be frustrating. But with support for OrientDB databases ending early next year, the time to start planning to get off of OrientDB is now. Your options are H2 and Postgres, and out of the two, Sonatype strongly suggests that all enterprise instances of Nexus Repository use Postgres.

To cut down on frustration and give you the smoothest possible migration, we’ve prepared the attached document, which includes complete instructions for migrating from OrientDB to Postgres, along with helpful tips and solutions to some of the most common migration pitfalls. Our hope is that this document jumpstarts your efforts.

If changes are made to the doc, we’ll update the link above so that it always points to the latest-and-greatest.

EDIT

Updated on 1/9/26 with a new, refined look.

Pinned globally on Jun 23, 2025

post by prateek_dodda on Jun 26, 2025

Hi I have a quick question on this so we are currently using 3.70.4 Nexus Repository Manager OSS instance and planning to migrate from orientdb to postgresql database. Is this possible with the OSS instance?

post by jzora on Jun 26, 2025

The guide linked above is for customers who have purchased a Nexus Repository Pro license.

OSS users cannot use Postgres as a database option until they move to Community Edition! Check out documentation below.

Because you’re an OSS user, your path to Postgres will be to migrate to H2, upgrade to Java 17, move to Community Edition (3.77.0+), then migrate to Postgres.

Sonatype Community Edition Onboarding
Upgrading to Nexus Repository 3.71.0 and beyond

post by prateek_dodda on Jun 27, 2025

missed this part of the documentation. Thank you so much for the response.