You can bring data from existing MongoDB deployments,
files into deployments in Atlas using either:
- live migration where Atlas assists you, or
- tools for a self-guided migration of data from your existing deployments into Atlas.
The following table discusses how to choose between different tools for data migration and import for common cluster configurations.
Source Cluster Configuration
A MongoDB deployment that is managed by Cloud Manager or Ops Manager.
A MongoDB deployment that is not managed by Cloud Manager or Ops Manager.
Use live migration (pull) where Cloud Manager or Ops Manager pulls data from the source deployment and requires access to the source deployment through the deployment's firewall.
A shared multi-tenant cluster, or a cluster where you have no access to the oplog, or a cluster that runs a MongoDB version that is no longer supported.
A replica set in AWS.
- To move data to a serverless instance, use Compass to export and import data, or migrate data with self-managed tools. To learn more, see Serverless Instance Limitations.
- To load data into a new cluster in Atlas, see Load Sample Data.
- To make a copy of your cluster for testing purposes, see MongoDB Backup Methods.
- If the application that you want to migrate requires a near-continuous uptime, contact MongoDB Support and share your uptime requirements and cluster configuration.