> This page location: /docs.md > /docs/management.md > /docs/atlas/create-connect-deployments.md > /docs/atlas/manage-clusters.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Move a Cluster to a Different Region

**Note: Feature Unavailable in Free Clusters**

This feature is available for Flex clusters and higher. Free clusters are designed for learning and small-scale development, and support a subset of Atlas capabilities. To learn more about which features are available for Free clusters, see [Atlas Free Cluster Limits.](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-atlas-free-tier)

## Considerations

### Support by Cluster Tier

Atlas supports changing a cluster's region and cloud provider:

- Anytime on a Flex cluster as long as the new region is [supported for Flex clusters.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-limits-config)

- Anytime on an `M10+` Atlas Core cluster.

During public preview, you can't change the region or cloud provider of an existing Atlas Infinite cluster.

### Preferred and Electable Nodes

Each node in the preferred and electable regions can:

- Participate in [replica set elections](https://www.mongodb.com/docs/manual/core/replica-set-elections.md#std-label-replica-set-elections)

- Become the [primary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) if the majority of replica set nodes are available.

On Atlas Core clusters, electable nodes must total 3, 5, or 7. On Atlas Infinite clusters, the storage layer coordinates failover instead of an election among the cluster's nodes. A standby compute node becomes the primary node without oplog replay or a cold start. To learn more, see [MongoDB Atlas Infinite: Architecture.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-architecture.md#std-label-atlas-infinite-architecture)

### Migration, Downtime and Performance Impact

Depending on the amount of data to migrate, migrations can take a significant amount of time. To maximize availability for a replica set, Atlas migrates one member at a time, starting with the secondary members first and then the primary.

Migration can affect performance if your primary is already reaching operational capacity: each newly migrated replica set member must perform an [initial sync](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-initial-sync), adding to the operational load. The type of initial sync that Atlas performs depends on your cloud provider. To learn more, see [Atlas Configuration Options](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-cluster-config-options). Migrations can also affect performance if [read preferences](https://www.mongodb.com/docs/manual/core/read-preference/) are set to read from secondaries: the replica set is down one secondary during the migration.

### VPC/VNet Peering (AWS and Azure)

If you move a cluster out of a region that has a [VPC/VNet peering](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering) connection, the moved cluster can no longer use that peering connection to communicate with servers in the peered network. Any other clusters with nodes remaining in the original region can continue to use the peering connection.

You can create multiple peering connections for each region, including a new peering connection with the region that you moved a cluster to.

**Note:**

Cluster nodes removed from a region can't inherit access rules from security groups (AWS) or allowed CIDR blocks configured for the peering connection. You must [configure IP Access List entries](https://www.mongodb.com/docs/atlas/security/ip-access-list.md#std-label-add-to-access-list) to allow the moved cluster to communicate with servers residing in the peered network. Cluster nodes remaining in the region are unaffected.

### Billing

If you change your cluster's [highest priority region](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-deploy-across-multiple-regions) or if MongoDB migrates oplog data to a different region, you will be billed for storage in both the old and new regions for the days following the region change. You must disable continuous cloud backup and reenable it to prevent billing in both the regions.

**Note:**

If you disable continuous cloud backup, Atlas will delete the continuous cloud backup history.

## Move a Single-Region Cluster

Use the following procedure to move nodes to a single-region cluster.

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Edit the configuration.

   Click Edit Config and select the cluster that you want to move from the drop-down menu.

   Alternatively, if you are already viewing the specific cluster, click Configuration.

3. In the Cloud Provider & Region view, select the desired new region for the new cluster.

   For Free clusters:

   - You must also select a higher cluster tier. Atlas supports moving Free clusters only when you [increase the cluster tier.](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-modify-cluster)

   - The available regions are a subset of the total supported regions for any given cloud service provider.

4. Click Review Changes.

5. Click Apply Changes or Apply Changes and Checkout to configure the billing information.

## Move a Multi-Region Cluster

Use the following procedure to move nodes to one or more regions in an `M10` or larger multi-region cluster:

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Open the configuration menu.

   Click Edit Config and select the cluster that you want to move from the drop-down menu.

   Alternatively, if you are already viewing the specific cluster, click Configuration.

3. In the Cloud Provider & Region view, review the current multi-region configuration options.

   For a given region, click the currently selected Region and pick a new region from the drop-down list. If you modify the Preferred region, the Atlas cluster calls for one or more elections to select a new [primary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) in the selected region. See [Test Primary Failover](https://www.mongodb.com/docs/atlas/tutorial/test-resilience/test-primary-failover.md#std-label-test-failover) for instructions on testing your application response to a replica set election before changing the Preferred cluster.

   To change the number of nodes Atlas deploys to a given region, increase or decrease the Number of Nodes value. The total number of nodes across the Preferred region and all Electable regions must be an odd number.

4. Click Confirm & Deploy.
