Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Migrate Deployments

To move your applications to the cloud, you can migrate data from your existing MongoDB deployments into MongoDB Atlas. The following table helps you choose between different tools for migrating common deployment configurations into MongoDB Atlas.

Deployment Configuration Migration Strategy
Your data is in Ops Manager and your network allows flexibility in ingress rules. Pull data into Atlas from Ops Manager. In this type of Live Migration, MongoDB Atlas requires access to the source deployment in Ops Manager through the deployment’s firewall.
Your data is in Ops Manager and your network doesn’t allow flexibility in ingress rules. Push your data into Atlas from Ops Manager. In this type of Live Migration, MongoDB Atlas receives data from Ops Manager without requiring access through the firewall.
Your data is in MongoDB Community and your network doesn’t allow flexibility in ingress rules. Push your MongoDB Community data into Atlas after adding your Community deployment to Ops Manager. In this type of Live Migration, MongoDB Atlas receives data from Ops Manager without requiring access through the firewall.
Your data is in a MongoDB deployment and you don’t have access to the oplog. Use mongorestore to run a self-managed migration. To learn more, see Seed with mongorestore.

You can also migrate a MongoDB deployment from one Ops Manager project to another project. To learn more, see Migrate a MongoDB Deployment to a New Project.