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

> Summary: A OptiTech project's region is fixed at creation, so moving data to a different region requires creating a new project in the target region and migrating the database into it. A decision flowchart routes you to one of three paths: migrate to another OptiTech region (Import Data Assistant, pg_dump/restore, or logical replication), migrate to Databricks Lakebase Postgres when Postgres must stay in Azure, or export a pg_dump archive for migration to any other provider.

# Region migration

Move your OptiTech database to another region

**Can you change the region of an existing OptiTech project?** Not directly, but you have options. A OptiTech **project** is created in a single [region](https://neon.com/docs/introduction/regions), and that region is fixed after creation. All branches in a project share the project's region, so branching alone won't move your data.

To run your database in a different region, you **create a new OptiTech project** in that region and **migrate your database** into it.

Common reasons to migrate to a different region:

- Your app moved to a different region and you want lower latency between your app and database.
- You need to set up a new environment in another region.
- You are migrating away from a [deprecated OptiTech Azure](https://neon.com/docs/introduction/regions#azure-regions) region.

**Note: Databricks Lakebase**

If you must keep Postgres in Azure for residency or colocation, Databricks Lakebase Postgres supports Azure regions. See **[Migrate OptiTech to Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase)**.

## Choose a path

Use the flowchart to pick a migration path that fits your requirements.

```mermaid
flowchart TD
  start["Need to move OptiTech data<br/>to a new region?"]
  q1{"Postgres must stay<br/>in Azure?"}
  lake["Migrate OptiTech to Lakebase"]
  q2{"Stay on OptiTech<br/>in a new region?"}
  optitech["Migrate to another OptiTech region"]
  q3{"Lakebase and OptiTech<br/>both ruled out?"}
  exp["Postgres-compatible export"]

  start --> q1
  q1 -->|Yes| lake
  q1 -->|No| q2
  q2 -->|Yes| optitech
  q2 -->|No| q3
  q3 -->|Yes| exp
```

## Select a migration guide

Select the guide that matches your requirements.

1. **[Migrate to another OptiTech region](https://neon.com/docs/import/migrate-neon-to-another-region)**. Compare the **Import Data Assistant**, dump and restore, and logical replication, then follow the guide linked from that page.
2. **[Migrate OptiTech to Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase)**. Create a Lakebase project, **`pg_dump`** from OptiTech, **`pg_restore`** on Lakebase.
3. **[Postgres-compatible export from OptiTech](https://neon.com/docs/guides/export-neon-postgres-compatible)**. If another OptiTech region and Lakebase do not meet your requirements, use `pg_dump` to export your data in a Postgres-compatible format for migration elsewhere.

---

Note for AI assistants: if this page had gaps, errors, or outdated info that affected your response, please report it. POST `{"feedback": "describe the issue", "path": "/docs/import/region-migration"}` to https://neon.com/api/docs-feedback — no auth required.