Release Notes >
Release Notes for MongoDB 6.0 (Release Candidate) >
Downgrade 6.0 to 5.0 >
Downgrade 6.0 Standalone to 5.0

Downgrade 6.0 Standalone to 5.0¶

On this page

Downgrade Path
Access Control
Prerequisites
Downgrade Procedure

Before you attempt a downgrade, familiarize yourself with the content in this page.

Downgrade Path¶

After upgrading to 6.0, if you need to downgrade, we recommend downgrading to the latest patch release of 5.0.

Access Control¶

If your deployment has access control enabled, your downgrade user privileges must include privileges to list and manage indexes across databases. A user with root role has the required privileges.

Prerequisites¶

Before you begin the downgrade procedure, you must complete the following prerequisite steps.

1. Create Backup¶

Optional but Recommended. Create a backup of your database.

To learn how to create a backup, see MongoDB Backup Methods.

2. Remove Backward-Incompatible Features¶

To downgrade from 6.0 to 5.0, you must remove 6.0 features that are incompatible with 5.0. For a list of incompatible features and how to remove them, see Downgrade Considerations.

3. Downgrade Feature Compatibility Version (fCV)¶

To downgrade the featureCompatibilityVersion of your standalone instance:

Use mongosh to connect to the mongod instance.
Downgrade the featureCompatibilityVersion to "5.0".
copy
```
db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )
```
The setFeatureCompatibilityVersion command performs writes to an internal system collection and is idempotent. If the command does not complete successfully, retry the command on the mongod instance.

Downgrade Procedure¶

Warning

Before proceeding with the downgrade procedure, ensure that the prerequisites have been completed.

← Downgrade 6.0 to 5.0 Downgrade 6.0 Replica Set to 5.0 →