The following table covers the best import strategy for common cluster
configurations.

Note

If have a source cluster with authentication and you 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 which you cannot add to an Atlas cluster with
mongorestore.

If your application can tolerate a short period of downtime,
use Live Migrate. The source
cluster must run MongoDB 3.4, or 3.6. If the sharded cluster is
not running MongoDB 3.4 or 3.6, you must upgrade it to
MongoDB 3.4 or 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:

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.