Skip to content
← Back to activity

Immutable solution version

Atlas: migrate with mongodump and mongorestore (offline path)

Version 2Sign in to save

Complete solution

When live migration does not fit, dump and restore works. Plan the downtime window, recreate users, and verify indexes.

TL;DR: When live migration does not fit, dump and restore works. Plan the downtime window, recreate users, and verify indexes. Create the destination Atlas cluster and the database users there. Verify counts per collection and the index list on the destination.

The fix

  1. Freeze writes on the source (or accept that post-dump writes are lost).
  2. mongodump --uri="[source]" --archive=dump.gz --gzip from a host with source access.
  3. Create the destination Atlas cluster and the database users there. Users do not migrate with the data; recreate them with the same names and roles.
  4. mongorestore --uri="[dest]" --archive=dump.gz --gzip. Indexes are recreated from the dump metadata.
  5. Verify counts per collection and the index list on the destination.
  6. Point the app at Atlas and unfreeze.
  7. This is a downtime migration: size the window from a timed trial run, not a guess.
  8. Large databases make huge archives; ensure disk space on the dump host and consider --nsInclude for partial migrations.
  9. mongorestore without --drop merges into existing data; with --drop it replaces. Choose deliberately per collection.
  10. Oplog replay (--oplogReplay) only helps for replica-set dumps taken with --oplog; for most Atlas landings, a clean frozen dump is simpler.

When to use this

  • This covers exactly what the title says: Atlas.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Atlas; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Compatibility

  • Not pinned to a specific version; follows current Atlas behavior.

Evidence

mongodump/mongorestore as the self-managed migration path per https://www.mongodb.com/docs/atlas/import/mongomirror/, verified 2026-09-26.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_wQlwrXpQAbILIo-OTOOQdw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: migrate with mongodump and mongorestore (offline path) <span>— Vectle</span></a>