There are several methods available for migrating / upgrading your Aura instances, both AuraDB and AuraDS, from Neo4j version 4 to the latest version. 

• Run the test / Live migration option from the Migration readiness report.
• Clone to a new AuraDB / AuraDS latest version instance.
• Clone to an existing AuraDB / AuraDS latest version instance.
• Manually export and import the data.

Pre Upgrade Tasks

We recommend that you review the Neo4j Aura product documentation available, in the Migrate a version 4 instance to the latest version section.

Other sources of helpful information are the Upgrade and Migration Guide, in particular focus on the Migrate from 4.4 section, making sure to review the Reference section that includes, 

• Breaking changes between Neo4j 4.4 and Neo4j 5.x 
• Changes to procedures and functions in Neo4j version 5
• Changes to Java API in Neo4j version 5

You may also wish to consider capturing and dropping the existing indexes prior to migration / upgrade and recreating them at the end of the process. This may prove more performant for large stores and remove the existing detail check of the index. Please refer to the article Indexes - Capture / Drop / Recreate existing for details on how to do this.

 

Run the test / Live migration option from the Migration readiness report

The Migration readiness report is a tool that advises how to prepare an AuraDB v4 instance for migration to AuraDB latest. It reports current application queries, drivers, and database objects that would prevent you from migrating to AuraDB latest by providing information based on your recent usage history.

Included in the functionality is the ability to perform a test or live migration. Please refer to the Testing and executing the migration section of the documentation for details of how to perform a test or live migration.

 

 

Cloning to a new or existing AuraDB / AuraDS latest version instance

Note: You must ensure both the source and target AuraDB / AuraDS instances are using the same Cloud Service Provider (CSP), as it is not possible to clone across CSP's at the current time.

Caution: Cloning into an existing AuraDB / AuraDS Instance will replace all data. Please take a snapshot and export it if you want to keep the current data.

Cloning to new AuraDB / AuraDS latest version instance

On the source AuraDB / AuraDS instance, if you have decided to do so, please ensure you have dropped your indexes before attempting to clone. 

In order to migrate / upgrade a version 4 instance using clone options, refer to the Clone an instance section of the Neo4j Aura product documentation for details of how to clone to a new or an existing instance.

Remember to download the credentials for your new instance.

Once the instance is running, if you dropped your indexes from the source system before the clone, please recreate them in the latest version instance.

Manually export and import the data

Follow the steps in the knowledge base article for exporting your data . Once you have downloaded the dump file you can proceed with the import process.

The first stage of the import process is to create a new latest version Aura instance (AuraDB / AuraDS), in which to load your dump file into. Refer to the Neo4j Aura product documentation for details of how to create a new instance.

Remember to download the credentials for your new instance.

 

Once the new instance is in the running state, you are now ready to import your data. Refer to the Upload an existing Neo4j database section of the Neo4j Aura product documentation for details and options of how to perform the import, dependant on your network access configuration setup (public traffic enabled or disabled) / the size of your dump file.

 

At this stage, once the instance is running, if you dropped your indexes from the source system before the dump file was created, please recreate them in the version 5 instance.