Migrate MongoDB.
Zero downtime.

Exodus deploys as a command-aware MongoDB gateway with parallel pre-test capture, safe mirroring, BSON batch movement, validation, and gateway-level rollback.

Supported Systems

MongoDB AtlasMongoDB AtlasAmazon DocumentDBAmazon DocumentDBAzure Cosmos DBAzure Cosmos DBGoogle CloudGoogle CloudReplica SetsReplica SetsSharded ClustersSharded ClustersSelf-HostedSelf-Hosted
See how it works

How it works

Follow each phase of a zero-downtime MongoDB migration.

Pre-test mirrors command traffic while apps still use the source. Analyze cuts clients over to Exodus, then compare, test, migrate, roll back, or commit through the gateway.

Web apps
Workers
Queues
Source MongoDB
Exodus
Observability
Parallel Capture

Mirror MongoDB traffic before Exodus enters the request path.

Applications keep talking directly to the source MongoDB deployment. A parallel traffic copy feeds Exodus and Observability so command policy, mirroring, and rollback behavior can be tested first.

Apps still hit sourceParallel traffic copyTelemetry capture
Migration path

Implementation documentation

Use these references when you are ready to configure endpoints, point traffic at Exodus, prepare a workflow, approve execution, monitor progress, and roll back or complete the migration.

Migration runbook

Phase-by-phase operating guide for source, target, interlay, workflow setup, approval, monitoring, rollback, and completion.

Migration API reference

Guided Redis workflow endpoints plus raw migration APIs for analysis, compatibility, tests, traffic controls, metrics, and rollback.

MongoDB endpoint setup

Connection shape, topology inventory, command policy, collection movement planning, validation, and preview notes.

Product Features

Source-backed MongoDB migration details

These details come from the MongoDB gateway, analyzer, metadata collectors, and BSON migration state machine currently present in the codebase.

MongoDB wire parsing

The gateway parses OP_MSG and OP_QUERY frames, extracts command documents, and tracks request shape before forwarding.

Command classification

Reads, writes, and unknown commands are classified so routing and policy behavior can be conservative by default.

Policy enforcement

Strict and production presets can block destructive commands such as drop, dropDatabase, compact, fsync, and repairdb.

Mirror comparison

Safe mirrored commands can compare primary and mirror responses, while transactions and session lifecycle commands are skipped.

Collection batches

The data mover lists non-system databases and collections, then extracts documents sorted by _id into bounded BSON batches.

Conflict modes

Target writes support direct insert, replace-style upsert, and merge behavior for document conflicts.

Topology metadata

Endpoint collectors include replication, sharding, balancer, WiredTiger, profiler, indexes, users, and collection metadata.

Shape analytics

MongoDB request analysis tracks command and pipeline patterns so teams can spot risky workloads before migration.

Rollout Patterns

Preview rollout patterns for MongoDB

The MongoDB architecture uses the same gateway primitives as the rest of Exodus, but customer-facing migration execution should be planned as preview until the full page is launched.

observe first

Shadow validation

Mirror safe read and write-shaped traffic to target, compare responses, and record divergence before cutover decisions.

batch by collection

Collection backfill

Move BSON data collection by collection, preserving document identity through _id sorted extraction and conflict rules.

preview workflow

Gateway cutover

Use interlay routing state to shift MongoDB requests toward target while keeping source available as a fallback.

Ready to plan a MongoDB migration?

We work with teams to map topology, command policy, collection movement, validation signals, and rollback expectations before a MongoDB POC.

Compare endpoints