Autoscaling Report: Production databases on Neon use 2.4x less compute and 50% less cost than if they were running on a provisioned platform.
/Region migration/Neon to another region

Migrate to another Neon region

Choose a migration method for a new Neon project in another region

You can't change the region of an existing Neon project in place. A project's region is fixed when you create it. To move your database to a different region, you create a new Neon project in the target region and migrate your data into it, then cut over and delete the old project.

Choose a migration method

Each option below is a different way to move your database into a new Neon project in a different region. Choose the option that matches your requirements.

Import Data Assistant

Best for smaller databases (roughly under 10 GB) and when you want a guided flow in the Neon Console.

In the Neon Console, open the Projects page and start the Import Data Assistant. The assistant creates your new Neon project in the target region as part of the same flow. You begin by entering the connection string for the database you are migrating from. See Import Data Assistant for instructions.

pg_dump and pg_restore

Best for when you want full control of dump files and restore timing. See Migrate data from another Neon project.

Logical replication

Best for minimal downtime on busy databases where a long dump or restore window is not acceptable.

You replicate from the source project to the target and cut over when caught up. See Replicate data from one Neon project to another. Expect more configuration than other migration methods.

Need help?

Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support.

Was this page helpful?
Edit on GitHub

On this page

Copy neon init command