Supported upgrade and migration paths

This section explains the supported upgrade and migration paths.

Which path you choose depends on your current version and the version you want to go to; if you are going to upgrade or migrate the whole Neo4j DBMS or a single user database; and your backup and restore strategy.

  • sequential (Neo4j DBMS) — 3.5.latest → 4.0.latest → 4.1.latest → 4.2.latest → 4.3.latest → 4.4.latest
    It includes migration and follow-up upgrades of the whole Neo4j DBMS (both the user and system databases).

  • direct migration (Neo4j 3.5 only) — Neo4j Community or Enterprise Edition 3.5.latest → Neo4j Enterprise Edition 4.x.latest
    It makes use of the neo4j-admin copy command to migrate the data store of the single 3.5 user database.

    The neo4j-admin copy command is a Neo4j Enterprise Edition feature. However, you can use it to migrate from Neo4j Community Edition to Neo4j Enterprise Edition.

  • direct upgrade (single user database only) — a user database on any version → to a later version.
    It makes use of the neo4j-admin copy or neo4j-admin restore commands to copy/restore a single user database into a running Neo4j DBMS on a later version.

upgrade paths

1. Sequential path (Neo4j DBMS)

Following the sequential path, you first migrate your Neo4j deployment from 3.5.latest to 4.0.latest and then sequentially upgrade it to 4.1.latest, 4.2.latest, 4.3.latest, and 4.4.latest. It makes use of neo4-admin load or neo4j-admin restore to copy both the user and the system databases or backups to the new installation, and then it upgrades the data and schema stores to the new version during the Neo4j startup. The neo4j-admin commands can be run from an online, as well as from an offline Neo4j DBMS, and must be invoked as the neo4j user to ensure the appropriate file permissions.

Table 1. Documentation for completing your upgrade/migration
Starting version Target version Supported path Operations Documentation

3.4.latest

3.5.latest

3.4.latest → 3.5.latest

Upgrade

3.5.latest

4.0.latest

3.5.latest → 4.0.latest

Migration

3.5.latest

4.1.latest

3.5.latest → 4.0.latest → 4.1.latest

Migration and upgrade

3.5.latest

4.2.latest

3.5.latest → 4.0.latest → 4.1.latest → 4.2.latest

Migration and upgrades

3.5.latest

4.3.latest

3.5.latest → 4.0.latest → 4.1.latest → 4.2.latest → 4.3.latest

Migration and upgrades

3.5.latest

4.4.latest

3.5.latest → 4.0.latest → 4.1.latest → 4.2.latest → 4.3.latest → 4.4.latest

Migration and upgrades

4.0.latest

4.1.latest

4.0.latest → 4.1.latest

Upgrade

4.0.latest

4.2.latest

4.0.latest → 4.1.latest → 4.2.latest

Upgrades

4.0.latest

4.3.latest

4.0.latest → 4.1.latest → 4.2.latest → 4.3.latest

Upgrades

4.0.latest

4.4.latest

4.0.latest → 4.1.latest → 4.2.latest → 4.3.latest → 4.4.latest

Upgrades

4.1.latest

4.2.latest

4.1.latest → 4.2.latest

Upgrade

4.1.latest

4.3.latest

4.1.latest → 4.2.latest → 4.3.latest

Upgrade

4.1.latest

4.4.latest

4.1.latest → 4.2.latest → 4.3.latest → 4.4.latest

Upgrade

4.2.latest

4.3.latest

4.2.latest → 4.3.latest

Upgrade

4.2.latest

4.4.latest

4.2.latest → 4.3.latest → 4.4.latest

Upgrade

4.3.latest

4.4.latest

4.3.latest → 4.4.latest

Upgrade

2. Direct migration path (Neo4j 3.5 only)

The direct migration path (3.5 → 4.x) makes use of the neo4j-admin copy command, which does not copy the schema store at all, and therefore, the intermediary steps of the sequential path are not needed. If a schema is defined, you have to recreate it by running the commands that the neo4j-admin copy operation outputs.

This path is suitable if you want to migrate a 3.5 Neo4j DBMS (Community or Enterprise) to 4.x Enterprise because the 3.5 DBMS contains just a single user database. You can also move from Community to Enterprise Edition (vice versa is not supported) and from a standalone to a cluster.

Table 2. Documentation for completing your upgrade/migration
Starting version Target version Supported path Operations Documentation

Neo4j Community or Enterprise Edition 3.5.latest

Neo4j Enterprise Edition 4.x.latest

Neo4j Community or Enterprise Edition 3.5.latest → Neo4j Enterprise Edition 4.x.latest

Store copy

The neo4j-admin copy command copies the node IDs, but the relationships get new IDs.

Therefore, if you want to preserve the relationship IDs, follow the sequential path.

3. Direct migration/upgrade of a single user database on a running Neo4j DBMS

This path allows you to use the neo4j-admin copy or neo4j-admin restore commands to copy or restore a single user database into a running Neo4j DBMS on a later version.

Table 3. Documentation for completing your upgrade/migration
Starting version Target version Supported path Operations Documentation

Any version

Any version

A single user database → into a running Neo4j Enterprise Edition on a later version

Restore

Any version

Any version

A single user database → into a running Neo4j Enterprise Edition on a later version

Restore

Any version

Any version

A single user database → into a running Neo4j Enterprise Edition on a later version

Store copy