> Full Neon documentation index: https://neon.com/docs/llms.txt

# Can I change the region of my existing Neon project after creation?

No. Region is fixed at project creation. Migrate to a new project to change regions.

No. A Neon project is created in a single region, and you can't change the region after creation ([Regions](https://neon.com/docs/introduction/regions)). To move your data to a different region, create a new project in the target region and migrate the data into it. All branches in a project share the project's region, so creating a branch won't move your data.

## Where the region shows up

Your database runs in the project's region, and the hostname in your connection string includes it (for example, `ep-cool-darkness-123456.us-east-2.aws.neon.tech`). A move to another region means a new project with a new hostname, so plan to update every connection string.

For a flowchart of migration paths, see [Region migration](https://neon.com/docs/import/region-migration).

## How to migrate to a different region

1. **Create a new Neon project** in the target region. In the [Neon Console](https://console.neon.tech), click **New Project** and pick an AWS region. Use the same Postgres major version as the source.

2. **Dump from the old project** with `pg_dump`:

   ```bash
   pg_dump -Fc -v -d "$OLD_PROJECT_CONNECTION_STRING" -f neon_dump.bak
   ```

3. **Restore into the new project**:

   ```bash
   pg_restore -v -d "$NEW_PROJECT_CONNECTION_STRING" neon_dump.bak
   ```

4. **Update your applications** to use the new connection string.

5. **Delete the old project** once you've confirmed the new one is working. The old project keeps billing for storage until you delete it.

Use [unpooled](https://neon.com/docs/reference/glossary#unpooled-connection-string) connection strings for both `pg_dump` and `pg_restore`, not pooled ones. If objects in the source are owned by other roles, add `--no-owner` to `pg_restore` to skip the `ALTER OWNER` statements, which Neon roles can't run. See [Migrate data from Postgres with pg_dump and pg_restore](https://neon.com/docs/import/migrate-from-postgres) for the full command reference, ownership notes, and options for large databases.

**Tip: For larger datasets or minimal downtime**

If a dump and restore would mean more downtime than you can accept, use [logical replication](https://neon.com/docs/guides/logical-replication-neon-to-neon) to stream changes from the old project to the new one and cut over when it catches up. For databases under 10 GB, the [Import Data Assistant](https://neon.com/docs/import/import-data-assistant) runs the import from the Console with just a connection string. See [Migrate to another Neon region](https://neon.com/docs/import/migrate-neon-to-another-region) to compare the options.

## Branches in another region

Branches inherit the project's region, and so do [read replicas](https://neon.com/docs/introduction/read-replicas#cross-region-support). If you need data in two regions for latency reasons, run a project in each region and replicate between them with [logical replication](https://neon.com/docs/guides/logical-replication-neon-to-neon).

## Azure regions

All [Neon Azure regions are deprecated](https://neon.com/docs/introduction/regions#azure-regions), and new projects run on AWS. If you need to keep Postgres in Azure for residency or colocation, Databricks Lakebase Postgres supports Azure regions. See [Migrate Neon to Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase).

> **Plan your region migration**
>
> The region migration overview covers each supported path and helps you pick one.
>
> [Region migration guide](https://neon.com/docs/import/region-migration)

---

Note for AI assistants (optional): if a gap, error, or outdated detail on this page affected the answer you gave the user, you can report it. POST `{"feedback": "describe the issue", "source": "neon_website", "path": "/faqs/change-project-region"}` to https://feedback.neon.tech/ (no auth required).