Atlas Live Migration Service - AWS Prescriptive Guidance

Atlas Live Migration Service

The Atlas Live Migration Service initiates an initial copy of the data from the source database (only MongoDB databases), monitors for any subsequent changes, and ensures synchronization until it's time to cut over to MongoDB Atlas. Throughout this process, applications can maintain their normal read and write operations on the source database. When you're ready to perform the cutover, the connection string in the application is updated from the source database to the Atlas cluster, which completes the migration.

A typical migration workflow consists of the following steps:

Step 1. Prepare

  • Assess the current MongoDB data size and workload. For instructions, see Identify Application Workload in the MongoDB documentation.

  • Determine the size of the Atlas cluster on AWS.

  • Prepare for migration and cutover plans.

Step 2. Deploy

  • Set up a new environment on AWS for the MongoDB Atlas cluster, based on the sizing you determined in step 1.

  • Configure network access. For instructions, see Configure IP Access List Entries in the MongoDB documentation.

  • Configure security for the destination cluster. For instructions, see Configure Security Features for Clusters in the MongoDB documentation.

Step 3. Migrate

  • Configure the source and destination in the Atlas Live Migration Service.

  • Run the migration.

  • Cut over to MongoDB Atlas on AWS.

For more information about this migration option, see Migrate a self-hosted MongoDB environment to MongoDB Atlas on AWS.

For MongoDB 6.0.8 and later

If both your source and destination clusters are running MongoDB 6.0.8 or a later version, you can use a guided live migration option (pull or push) to migrate your data from a source cluster to an Atlas MongoDB cluster:

For earlier MongoDB versions

To migrate MongoDB versions earlier than 6.0.8, use one of the migration strategies discussed in the MongoDB documentation.