Migrate data from another Neon project

This guide describes how to migrate a database from one Neon project to another by piping data from pg_dump to pg_restore.

Use these instructions to:

• Import a database from a Neon project created in one region to a project created in another region.
• Import a database from a Neon project created with one Postgres version to a Neon project created with another Postgres version.

Important considerations

• Upgrading the Postgres version: When upgrading to a new version of Postgres, always test thoroughly before migrating your production systems or applications. We also recommend familiarizing yourself with the changes in the new version of Postgres, especially those affecting compatibility. For information about those changes, please refer to the official Postgres Release 15 or Release 16 documentation.
• Piping considerations: Piping is not recommended for large datasets, as it is susceptible to failures during lengthy migration operations (see Pipe pg_dump to pg_restore for more information). If your dataset is large, we recommend performing the dump and restore as separate operations. For instructions, see Migrate data from Postgres with pg_dump and pg_restore.

Import data from another project

To import your data from another Neon project:

1. Create a new project with the desired region or Postgres version. See Create a project for instructions.

2. Create a database with the desired name in your new Neon project. See Create a database for instructions.

3. Retrieve the connection strings for the new and existing Neon databases.

   You can find the connection details for your database by clicking the Connect button on your Project Dashboard. Connections strings have this format:

   postgresql://[user]:[password]@[neon_hostname]/[dbname]

4. Prepare your command to pipe data from one Neon project to the other. For the pg_dump command, specify connection details for the source database. For the pg_restore command, specify connection details for the destination database. The command should have the following format:

   pg_dump -Fc -v -d postgresql://[user]:[password]@[source_neon_hostname]/[dbname] | pg_restore -v -d postgresql://[user]:[password]@[destination_neon_hostname]/[dbname]

   With actual source and destination connection details, your command will appear similar to this:

   pg_dump -Fc -v -d postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/my_source_db | pg_restore -v -d postgresql://alex:AbC123dEf@square-shadow-654321.us-east-2.aws.neon.tech/my_destination_db

   note

   While your source and destination databases might have the same name, the hostnames will differ, as illustrated in the example above.

   The command includes these arguments:

   • -Fc: Sends the output to a custom-format archive suitable for input into pg_restore.
   • -v: Runs commands in verbose mode, allowing you to monitor what happens during the operation.
   • -d: Specifies the database name or connection string.

5. Run the command from your terminal or command window.

6. If you no longer require the old project, you can remove it. See Delete a project for instructions.