> 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/updating-to-sonarqube-server.md).

# Moving to SonarQube Server

This page provides links to relevant pages in the SonarQube Community Build and SonarQube Server documentation that will help you succeed in making a version update.

See the [Updating from SonarQube Community Build](https://docs.sonarsource.com/sonarqube-server/server-update-and-maintenance/update/updating-from-sonarqube-community-build) page in the SonarQube Server documentation.

## Related pages <a href="#related-pages" id="related-pages"></a>

* The Update [Overview](/sonarqube-community-build/server-update-and-maintenance/update/roadmap.md) page when updating to a new version of SonarQube Community Build.
* [Other migration-related tasks](/sonarqube-community-build/server-update-and-maintenance/update/other-procedures.md) page when reverting to the previous version of SonarQube Community Build or migrating your database to another vender.
* [Project move](/sonarqube-server/2025.4/project-administration/project-move.md) page when exporting a project from one SonarQube Server instance and import it into another SonarQube Server instance.


---

# 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/updating-to-sonarqube-server.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.