The MongoDB Software Lifecycle Schedules page describes the supported versions and end-of-life dates for MongoDB Server releases. Depending on your cluster type, Atlas offers different version-management options. For Dedicated clusters, Atlas provides two release cadence options: major versions, or ongoing updates using Latest Version With Auto Upgrades. Free and Flex clusters don't let you choose a release cadence; they stay on a major version (currently, MongoDB 8.0), and Atlas automatically upgrades them.
For most Atlas deployments, Latest Version With Auto Upgrades is the best way to receive the latest MongoDB features and enhancements automatically as Atlas rolls them out. However, you can opt for tighter version control and choose to stay on a specific major version.
The following table compares the two release cadences:
Consideration | Latest Version With Auto Upgrades | Major Version |
|---|---|---|
Automatic upgrades | Major, minor, and patch releases | Patch releases only |
Control over upgrade timing | No | Yes |
Version selection | Not available | Choose from the available versions |
Switching cadence | Switch to a major version only in the window after a new major version releases | Switch to auto upgrades at any time by modifying the cluster |
Best for | Staying current with the latest features and improvements automatically | Direct control over release acceptance, such as coordinating versions across environments or certifying release contents before adoption |
Avoid if | You require direct control over release acceptance, such as coordinating versions across environments or certifying release contents before adoption | You want to stay current with the latest features and improvements without managing upgrade timing yourself |
To learn more about MongoDB Server versions in general, see MongoDB Versioning.
Latest Version with Auto Upgrades
When you choose your cluster version and select Latest Version With Auto Upgrades, Atlas automatically upgrades your cluster to the latest available MongoDB major or minor version, enables new features as they become available, and upgrades patch releases through a rolling process to maintain cluster availability. You can't select a specific major, minor, or patch version.
Switching from Auto Upgrades
If your cluster uses Latest Version With Auto Upgrades, you can't switch to a major-version cadence until MongoDB 9.0 is available to all Atlas deployments.
Important
Live Migration and Mongosync are not supported on minor versions, and therefore won't work if your cluster uses Latest Version With Auto Upgrades. To migrate a cluster that is currently on a minor version, use self-guided migration tools instead.
Major Version
If you remain on a major version, you control when major-version upgrades happen. You can upgrade the major version of your Atlas cluster at any time by modifying the cluster. Major versions also automatically receive patch release updates.
Before upgrading a major version in production, test your application against a staging cluster and review compatibility changes in the release notes. If applicable, rely on the Stable API.
End of Life for a Major Version
Atlas sends you an email notification at least six months before a MongoDB version reaches end of life. You can also find the information on the MongoDB Software Lifecycle Schedules page. After the cut-off date, Atlas upgrades your clusters to the next MongoDB version unless you request and receive approval for an extension. Upgrade your cluster before the cut-off date to ensure that your services and applications experience no downtime or compatibility issues with the new MongoDB version.
Version Availability
The following table shows the MongoDB versions available for each cluster type.
Version | Available on M10+ | Available on M0 and Flex clusters |
|---|---|---|
MongoDB 7.0 | ||
MongoDB 8.0 | ||
MongoDB 8.3 * |
- Version 8.3 is available only for clusters with Latest Version With Auto Upgrades.
Important
If your project contains a custom role that uses actions introduced in a specific MongoDB version, you can't create a cluster with a MongoDB version earlier than that version unless you delete the custom role.
Select or Change the Cluster Version
Important
Before you upgrade your cluster, review the recommended best practices for major version upgrades.
To select or change the cluster version:
Open the cluster configuration.
To set the version for a new cluster, complete the steps to create a cluster and expand Additional Settings.
To change the version for an existing cluster, click Edit Config to open the cluster form and expand Additional Settings.
Select a version.
From the Select a version dropdown, select the version for your cluster.
Atlas supports the following upgrade paths:
MongoDB 7.0 to MongoDB 8.0
MongoDB 8.0 to Latest Version With Auto Upgrades
Atlas always upgrades the cluster to the latest patch release of the specified major version. The upgrade uses a rolling update process to maintain cluster availability.
You can't downgrade the cluster to an earlier MongoDB version unless you pinned the cluster's FCV before upgrading.
You can switch from using the Latest Release to using a specific release only if the latest MongoDB version is a major release.