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.

Upgrade Ops Manager

Upgrade Paths

The version of your existing Ops Manager installation determines the upgrade path you must take to upgrade to Ops Manager 4.0 or later.


  • You must follow the upgrade path for your existing version to perform necessary database migrations.
  • To protect your data, Ops Manager refuses to start direct upgrades from versions 1.8.x and 2.0.x to version 3.4 or later.
  • In high availability environments, you must shut down every Ops Manager application server before starting any Ops Manager application servers upgraded to the new version.

The following table lists upgrade paths for all versions:

Existing Version Upgrade Path
4.0.x Use this tutorial to upgrade from Ops Manager 4.0.x to a more recent 4.0.x version.
3.6.x Use this tutorial to upgrade from Ops Manager 3.6.x to version 4.0.x.
3.4.x Use the v3.6 upgrade tutorial to upgrade from Ops Manager 3.4.x to version 3.6.x.
2.x or earlier Use the v3.4 upgrade tutorial to upgrade from Ops Manager 2.x or earlier.

There are no supported downgrade paths for Ops Manager.


It is crucial that you back up the existing and gen.key files because the upgrade process will delete existing data.


Before upgrading Ops Manager from 3.6 to 4.0, complete the following actions:

  • Upgrade all backing databases to MongoDB 3.4 or later.


Upgrade with RPM Package
Upgrade Ops Manager on Red Hat, Fedora, CentOS, and Amazon AMI Linux.
Upgrade with DEB Package
Upgrade Ops Manager on Debian and Ubuntu systems.
Upgrade from Archive on Linux
Upgrade Ops Manager on other Linux systems, without using package management.
Upgrade on Windows
Upgrade Ops Manager on Windows systems.