Docs Home → MongoDB Ops Manager
Change the Version of MongoDB
On this page
You can upgrade or downgrade MongoDB versions within the same Feature Compatibility Version (FCV) in Ops Manager sharded clusters, replica sets, and standalone MongoDB instances while maximizing the availability of your deployments.
You can add custom-built versions of MongoDB for Ops Manager to download.
If Ops Manager doesn't manage your deployment, change the version of MongoDB manually. To learn more, see upgrade tutorials for each MongoDB release.
Note
Ops Manager support for End of Life MongoDB versions
Ops Manager doesn't support Backup, Monitoring, or Automation for versions earlier than MongoDB 3.6.
Ops Manager continues to support Automation, Backup, and Monitoring using the MongoDB Agent for clusters running MongoDB 3.6 or later.
Considerations
Check the following documents for any considerations or compatibility issues before changing a deployment's MongoDB version:
The documentation for your driver.
Plan the version change during a predefined maintenance window.
Change the MongoDB version on a staging environment before changing a production environment. Your staging environment should mirror your production environment. This can help avoid compatibility issues that may result in downtime for your production deployment.
Follow the MongoDB release notes when performing manual upgrades of replica sets and sharded clusters.
Note
Downgrading Limitations
You cannot downgrade a MongoDB deployment:
From version 5.0 to any version before 4.4.0
From version 4.4 to any version before 4.2.6
From version 4.2 to any version 4.0.12 (for Windows) or 4.0.7 (for Linux)
From version 4.0 to any version before 3.6.23
Prerequisites
Remove Incompatible MongoDB Features when Downgrading
If the MongoDB deployment has its Feature Compatibility Version set to the same release series as its Version, you must first manually downgrade the instance's featureCompatibilityVersion.
Procedure
Navigate to the Clusters view for your deployment.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If it is not already displayed, click Deployment in the sidebar.
Click the Clusters view.
On the line listing the deployment item, click Modify.
Verify the desired version number is in the version list.
In the Cluster Configuration section, the Cluster Settings heading lists the processes with their names, MongoDB versions, data directories and log files.
Scroll to the Cluster Settings heading.
Click the Version arrow for the first MongoDB process in the list.
Note
If you're running in local mode and don't see your desired version, you can Update the Version Manifest Manually.
To learn more, see Local Mode Configuration.
Change the version of MongoDB for the deployment.
For each MongoDB process that you want to change:
Click the current version number for the process.
Click the desired version number.
(Optional) Update the featureCompatibilityVersion.
If you are upgrading to a new major version, and wish to enable
features offered in the new major version, you must also update the
featureCompatibilityVersion.
For each MongoDB deployment that you want to change:
Click the current
featureCompatibilityVersionfor the deployment.Click the value that matches the desired version number.
Click Save.
Click Review & Deploy to review your changes.
Click Confirm & Deploy to deploy your changes.
Otherwise, click Cancel and you can make additional changes.