MongoDB Atlas to Amazon DocumentDB: Migration Guide and Comparison

MongoDB Atlas to Amazon DocumentDB is one of the most nuanced database migrations you can undertake. On the surface it looks straightforward — DocumentDB speaks the MongoDB wire protocol, so your drivers connect. The complexity lives in the gaps between what DocumentDB advertises and what MongoDB actually delivers.

This guide does not sugarcoat the compatibility story. We will cover what works, what does not, when DocumentDB is a reasonable choice, and when you should stay on Atlas or consider a different AWS-native option.

We are an AWS Select Tier Consulting Partner, and we have handled Atlas-to-DocumentDB migrations. The advice here reflects production experience, not vendor documentation.

The Compatibility Gap: What DocumentDB Does Not Support

This is the section most vendor comparisons skip. Read it before you start planning a migration.

The bottom line on compatibility: For CRUD-heavy applications that do not use Atlas Search, complex aggregations, or change streams at the database level, DocumentDB’s wire protocol compatibility is adequate. For applications that use these features, you are not migrating to DocumentDB — you are rewriting parts of your application.

When DocumentDB Makes Sense

DocumentDB is a reasonable choice in specific situations:

• AWS-only vendor requirement. Some regulated environments or enterprise procurement policies require all data services to be native AWS services. Atlas runs on AWS infrastructure but is managed by MongoDB Inc., not AWS. DocumentDB satisfies this constraint.
• Operational simplicity over feature completeness. If your team finds Atlas’s operational model complex (cross-cloud replication, Atlas alerts, Atlas Data Federation), DocumentDB integrates more naturally into your existing AWS tooling — CloudWatch, VPC security groups, IAM authentication.
• Your workloads fit the compatibility matrix. If your application is a document store for structured JSON with standard CRUD operations and simple queries, DocumentDB’s supported feature set may be entirely sufficient.
• Cost modeling favors DocumentDB. For low-I/O workloads, DocumentDB’s unbundled pricing can be cheaper than Atlas.

When Atlas Is the Better Choice

Atlas is the stronger option when:

• You use Atlas Search for full-text or relevance-based queries — there is no DocumentDB equivalent. The nearest AWS option is OpenSearch Service, which requires a separate migration.
• You use Atlas Vector Search for semantic similarity search or RAG pipelines.
• You use MongoDB 6.0 or later features.
• Your application relies on change streams at the database or deployment level.
• You use Atlas App Services, Atlas Data Federation, or Atlas Charts.
• You need multi-cloud replication (Atlas runs on AWS, GCP, and Azure; DocumentDB is AWS-only).

Cost Comparison

DocumentDB uses an unbundled pricing model. The instance price is only part of the cost.

Worked example: A db.r5.large with 100 GB of data and 500 million I/Os per month costs: $196 (instance) + $10 (storage) + $100 (I/Os) = $306/month. The comparable Atlas M30 with 100 GB NVMe storage is approximately $209/month all-inclusive.

Write-heavy workloads can make DocumentDB significantly more expensive than Atlas pricing suggests. Model your I/O before assuming cost parity.

Migration Approach: Atlas to DocumentDB with AWS DMS

Step 1: Compatibility Audit

Run your queries and aggregation pipelines against the DocumentDB compatibility matrix. Check for $lookup with subqueries, $unionWith, custom $accumulator or $function operators, and any full-text or vector search usage. Fix or rewrite incompatible patterns before proceeding.

Step 2: Driver Compatibility

For best compatibility with DocumentDB, use the MongoDB 3.x driver rather than 4.x or later. The 4.x driver introduced connection behavior changes that can cause issues with DocumentDB’s connection handling. Check the AWS documentation for your language’s recommended driver version.

Step 3: Provision DocumentDB Cluster

Create your DocumentDB cluster inside your VPC. DocumentDB does not support public endpoints — your application must connect from within the VPC or via a VPN/Direct Connect. Enable TLS (required) and download the AWS-provided CA certificate bundle for your connection string.

Step 4: Migrate Data with AWS DMS

Configure AWS DMS with your Atlas cluster as the source and your DocumentDB cluster as the target. Use full-load mode for the initial migration, then enable ongoing replication (change data capture) to keep DocumentDB in sync while you test your application. DMS supports MongoDB as a source natively.

Validate document counts and spot-check data integrity after the full load completes.

Step 5: Update Connection Strings

DocumentDB connection strings use mongodb:// format but require the retryWrites=false parameter — DocumentDB does not support retryable writes in the same way MongoDB does. Example:

mongodb://user:pass@docdb-cluster.cluster-xxxx.us-east-1.docdb.amazonaws.com:27017/?ssl=true&ssl_ca_certs=rds-combined-ca-bundle.pem&retryWrites=false

Step 6: Application Testing and Cutover

Run your full integration test suite against DocumentDB. Pay particular attention to any code paths that use aggregation pipelines, change streams, or text queries. Once validated, cut over your application by updating the connection string, then decommission the Atlas cluster.

A Note on Full-Text Search

If your application uses MongoDB Atlas Search, you have two AWS options:

1. Amazon OpenSearch Service — A dedicated search cluster running OpenSearch (Elasticsearch-compatible). Provides full-text search, facets, relevance tuning, and vector k-NN search. Requires maintaining a separate service alongside DocumentDB.
2. Amazon OpenSearch Serverless — Serverless version with no cluster management. Good for variable query volumes.

Neither is as seamlessly integrated as Atlas Search, which runs embedded within your MongoDB cluster. Factor this operational complexity into your migration timeline.

Ready to Migrate?

FactualMinds handles database migrations to AWS, including Atlas-to-DocumentDB migrations with DMS and post-migration optimization.

Talk to our team about your database migration or learn more about our AWS RDS and database consulting services.