To live migrate data from the Cloud Manager-monitored deployments to clusters in Atlas, you:
Add your deployment to Cloud Manager if you haven't already done so.
Add credentials to Monitoring.
Prepare a cluster in MongoDB Atlas.
Provision a migration host in Cloud Manager and connect Cloud Manager to Atlas.
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.
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.
The list of supported platforms depends on which type of live migration you are using:
For live migrations of MongoDB 6.0.8+ clusters monitored by Cloud Manager to Atlas, see mongosync platforms to review the list of supported platforms for the migration host.
For live migrations of source clusters running MongoDB versions 4.4.x or 5.0.x (FCV), the live migration to Atlas is supported for all platforms on which you can provision a migration host.
Provisioning of the migration host is not supported on 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.
Before you begin the live migration process, follow these prerequisites.
Follow the procedure to Add MongoDB Processes.
When you add your deployment to Cloud Manager, you need to add credentials for Monitoring only, not for Automation or Backup. Adding your deployment for Monitoring imports your deployment's metadata into Cloud Manager to help with the live migration process. It doesn't import your deployment's actual data. To learn more about authentication credentials, see Authentication Use Cases.
To add credentials for Monitoring:
Create the credentials to the deployment. See Required Access for Monitoring.
Add the credentials based on your project's authentication mechanism. See Add Authentication Credentials to your Deployment.
If you're adding your MongoDB deployment to monitoring so that you can live migrate it to Atlas, you don't need to add credentials for Automation and Backup. To learn more, see Authentication Use Cases.
For information about support for VPC peering connections and private endpoints, see the MongoDB Atlas documentation for your type of live migration:
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.
Perform these tasks in Atlas:
The stages in the live migration workflow are:
Stage 1: Link with Atlas. Perform this step in Atlas, after provisioning a cluster.
In the left-side panel of your organization's page in MongoDB Atlas, click Live Migration.
Select Migrate from Ops Manager or Cloud Manager and start the live migration wizard. Even though the UI mentions Ops Manager, depending on the type of the source cluster you are migrating to Atlas, only Cloud Manager is supported with that source cluster. Specifically, for source clusters running MongoDB 6.0.8 or later, you can monitor them in Cloud Manager only but not in Ops Manager.
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 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.