Migrate your databases

The following steps assume that:

  • You have taken backups of any Neo4j v4.4 databases you want to migrate.

  • You have installed an equivalent Neo4j v5 DBMS to move the databases to.

Switching to Neo4j v5

If your method of installation (e.g. tarball or docker) allows you to have Neo4j v4.4 and v5 installations concurrently on the same server, you may now shut down your Neo4j v4.4 process. Alternatively, you may prefer to leave it running, with all its databases in read-only mode until the migration is complete.

If you do choose to run two Neo4j installations concurrently, ensure that your server has sufficient resources to support this and that your configuration for the two installations does not conflict (e.g., on ports).

From this point on, you are on the Neo4j v5 DBMS. If both versions are on the same machine, you may need to change the default Java runtime to Java 17.

Make sure Neo4j v5 does not already host any databases with the same name as those that you want to migrate (ignoring the system database).

Restore the database on Neo4j v5

You can now restore the database backups to Neo4j v5.

If you are migrating to a cluster, only restore them to one server; later you will use this server to seed the others.

If you are migrating databases from an installation of Neo4j v4.4 Community Edition, you need to restore your dump file using the neo4j-admin database load command.

  1. Use the neo4j-admin restore command to restore each of your databases, except the system database:

    /usr/bin/neo4j-admin database restore <databasename> --from-path=/migration-backups/<databasename>
  2. Use the neo4j-admin database migrate command to update the file metadata to the v5 format:

    /usr/bin/neo4j-admin database migrate <databasename>

The command will fail if you do not have RANGE, POINT, or TEXT indexes for each of your BTREE indexes and index-backed constraints. You can use the option --force-btree-indexes-to-range to force neo4j-admin database migrate to drop the BTREE indexes and replace them with RANGE indexes. It is advisable to read the section on preparing indexes from Prepare for your migration to understand the consequences.

Recreate the databases

Start Neo4j v5 and recreate each of your databases using the following Cypher:

CREATE DATABASE <databasename>
  1. Start Neo4j v5 and retrieve the server ID for the server where you restored the backups by running:

    SHOW SERVERS YIELD address, serverId

    When you create a database on a Neo4j v5 cluster you can optionally use the TOPOLOGY parameter to specify how many primary and secondary copies are required. These values can be changed later using ALTER DATABASE.

    For more information, see Operations Manual v5 → Create Database.

  2. Recreate each of your databases using the following Cypher:

    CREATE DATABASE <databasename>
    TOPOLOGY [desired number of primaries] PRIMARIES [desired number of secondaries] SECONDARIES
    OPTIONS {existingData: 'use', existingDataSeedInstance: '[ServerId for a]'}
  3. Finally, run REALLOCATE DATABASES to distribute your databases among the servers.


(Optional) Restore roles and privileges

Restore the roles and privileges associated with each of your databases by running the respective metadata script data/scripts/databasename/restore_metadata.cypher, with the neo4j-admin restore command output, using Cypher Shell:

Using cat (UNIX):

cat neo4j-enterprise-5.x/data/scripts/databasename/restore_metadata.cypher | bin/cypher-shell -u user -p password -a ip_address:port -d system --param "database => 'databasename'"

Using type (Windows):

type neo4j-enterprise-5.x\data\scripts\databasename\restore_metadata.cypher | bin\cypher-shell.bat -u user -p password -a ip_address:port -d system --param "database => 'databasename'"

Monitor the logs

When Neo4j starts, it can be useful to monitor the logs for any errors or warnings caused by the migration. You can find information about the upgrade in the neo4j.log file.