Docs Menu

Choose a Data Import and Migration Tool

You can bring data from existing MongoDB deployments, JSON, or CSV files into Atlas using either:

  • live migration tools where Atlas assists you, or
  • tools for a self-guided migration of data from your existing deployments into Atlas.
Note
Serverless Instances are in Preview

To move data to a serverless instance, you can use Compass to export and import data, or migrate data with self-managed tools.

To learn more about serverless instance limitations, see Serverless Instance Limitations.

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

Cluster Configuration
Import Strategy
A replica set from a Cloud Manager or Ops Manager deployment.
Live migrate a replica set from Cloud Manager or Ops Manager to Atlas. In this Live Migration mode, Cloud Manager or Ops Manager pushes data to Atlas using a secure link-token without requiring access through the firewall.
A sharded cluster from a Cloud Manager or Ops Manager deployment.
Live migrate a sharded cluster from Cloud Manager or Ops Manager to Atlas. In this Live Migration mode, Cloud Manager or Ops Manager pushes data to Atlas using a secure link-token without requiring access through the firewall.
A standalone MongoDB node from a Cloud Manager or Ops Manager deployment.
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 it to Atlas. In this Live Migration mode, Cloud Manager or Ops Manager pushes data to Atlas using a secure link-token without requiring access through the firewall.
A replica set deployment.

Live migrate a replica set into Atlas. In the General Live Migration mode, Atlas requires access to the source deployment through the deployment's firewall.

Before you migrate to Atlas, upgrade the source cluster to MongoDB 4.0 or later. Provide the hostname of the primary to the Live Migration service. If the cluster runs with authentication, allow read access to the primary node's oplog. To learn more, see Pre-Migration Validation.

A sharded cluster deployment.

Choose a data migration option based on the amount of downtime your application can tolerate:

  • If the application requres a near-continuous uptime, contact MongoDB Support and share your uptime requirements and cluster configuration.
  • If the application can tolerate a short period of downtime, live migrate a sharded cluster into Atlas. In the General Live Migration mode, Atlas requires access to the source deployment through the deployment's firewall.
  • If the application can tolerate a longer downtime, or if your cluster runs a MongoDB version that is no longer supported, use mongorestore and back up the cluster with database dumps.
A standalone MongoDB deployment.

Choose one of the following data migration options:

  • If you can convert the standalone to a single-node replica set, live migrate a replica set into Atlas . In the General Live Migration mode, 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.

Before you migrate to Atlas, upgrade the deployment to MongoDB 4.0 or later. If the deployment runs with authentication, allow read access to the primary node's oplog.

A shared multi-tenant cluster, or a cluster where you have no access to the oplog.

Use mongorestore.

If the cluster runs with authentication, allow read access to the primary.

A standard "single shard" sharded cluster MongoDB deployment in Compose.

Live Migrate the cluster to Atlas.

Before you connect from the Live Migration service, enable the oplog proxy and specify the oplog proxy's hostname and credentials to Atlas. To learn more, see Pre-Migration Validation.

Tip
Give Feedback
© 2021 MongoDB, Inc.

About

  • Careers
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2021 MongoDB, Inc.