> This page location: /docs.md > /docs/management.md > /docs/atlas/create-connect-deployments.md > /docs/atlas/manage-clusters.md > /docs/atlas/atlas-versions.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

<!--
Tab options on this page. Append to the .md URL to filter:
  ?tabs=<id,...>   select specific tabs (e.g. ?tabs=nodejs,shell)
  ?allTabs=true    include every tab
  (no param)       default: one tab per tabset

Available tabs:
  other tabs: ui, api
-->

# Downgrade Major MongoDB Version for a Cluster

To downgrade your Atlas Core cluster to the previous major MongoDB version, you must have pinned the FCV (Feature Compatibility Version) before you upgraded. This tutorial describes how to downgrade your Atlas Core cluster and how to pin and unpin the FCV (Feature Compatibility Version).

To learn what the FCV (Feature Compatibility Version) is and how pinning it preserves the ability to downgrade, see [MongoDB Versions and Upgrade Paths.](https://www.mongodb.com/docs/mongodb-versions.md#std-label-versions-and-upgrade-paths)

**Important: Atlas Infinite clusters do not support manual MongoDB versioning.**

Only Atlas Core clusters support upgrading and downgrading MongoDB versions.

Atlas Infinite clusters run MongoDB using Latest Version With Auto Upgrades, and do not support manual version upgrades. Atlas automatically manages versioning for Atlas Infinite clusters.

## Limitations

The following limitations apply to downgrading your cluster's version:

- You can only downgrade your cluster using the procedure on this page if you pinned the FCV (Feature Compatibility Version) before upgrading.

- You can only downgrade your cluster to the major version that matches the pinned FCV (Feature Compatibility Version).

- You can only perform this action if the pinned FCV (Feature Compatibility Version) is only one [major version](https://www.mongodb.com/docs/atlas/atlas-versions.md#std-label-atlas-versions) below the current FCV (Feature Compatibility Version) and you don't have Latest Version With Auto Upgrades enabled.

- If your cluster uses [Latest Version With Auto Upgrades](https://www.mongodb.com/docs/atlas/atlas-versions.md#std-label-latest_version_with_auto_upgrades), you can't pin its FCV (Feature Compatibility Version) and you can't downgrade the cluster. If you want to move off Auto Upgrades, you can do so after the major version release (`x.0.0`) but before the first minor release in that cycle (`x.1.0`).

- You can't downgrade to a version after it reaches end-of-life. Ensure pinning occurs before the current version reaches end-of-life.

- FCV (Feature Compatibility Version) pinning is only available on Dedicated clusters.

- FCV (Feature Compatibility Version) pinning can't be extended beyond 4 weeks from the pin date.

If a downgrade is necessary, and you did not pin the FCV (Feature Compatibility Version) before upgrading, you can:

- Restore to a specific point in time:

  - If you have [Continuous Cloud Backup](https://www.mongodb.com/docs/atlas/backup/cloud-backup/dedicated-cluster-backup.md#std-label-pit-restore) enabled for your cluster, you can perform a PIT (Point in Time) restore to restore your cluster to a previous state with the older MongoDB version:

    - Create a new cluster with the previous major version.

    - Perform a PIT (Point in Time) restore using the instructions in [Restore from Continuous Cloud Backup.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-continuous.md#std-label-restore-from-continuous)

- Restore from an Atlas snapshot:

  - If you have [Cloud Backup](https://www.mongodb.com/docs/atlas/backup/cloud-backup/overview.md#std-label-backup-cloud-provider) enabled without continuous cloud backups, consider restoring the latest snapshot of the cluster based on the previous version to a new cluster:

    - Create a new cluster with the previous major version.

    - Restore the latest snapshot before the MongoDB version upgrade to the new cluster using the instructions in [Restore from a Scheduled or On-Demand Snapshot.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-snapshot.md#std-label-restore-from-snapshot)

## Required Access

To downgrade a cluster by a major version, pin the FCV (Feature Compatibility Version) for your cluster, or unpin the FCV (Feature Compatibility Version) for your cluster, you must have the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) or higher role for the project.

## Downgrade Your Cluster by One Major Version

To downgrade your cluster by one major version:

### Atlas UI

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Click the  icon to the right of the cluster.

3. Select Edit Configuration.

4. In the Additional Settings section of the cluster form, select a major version from the dropdown next to Select a Version that matches your cluster's FCV (Feature Compatibility Version).

   A warning banner appears indicating that your cluster's MongoDB version will be downgraded.

## Pin the FCV (Feature Compatibility Version) for Your Cluster

When your cluster has a pinned FCV (Feature Compatibility Version), a pin icon appears next to your cluster's Version at the bottom of the cluster card. If you hover your cursor over the pin icon, a tooltip that shows the FCV (Feature Compatibility Version) and the expiration date appears.

Atlas unpins your cluster's FCV (Feature Compatibility Version) on the next [maintenance window](https://www.mongodb.com/docs/atlas/tutorial/cluster-maintenance-window.md#std-label-configure-maintenance-window) starting on or after the expiration date.

If you already upgraded your cluster's MongoDB version, Atlas upgrades its FCV (Feature Compatibility Version) to match its MongoDB version after the pin expires.

**Warning:**

The FCV (Feature Compatibility Version) pin is a short-term measure that persists for up to 4 weeks after the pin date, and doesn't simulate the behavior of the previous binary versions. It only postpones upgrading certain internal data structures that allow new server features. After you are confident that a downgrade to the previous version is unnecessary, unpin the FCV (Feature Compatibility Version) to match the current binary version.

To pin the FCV (Feature Compatibility Version) for your cluster:

### Atlas UI

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Click the  icon to the right of the cluster.

3. Select Pin Feature Compatibility Version.

   A modal appears with the Feature Compatibility Version and the Set expiration date field.

4. Set the expiration date.

   All dates are set to Timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601?oldid=962856429) date and time format in UTC (Coordinated Universal Time), in the `MM/DD/YYYY` format. Set the FCV (Feature Compatibility Version) expiration date to be within four weeks of the date to which you pinned the FCV (Feature Compatibility Version). When the expiration date passes, the tooltip displays `Expired XX/XX/XXXX`. Your FCV (Feature Compatibility Version) pin automatically expires after 4 weeks.

   After the FCV (Feature Compatibility Version) pin expires, Atlas unpins your cluster's FCV (Feature Compatibility Version) on the next maintenance window starting on or after the expiration date. If you already upgraded your cluster's MongoDB version, Atlas upgrades its FCV (Feature Compatibility Version) to match its MongoDB version.

## Unpin the FCV (Feature Compatibility Version) for Your Cluster

To unpin the FCV (Feature Compatibility Version) for your cluster:

### Atlas UI

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Click the  icon to the right of the cluster.

3. Select Edit Pinned Feature Compatibility Version.

   A modal appears with the Feature Compatibility Version and the Edit expiration date field.

4. Click Unpin next to the Feature Compatibility Version.

## Contact Support

If you have any questions regarding migration support beyond what is covered in this documentation, or if you encounter an error during migration, file a support ticket through the Atlas user interface.

If you have any questions or need further assistance, reach out to our [support](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support) team.
