# Migrate between regions

> Use Temporal Cloud's High Availability features to migrate between regions.

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. 
See [failover scenarios](/cloud/export#failover-scenarios) for details.

[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

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

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

![Choose the region for the replica](/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 API key authentication: ensure your workers (and all other client code) are updated to [use the regional endpoint of the new replica](/cloud/namespaces#access-namespaces).
4. Trigger a failover to the new region.

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

5. Remove the Namespace replica in the region you are migrating from.

> **📝 Note:**
> If using [API keys](/cloud/api-keys) for worker authentication, you must open a [support ticket](/cloud/support#support-ticket) to remove the replica.
>

![Remove the replica for the original region](/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.
>