Migrating from a self-managed MongoDB database to Amazon DocumentDB requires careful planning, data extraction, secure file transfer, namespace mapping, restoration, and validation.<\/span><\/p>\n This guide explains how to migrate the The migration uses MongoDB Database Tools (mongodump and mongorestore), rsync for transferring backup files, TLS for encrypted connectivity, and a dry-run restore to validate the migration command before making changes.<\/span><\/p>\n Amazon DocumentDB is a fully managed document database service from Amazon Web Services that supports MongoDB-compatible APIs.<\/p>\n It allows developers to use many familiar MongoDB drivers, tools, and document-oriented data structures while AWS manages infrastructure-related operations.<\/p>\n Amazon DocumentDB provides capabilities such as managed backups, high availability, monitoring, and storage management.<\/p>\n However, Amazon DocumentDB is not identical to MongoDB. Feature compatibility, supported operators, index behavior, and application functionality can differ depending on the target engine version.<\/p>\n AWS<\/a><\/span> maintains an official compatibility reference that should be reviewed before migration<\/p>\n Organizations may consider migrating MongoDB to Amazon DocumentDB to simplify database operations and take advantage of AWS-managed infrastructure.<\/p>\n Potential benefits include:<\/p>\n Reduced infrastructure management: Less responsibility for manually maintaining database infrastructure.<\/p>\n<\/div>\n<\/div>\n<\/li>\n High availability: Managed deployment options with replication and failover capabilities.<\/p>\n<\/div>\n<\/div>\n<\/li>\n Automated backups: AWS-managed backup and recovery functionality.<\/p>\n<\/div>\n<\/div>\n<\/li>\n AWS integration: Connectivity with services such as Amazon EC2, AWS IAM, Amazon CloudWatch, and AWS networking.<\/p>\n<\/div>\n<\/div>\n<\/li>\n Operational scalability: Managed infrastructure options to accommodate changing workloads.<\/p>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n These benefits should be evaluated against application compatibility, performance requirements, and projected costs.<\/p>\n Source environment<\/b><\/p>\n Destination environment<\/b><\/p>\n Before starting the migration, confirm the following.<\/span><\/p>\n Log in to the source MongoDB server and execute the following command.<\/span><\/p>\n The command prompts for the password.<\/span><\/p>\n After a successful dump, the directory should resemble:<\/span><\/p>\n \/usr\/local\/src\/migrate\/<\/span><\/p>\n \u2514\u2500\u2500 dump\/<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u2514\u2500\u2500 sourcedb\/<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u251c\u2500\u2500 collection1.bson<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u251c\u2500\u2500 collection1.metadata.json<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u251c\u2500\u2500 collection2.bson<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u251c\u2500\u2500 collection2.metadata.json<\/span><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u2514\u2500\u2500 …<\/span><\/p>\n Actual filenames depend on the collections in the database. The BSON files contain the document data, while the metadata files can contain collection options and index definitions.<\/span><\/p>\n On the destination server, ensure the target directory exists and use Verify the TLS certificate bundle. Confirm that the certificate bundle exists:<\/span><\/p>\n Use the current AWS-provided CA bundle appropriate for Amazon DocumentDB. Keep the bundle readable by the migration account and do not disable certificate verification to bypass TLS errors.<\/span><\/p>\n Use the target administrator account and a TLS-enabled connection:<\/span><\/p>\n Enter the password when prompted. After connecting, check the available databases and confirm that the account has the permissions required for the restore.<\/span><\/p>\n The source database is named sourcedb, while the destination database must be named destinationdb. The following namespace mapping handles that change:<\/span><\/p>\n –nsTo=”destinationdb.*”<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The wildcard preserves each collection name while changing its database name. This mapping does not rename the individual collections or transform document fields. It only changes the namespaces used by the restore operation.<\/span><\/p>\n Before modifying production data, execute a dry run on destination server.<\/span><\/p>\n Enter the destination password when prompted.<\/span> A dry run checks and reports the restore plan without importing the documents. The –drop option is included to document the intended final restore behavior, but it does not actually drop collections during a supported dry run.<\/span><\/p>\n Once the dry run, backup integrity checks, target connectivity, and change-control approvals are complete, run the actual restore. The following command omits –dryRun, so it will perform real changes:<\/span><\/p>\n Enter the password when prompted.<\/span><\/p>\n A completed mongorestore command does not by itself prove that the migration is correct. Validate the result at multiple levels.<\/span><\/p>\n Connect to Amazon DocumentDB using mongosh:<\/span><\/p>\n Then run:<\/span><\/p>\n use destinationdb<\/span><\/p>\n show collections<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Confirm that the expected collections exist.<\/span><\/p>\n After database-level checks, verify the application against the destination database.<\/span><\/p>\n Test:<\/span><\/p>\n Keep the source available and retain a rollback plan until the destination has passed the required validation.<\/span><\/p>\n Migrating MongoDB to Amazon DocumentDB using mongodump, rsync, and mongorestore is a practical approach for controlled migrations.<\/span><\/p>\n The essential stages are to create a reliable source backup, transfer it securely, map sourcedb to destinationdb, validate the restore plan, execute the restore, and verify data integrity and application compatibility.<\/span><\/p>\n A successful MongoDB migration<\/a> requires careful planning, compatibility checks, secure data transfer, and thorough validation. Businesses planning to move their databases to AWS can work with Skynats<\/a> for migration planning, cloud infrastructure management<\/a>, and post-migration support.<\/p>\nsourcedb<\/code> database from a self-managed MongoDB server to an Amazon DocumentDB cluster, using destinationdb<\/code><\/span> as the destination database..<\/span><\/p>\nWhat Is Amazon DocumentDB?<\/h2>\n
Why Migrate MongoDB to Amazon DocumentDB?<\/h2>\n
\n
Migration overview<\/b><\/h3>\n
\n
\n
Prerequisites<\/b><\/h2>\n
Source MongoDB<\/b><\/h3>\n
\n
Destination server<\/b><\/h3>\n
\n
Create a MongoDB dump on the source server<\/b><\/h2>\n
\n\n
\n mongodump\u00a0 –host=”localhost” –port=27017 –username=”sourcedbuser”\u00a0 –password –authenticationDatabase=”sourcedb” –db=”sourcedb” –out=”\/usr\/local\/src\/migrate\/dump”<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Explanation of the parameters<\/b><\/h3>\n
\n\n
\n Parameter<\/b><\/td>\n Purpose<\/b><\/td>\n<\/tr>\n \n –host<\/span><\/td>\n MongoDB server hostname<\/span><\/td>\n<\/tr>\n \n –port<\/span><\/td>\n MongoDB connection port<\/span><\/td>\n<\/tr>\n \n –username<\/span><\/td>\n Source database username<\/span><\/td>\n<\/tr>\n \n –password<\/span><\/td>\n Prompts for the password<\/span><\/td>\n<\/tr>\n \n –authenticationDatabase<\/span><\/td>\n Database where the user authenticates<\/span><\/td>\n<\/tr>\n \n –db<\/span><\/td>\n Database to back up<\/span><\/td>\n<\/tr>\n \n –out<\/span><\/td>\n Directory where dump files are written<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Expected directory structure<\/b><\/h3>\n
Transfer the dump to the destination server<\/b><\/h2>\n
rsync<\/code> to transfer the MongoDB backup securely from the source server.
\n<\/span>\u00a0command:<\/span><\/p>\n\n\n
\n rsync -avz root@sourceip:\/usr\/local\/src\/migrate\/dump\/\u00a0 \/var\/www\/mongorestore\/dump\/<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Prepare the Amazon DocumentDB destination<\/b><\/h2>\n
\n\n
\n ls -l \/root\/global-bundle.pem<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Verify database authentication<\/b><\/h3>\n
\n\n
\n mongosh –host=”<\/span>destination-db.cluster-cbpxrmfy65hz.ap-south-1.docdb.amazonaws.com:27017<\/span>” –username=”admin00000″ –password –authenticationDatabase=”admin”\u00a0 –tls –tlsCAFile=”\/root\/global-bundle.pem” –retryWrites=false<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Map the source database to the destination database<\/b><\/h2>\n
\n\n
\n –nsFrom=”sourcedb.*”<\/span><\/p>\n Perform a dry-run restore<\/b><\/h2>\n
\n\n
\n mongorestore –host=”<\/span>destination-db.cluster-cbpxrmfy65hz.ap-south-1.docdb.amazonaws.com:27017<\/span>” –username=”admin00000″ –password –tls –tlsCAFile=”\/root\/global-bundle.pem” –authenticationDatabase=”admin” –retryWrites=false –nsFrom=”sourcedb.*” –nsTo=”destinationdb.*” –drop –dryRun “\/var\/www\/mongorestore\/dump\/”<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Restore the data into Amazon DocumentDB<\/b><\/h2>\n
\n\n
\n mongorestore –host=”<\/span>destination-db.cluster-cbpxrmfy65hz.ap-south-1.docdb.amazonaws.com:27017<\/span>” –username=”admin00000″ –password –tls –tlsCAFile=”\/root\/global-bundle.pem” –authenticationDatabase=”admin” –retryWrites=false –nsFrom=”sourcedb.*” –nsTo=”destinationdb.*” –drop “\/var\/www\/mongorestore\/dump\/”<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Validate the restored database<\/b><\/h2>\n
Verify the destination database<\/b><\/h3>\n
\n\n
\n mongosh –host=”<\/span>destination-db.cluster-cbpxrmfy65hz.ap-south-1.docdb.amazonaws.com:27017<\/span>” –username=”admin00000″ –password –authenticationDatabase=”admin”\u00a0 –tls –tlsCAFile=”\/root\/global-bundle.pem” –retryWrites=false<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n \n\n
\n show dbs<\/span><\/p>\n Validate application functionality<\/b><\/h3>\n
\n
Conclusion<\/b><\/h2>\n
Need Expert Help Migrating MongoDB to Amazon DocumentDB?<\/h2>\n