Navigation
You were redirected from a different version of the documentation. Click here to go back.

Migrate from Cloud Manager to Atlas

Overview

To live migrate data from the Cloud Manager-managed deployments to clusters in Atlas, you:

  1. Prepare a cluster in MongoDB Atlas.
  2. Provision a migration host in Cloud Manager and connect Cloud Manager to Atlas.
  3. Start the live migration process in Atlas.

You begin the process in Atlas, by running the live migration wizard. Depending on the stage in the process, you perform the live migration steps either in Atlas or in Cloud Manager. See Workflow for Live Migration.

To live migrate your MongoDB Community deployments to Atlas using Cloud Manager, see Migrate a MongoDB Community Deployment to Atlas.

Restrictions

You can’t select an M0 free cluster or M2/M5 shared cluster as the source or target for Live Migration. To migrate data from an M0 free cluster or M2/M5 shared cluster to a paid cluster, see Modify a Cluster.

Prerequisites

Before you begin the live migration process, follow these prerequisites.

Consider Configuring a VPC Peering Connection or Private Endpoints

The following table lists the current support status for VPC peering and private endpoints for source and target clusters that you live migrate to MongoDB Atlas.

Note

If you choose not to use VPC peering or private endpoints, the live migration process runs over public IP addresses that you add to the MongoDB Atlas project’s IP access list as part of the live migration procedure. To learn more, see Live Migrate Your Data from Ops Manager or Cloud Manager.

Cloud Provider VPC Peering Private Endpoints
Azure check icon check icon star icon
AWS check icon check icon star icon
GCP check icon check icon star icon

Important

star icon Sharded clusters, multi-region clusters, and multi-cloud clusters don’t support live migration through private endpoints. Private endpoints are supported ONLY for live migration of replica sets deployed within a single cloud provider and single region.

To enable private endpoints with live migration on Azure, AWS, or GCP on replica sets deployed within a single cloud provider and single region:

To enable VPC peering with live migration on Azure, AWS, or GCP on replica sets or sharded clusters:

Create a Cluster in Atlas

Perform these tasks in Atlas:

Workflow for Live Migration

The following diagram describes the stages in the live migration workflow.

"To live migrate your deployment to Atlas, generate a link-token, provision a migration host, and start live migration."

The stages in the live migration workflow are:

  • Stage 1: Link with Atlas. Perform this step in Atlas, after provisioning a cluster.
    1. In the left-side panel of your organization’s page in MongoDB Atlas, click Live Migration.
    2. Select Migrate from Ops Manager or Cloud Manager and start the live migration wizard.
    3. In the Generate Link-Token step of the wizard, create the link-token. You will use this link-token in the next stage.
  • Stage 2: Provision Migration Host.
    • In Cloud Manager, provision a Migration Host. A migration host is a dedicated MongoDB Agent that orchestrates the live migration process from Cloud Manager to Atlas.
    • In the Live Migration: Connect to Atlas section of your Cloud Manager organization’s Settings page, select Connect to Atlas and enter the the link-token that you created in Atlas.
  • Stage 3: Start the Migration. In Atlas, follow the steps in the wizard to start the live migration process.

To learn more, see Live Migrate Your Data from Ops Manager or Cloud Manager.

Supported Platforms

Live migration to Atlas is supported for all platforms on which you can provision a migration host. Provisioning of the migration host is supported on all platforms except for Windows or macOS. You can still live migrate your data from a Windows-based deployment to Atlas if you provision your migration host on one of its supported platforms. You can’t live migrate your data from a macOS-based deployment to Atlas.