Other migration-related procedures

Reverting to the previous version

If you need to revert to the previous version of SonarQube Server, the high-level rollback procedure for all deployments is as follows:

1. Shut down your SonarQube Server instance or cluster.
2. Roll back your database to the backup you took before starting the upgrade.
3. Switch back to the previous version of your SonarQube Server installation.
4. Start your SonarQube Server instance or cluster.

Moving to another SonarQube Server edition

To move to another SonarQube Server edition during an upgrade:

• Follow the instructions in the respective upgrade section below on the Performing the upgrade page by using the appropriate edition file or Docker image tag:
  • Upgrading a ZIP file instance
  • Upgrading a Docker image instance
  • Upgrading a Helm chart instance

To move to another SonarQube Server edition without upgrading your SonarQube Server version:

• Follow the instructions in the respective upgrade section on the Performing the upgrade page:
  • By using the appropriate edition file or Docker image tag.
  • Without navigating to http://<yourSonarQubeServerURL>/setup or reanalyzing your projects.

Migrating the SonarQube Server database to another vendor

To migrate your SonarQube Server database from one database vendor to another, use the SonarQube DB Copy Tool.

Moving between SonarQube Community Build and SonarQube Server

To move from SonarQube Community Build to SonarQube Server, ensure the target SonarQube Server version was released after the installed version of SonarQube Community Build. In most cases, migrating to the latest version of the SonarQube Server will suffice. However, if you are using the latest version of SonarQube Community Build, you may need to wait for the next version of SonarQube Server, typically available within a month.

To move from SonarQube Server to SonarQube Community Build, you should always target the latest release of SonarQube Community Build.

Once the target version is confirmed, proceed with the standard upgrade procedure.