Importing an existing database
The process of importing or loading data requires you to create an AuraDB instance beforehand.
There are two ways you can import data from an existing Neo4j database into an Aura instance.
The easiest way is to export a Neo4j database as a .dump file and use the Import database process. This process, however, only works for .dump files under 4GB.
If the size of the .dump file exported from a database is greater than 4GB, you must use the Neo4j Admin
database upload method.
To import a .dump file under 4GB:
Navigate to the Neo4j Aura Console in your browser.
Select the instance you want to import the data.
Select the Import Database tab.
Drag and drop your .dump file into the provided window or select Select a .dump file and select your file.
When the upload is complete, the instance goes into a
Loading state as the dump is applied.
Once this has finished, the instance returns to its
Running state; and the data is ready.
This command will not work if you have a network access configuration setup that prevents public traffic to the region your instance is hosted in. See Public traffic below for more information.
database upload is a Neo4j Admin command that you can run to upload the contents of a Neo4j database into an Aura instance, regardless of the database’s size.
For details of how to use the
neo4j-admin database upload command, along with a full list of options, see Upload to Neo4j Aura.
If you have created a network access configuration from the Network Access page, accessed through the sidebar menu of the Console,
Public traffic must be enabled for the region your instance is hosted in before you can use the
database upload command on that instance.
To enable Public traffic on a network access configuration:
Select Configure next to the region that has Public traffic disabled.
Select Next until you reach step 4 of 4 in the resulting Edit network access configuration modal.
Clear the Disable public traffic checkbox and select Save.
You can now use the
database upload command on the instances within that region. Once the command has completed, you can disable Public traffic again by following the same steps and re-selecting the Disable public traffic checkbox.