Fleet Manager: Migrate a Community Edition database to Aura

Fleet manager now includes the ability to help you migrate your self-managed Community Edition databases to Aura via a simple user interface. In order to use this, you will need to have your Community Edition Neo4j database(s) registered with Fleet Manager. Please see the documentation for details on how to do this.

The Aura migration works for Neo4j Community Edition version 5.26 with Fleet Manager plugin 1.20, or version 2026.05 or later. If your Community Edition is running an earlier version of Neo4j, please upgrade to a supported version to use the migration utility.

There are two migration paths which are available, one which is automatic, and one which provides more control over the options and process.

To migrate your Community Edition database to Aura automatically, choose the “migrate with one click” option from the ellipsis menu.

This will bring up a confirmation window of the new Aura instance which will be created to migrate the database onto. The cheapest AuraDB instance is chosen, and the costs are displayed for you to review. If you are happy with the suggestion, click “Migrate” and the migration process will start. If you wish to have more control over the target, click “Cancel” and choose the “Migrate to Aura" (with options) approach.

Once the migration starts, the credentials for the neo4j user on the newly created AuraDB instance are shown. Please save these details to connect to the instance later. Once done, click next and the status of the steps is displayed. If you navigate away from this page, it can be displayed again by choosing “Migration status” from the ellipsis menu.

Once all four steps in the migration have completed, you may review your migrated Community Edition database in the new AuraDB instance. Should you need to review progress or investigate any issues, the “standard output” shows more information about each step in the process.

Choose this option if you require more control over your migration—such as choosing a specific instance type or size, selecting a region, or reusing an existing Aura instance. To launch the option, press the “Migrate to Aura” button on the instance card, or choose “Migrate to Aura” from the ellipsis menu.

The first step is displayed, which provides details of the need to confirm that your application is compatible with Aura. This includes reviewing the driver and application versions in use, and checking for any plugins or custom code which may not be supported in Aura. NOTE: The automatic migration bypasses this step and assumes the application is compatible.

The manual option provides guidance on what is needed and links to the documentation. The automatic option can be used to enable collection of workload (queries) for a 24 hour period to assist with this analysis. See documentation for details on this feature and requirements.

To proceed to the next step, check the box to confirm you are aware of the need for application compatibility and click “Next”.

The second step is to choose where you want the Community Edition database to migrate to in Aura. You may choose to migrate to a new AuraDB instance, or reuse an existing one. Choose the options for your target AuraDB instance for the migration, review the costs and choose next to continue. If creating a new instance, the credentials for the neo4j user on the newly created AuraDB instance are shown. Please save these details to connect to the instance later.

The third step is to run the migration. You may choose to run the steps yourself (manually) and follow the commands, or Fleet Manager can run the steps automatically for you. The progress can be followed on the Migration status window.

For full details of the feature, including additional content such as managing migration history, please refer to the documentation.