> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.4/setup-and-upgrade/upgrade-the-server/other-procedures.md).

# Other migration-related procedures

This section explains how to revert to the previous version of SonarQube Server, how to move to another edition, how to migrate the database to another vendor. This page is for SonarQube Server 10.4.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.4 documentation. For a list of all 10.4 pages, see the [SonarQube Server 10.4 page index](https://2155789048-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL4urx4YsPFYDefLTrxao%2Fuploads%2FlBlJSWAzuhYo7WEorlJX%2Fsonarqube-server-10.4-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.4 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

## Reverting to the previous version <a href="#revert-previous" id="revert-previous"></a>

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 <a href="#another-edition" id="another-edition"></a>

To move to another SonarQube Server edition during an upgrade:

* Follow the instructions in the respective upgrade section below on the [Performing the upgrade](/sonarqube-server/10.4/setup-and-upgrade/upgrade-the-server/upgrade.md) 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](/sonarqube-server/10.4/setup-and-upgrade/upgrade-the-server/upgrade.md) 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 <a href="#another-db-vendor" id="another-db-vendor"></a>

To migrate your SonarQube Server database from one database vendor to another, use the [SonarQube Server DB Copy Tool](/sonarqube-server/10.4/instance-administration/sonarqube-db-copy-tool.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/10.4/setup-and-upgrade/upgrade-the-server/other-procedures.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.