Choose a Data Import or Migration Tool

On this page

List of Tools for Migrating to Atlas

You can bring data from existing MongoDB deployments, JSON, or CSV 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.

Note

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.

List of Tools for Migrating to Atlas

The following table discusses how to choose between different tools for data migration and import for common cluster configurations.

Tip

If you want to make a copy of your cluster for testing purposes, see MongoDB Backup Methods.

Source Cluster Configuration	Import Strategy
A replica set, sharded cluster, or standalone MongoDB node that are managed by Cloud Manager or Ops Manager.	Use live migration where Cloud Manager or Ops Manager pushes data to Atlas using a secure link-token without requiring access to the source cluster through the cluster's firewall. To locate push type migration in the Atlas user interface, in the left-side panel of your organization's page, go to Live Migration to Atlas and select Migrate from Ops Manager or Cloud Manager. Replica Set: Live migrate (push) a replica set from Cloud Manager or Ops Manager to Atlas. Sharded Cluster: Live migrate (push) a sharded cluster from Cloud Manager or Ops Manager to Atlas. Standalone MongoDB node: Convert the standalone to a replica set in Ops Manager or convert the standalone to a replica set in Cloud Manager and then live migrate (push) it to Atlas.
A replica set, sharded cluster, or standalone MongoDB node deployment that are not managed by Cloud Manager or Ops Manager.	Use live migration where Cloud Manager or Ops Manager pulls data from the source deployment and requires access to the source deployment through the deployment's firewall. To locate pull type live migration in the Atlas user interface, in the left-side panel of your organization's page, go to Live Migration to Atlas and select General Live Migration. Replica Set that is not managed by Cloud Manager or Ops Manager: Live migrate (pull) a replica set into Atlas. Sharded Cluster that is not managed by Cloud Manager or Ops Manager: If the application can tolerate a short period of downtime, live migrate (pull) a sharded cluster into Atlas. If the application can tolerate a longer downtime, or if your cluster runs a MongoDB version that is no longer supported, use use mongorestore and back up the cluster with database dumps. If the application requires a near-continuous uptime, contact MongoDB Support and share your uptime requirements and cluster configuration. Standalone MongoDB deployment that is not managed by Cloud Manager or Ops Manager: If you can convert the standalone to a single-node replica set, live migrate (pull) a replica set into Atlas. Atlas requires access to the source deployment through the deployment's firewall. If you can't convert the standalone to a replica set, use mongorestore.
A shared multi-tenant cluster, or a cluster where you have no access to the oplog.	Use mongorestore.
A standard "single shard" sharded cluster MongoDB deployment in Compose.	Migrate from Compose to MongoDB Atlas.

What is MongoDB Atlas? →