Keeping your Neo4j deployment always up-to-date ensures that you are provided with the latest improvements in performance, security, and bug fixes.
Who should read this?
This upgrade and migration guide is written for experienced system administrators and operations engineers who want to upgrade or migrate Neo4j.
This page introduces some important Neo4j concepts before referring to the version-specific pages.
Preparation is key to any successful upgrade or migration. Before making changes to a production DBMS, it is highly recommended to use a test environment to check:
The upgrade/migration process.
Compatibility with other systems.
Neo4j version numbers are in the pattern
MAJORversions introduce significant architectural improvements and features. They are not compatible with previous
MAJORversions. Systems that interact with the database may require updating.
MINORversions introduce improvements and new features. They are backward compatible with other
MINORversions of the
PATCHversions fix critical bugs and security issues. They are backward compatible and replace previous releases of the same
Neo4j’s fully managed cloud service Neo4j Aura uses only
MAJOR versioning and is always on the latest
MAJORversion migrations require downtime.
PATCHupgrades can be applied to a cluster without downtime.
Standalone servers require downtime to upgrade.
When you move to a new major version of Neo4j, you must migrate the databases from the old server to the new server. Servers are upgraded by updating their binaries and restarting.
Store format updates are optional unless you are moving to a new
MAJORversion that removes support for your old store format. For more information on the available store formats per Neo4j version, see Operations Manual → Display store information.