> 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-community-build/server-update-and-maintenance/update/other-procedures.md).

# Other migration-related tasks

This article describes how to revert to the previous version of SonarQube Community Build and how to migrate the database to another vendor.

To update to SonarQube Server, see [Moving to SonarQube Server](/sonarqube-community-build/server-update-and-maintenance/update/updating-to-sonarqube-server.md).

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

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

1. Shut down your SonarQube Community Build instance.
2. Roll back your database to the backup you took before starting the update.
3. Switch back to the previous version of your SonarQube Community Build installation.
4. Start your SonarQube Community Build instance.

## Migrating the SonarQube Community Build database to another vendor <a href="#another-db-vendor" id="another-db-vendor"></a>

To migrate your SonarQube Community Build database from one database vendor to another, use the [Migrating database](/sonarqube-community-build/server-update-and-maintenance/maintenance/sonarqube-db-copy-tool.md).

## Moving from a ZIP file installation to a containerized deployment <a href="#from-zip-to-docker" id="from-zip-to-docker"></a>

To move from a ZIP file installation to Docker or Kubernetes, follow the [ZIP installation migration guide](/sonarqube-community-build/server-update-and-maintenance/maintenance/zip-migration-guide.md). It covers keeping your existing database and Server ID, carrying over your settings, verifying the migration, and rolling back.

## Updating a plugin <a href="#upgrading-plugin" id="upgrading-plugin"></a>

See [Installing a plugin](/sonarqube-community-build/server-installation/plugins/install-a-plugin.md). For the SonarQube Community Build, see [Using Marketplace](/sonarqube-community-build/server-update-and-maintenance/update/marketplace.md).

## Downgrading to SonarQube Community Build

Ensure the target SonarQube Community Build version was released after the source SonarQube Server version. See [Releases - Sonar Community](https://community.sonarsource.com/c/sq/releases/24) for release dates of SonarQube Community Build and SonarQube Server. In most cases, migrating to the latest version of the target product will suffice.

However, if you are using the latest version of SonarQube Server, you may need to wait for the next version of SonarQube Community Build accordingly, typically available within a month.

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

To update your SonarQube Community Build to SonarQube Server, see [Upgrading from SonarQube Community Build](https://docs.sonarsource.com/sonarqube-server/server-update-and-maintenance/update/updating-from-sonarqube-community-build).


---

# 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-community-build/server-update-and-maintenance/update/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.