> 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/server-update-and-maintenance/update/determine-path.md).

# Determining the update path

This explains the steps to follow to determine the path you need to take to update your version of SonarQube Server. This page is for SonarQube Server 2026.5.

This section explains the principles to follow to determine whether you can perform the update directly or must update first to an intermediate version(s). To understand the principles, you must first understand the [Release cycle model](/sonarqube-server/server-update-and-maintenance/update/release-cycle-model.md).

To determine your update path, consider the following principles:

* You can update directly from a non-LTA version to another if there is no LTA version in your update path.
* If there is at least one LTA version in your update path, you must first update to each intermediate LTA and then to your target version.
* When upgrading to an LTA version, you should directly update to its latest patch.
* You can update from the latest LTA version to the latest non-LTA version directly.
* If you’re migrating from an earlier patch version of an LTA, you can update directly to the next LTA. You don’t need to install any intermediate patch versions.
* There is no LTA concept for SonarQube Community Build.

## Update path examples <a href="#path-examples" id="path-examples"></a>

| From version | To version | Update path                                               |
| ------------ | ---------- | --------------------------------------------------------- |
| 2025.1 LTA   | 2026.1 LTA | 2025.1 LTA > 2026.1 LTA (direct)                          |
| 9.9 LTA      | 2026.1 LTA | 9.9 LTA > 2025.1 LTA > 2026.1 LTA (one intermediate step) |
| 9.9 LTA      | 2025.4 LTA | 9.9 LTA > 2025.1 LTA > 2025.4 LTA (one intermediate step) |
| 9.9 LTA      | 2025.1 LTA | 9.9 LTA > 2025.1 LTA (direct)                             |
| 8.9          | 2025.1 LTA | 8.9 LTA > 9.9 LTA > 2025.1 LTA (one intermediate step)    |
| 2025.1 LTA   | 2025.3     | 2025.1 LTA > 2025.3 (direct)                              |
| 10.6         | 2025.1 LTA | 10.6 > 2025.1 LTA (direct)                                |
| 10.6         | 2025.3     | 10.6 > 2025.1 LTA > 2025.3 (one intermediate step)        |

## Update path calculator

You can use our calculator to help determine your update path.

{% @sonar-embeds/upgrade-calculator %}


---

# 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/server-update-and-maintenance/update/determine-path.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.