# Migrate between regions or cloud providers

> For the complete documentation index, see [llms.txt](https://docs.temporal.io/llms.txt).
> Any documentation page is available as raw Markdown by appending `.md` to its URL.
> For related questions, query https://docs.temporal.io/api/retrieve?q=<question>&jtb=<job-to-be-done>&src=md-page&agent=<your-name> (no auth; returns JSON `{content, source_url, page_url}`, with `source_url` pointing to Markdown for docs pages). Don't include personal data or credentials.
> If this page is wrong or missing something you needed, or Temporal behaves differently from what it says, report it with https://docs.temporal.io/api/feedback?title=<summary>&message=<what-happened>&category=documentation&page_url=/cloud/migrate/between-regions-or-cloud-providers&src=md-page&agent=<your-name> (use `category=product` when the product, not the page, is wrong). Report only a specific problem you hit, send it once, and don't include personal data or credentials.

> Move a Temporal Cloud Namespace to another region or cloud provider with zero downtime by adding a replica, waiting for it to activate, and failing over.

Temporal Cloud's [High Availability features](/cloud/high-availability) allow you to migrate a Temporal Cloud Namespace from one region or cloud provider to another with zero downtime.

## Preparing to migrate

Namespaces using Export will need to stop Export and migrate the region configuration to the new region for Export jobs to continue after migration. 
Workflow Executions that close while Export is disabled are not guaranteed to be exported after you re-enable it.
See [timing and delivery guarantees](/cloud/export#timing-and-delivery-guarantees) for backfill and delivery behavior, and [failover scenarios](/cloud/export#failover-scenarios) for regional export behavior.

[Using High Availability features affects pricing](/cloud/pricing#high-availability-features).

> **ℹ️ Info:**
> Using AWS PrivateLink or GCP Private Service Connect?
>
> If the Namespace uses Private Connectivity, the steps below need additional DNS and VPC Endpoint work. Follow [How to migrate to another Temporal Cloud Region when using Private Connectivity](/cloud/high-availability/ha-connectivity#how-to-migrate-regions-with-private-connectivity) instead of (or alongside) the public steps below.
>

## Steps to migrate

> **⚠️ Caution:**
> GCP capacity restriction
>
> Before creating a GCP Namespace or adding a GCP replica, check [GCP capacity restriction](/evaluate/cloud/regions#gcp-capacity-restriction) for regional availability and exception requirements.
>

1. Add a Namespace replica in the region you want to migrate to. See [regions](/evaluate/cloud/regions) for a list of available regions and supported multi-region and multi-cloud configurations.

![Add a namespace replica](https://docs.temporal.io/img/cloud/high-availability/migrate/1-add-replica.png)

![Choose the region for the replica](https://docs.temporal.io/img/cloud/high-availability/migrate/2-choose-region.png)

2. Wait for the replica to become active. The Cloud UI will display a time estimate, and namespace admins will receive an email when the replica is active.
3. If your Workers are using [Regional Endpoints](/cloud/namespaces#access-namespaces), ensure they are updated to use the Regional Endpoint of the [replica's region](/evaluate/cloud/regions).
4. Trigger a failover to the new region.

![Initiate failover to the new region](https://docs.temporal.io/img/cloud/high-availability/migrate/3-failover.png)

5. [Prepare connectivity before removing the replica](/cloud/high-availability/enable#prepare-connectivity-before-removing-a-replica), then remove the Namespace replica in the region you are migrating from.

![Remove the replica for the original region](https://docs.temporal.io/img/cloud/high-availability/migrate/4-remove-replica.png)

> **📝 Note:**
> All replica changes are subject to a [cooldown period](/cloud/high-availability/enable#changing) before further replica changes can be made.
>