Navigation

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.

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

Note

If you have a source cluster with authentication and wish to use an import strategy which includes using mongorestore with the --oplogReplay option, you must delete the admin directory from the dump directory created by mongodump. The admin directory contains database user information that you can't add to a Atlas cluster with mongorestore.

Cluster Configuration
Import Strategy

Use Live Migrate.

You must provide the hostname of the primary to the Live Migrate tool.

If the cluster is running a MongoDB version earlier than 2.6, you must first upgrade it to at least MongoDB 2.6.

You must have access to the primary node's oplog. If the cluster runs with authentication, you must have credentials that provide read access to the primary and its oplog.

See Pre-Migration Validation for the full list of migration requirements.

A sharded cluster with multiple shards.

If your application can tolerate a short period of downtime, use Live Migrate. The source cluster must run MongoDB 3.6. If the sharded cluster is not running MongoDB 3.6, you must upgrade it to MongoDB 3.6.

If the source cluster enforces authentication, specify a user to Atlas that exists on every shard and the config server replica set. The user must have permission to:

  • Stop or start the sharded cluster balancer.
  • Read all databases and collections on the host.
  • Read the oplog on the host.

See Pre-Migration Validation for the full list of migration requirements.

If near-continuous uptime is a requirement, please contact MongoDB. From the Atlas UI, click Support. Fill out a Support ticket, noting your uptime requirements and cluster configuration in the More details text entry.

If some downtime is OK and your sharded cluster does not run a supported MongoDB version, you may use mongodump and mongorestore. See Seed with mongorestore and Backup Sharded Cluster with Database Dumps.

A "single shard" sharded cluster in Compose. This is the standard configuration for new MongoDB deployments in Compose.

Use Live Migrate.

You must enable the oplog proxy.

You must specify the hostname and credentials for the oplog proxy when connecting from Live Migrate.

See Pre-Migration Validation for the full list of migration requirements.

Tip
See also:
A standalone MongoDB node.

Convert the standalone MongoDB node to a single-node replica set and then use the Live Migration service.

If the standalone is running a MongoDB version earlier than 2.6, you must first upgrade it to at least MongoDB 2.6.

If you are running with authentication enabled, you must have credentials that provide read access to the primary and its oplog.

If you can't convert the standalone to a replica set, use mongodump and mongorestore. See Seed with mongorestore.

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

Use mongodump and mongorestore. See Seed with mongorestore.

If you are running with authentication enabled, you must have credentials that provide read access to the primary.

Atlas has built-in support for scaling an M0 Free Tier cluster to an M10+ paid cluster. Alternatively, use mongodump and mongorestore to copy data from an M0 Free Tier cluster to an M10+ cluster. See Seed with mongorestore.

Give Feedback