How to migrate sonar 6.0 version to 10.8 version of Sonar without loosing the data?

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension): sonar 6.0 community
  • how is SonarQube deployed: zip, Docker, Helm : zip
  • what are you trying to achieve : upgrade to 10.8
  • what have you tried so far to achieve this: not yet started , couldn’t find the document in the official website from 6.x to 7.x

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hi,

Welcome to the community!

This is not going to be fast or easy.

To get from 6.0 to 2025.1, the current LTA, which was released last week, you’ll need to upgrade:

6.0 → 6.7 → 7.9 → 8.9 → 9.9 → 2025.1

For each upgrade, you should

  • back up your database
  • follow the full upgrade procedure, although you can skip step 2 for the intermediate versions.

Note that even though re-analyzing is one of the hard-coded steps in the upgrade procedure, you can often get away without it. However, there are versions in this range where you’ll need to do it and unfortunately it’s been so long that I don’t remember which ones really require it. So I advise you to browse the interface after each upgrade. If things look fine, you can probably proceed with the next one. If not, then it’s time to reanalyze.

 
Good luck!
Ann

Thanks Ann. I couldtn see any upgrade procedure document from 6.0 to 6.7 .
But tried, post upgrade noticed the ui is up except the rules and quality profiles allother data is reflecting in the ui. could see the rules in the db but not inthe ui

Hi,

That sounds like a bad Elasticsearch index. You could dforce an ElasticSearch reindex or you could just move on to the next migration, since the indices aren’t re-used from version to version.

But don’t overlook making a DB backup before each migration in case you need to backtrack.

 
HTH,
Ann

Hi Ann,

<newSonarqubeHome>/elasticsearch/config/elasticsearch.yml

Entries in this file was commented by default. do we need to skip editing this file? (because I don’t see any step related to it in the documentation)

Hi,

Yes, skip editing the file.

 
Thx,
Ann

Thanks Ann,
was able to upgrade to 7.9 . could see the data is reflecting as expected. but while triggering build could see error as below.

ERROR: Error during SonarQube Scanner execution
ERROR: Unable to execute SonarQube
ERROR: Caused by: Fail to download libraries from server
ERROR: Caused by: Index 1 out of bounds for length 1

HI Ann,
we have upgraded to 9.9 LTA. noticed 10.x is not LTA. where as SonarQube 2025.1 LTA but couldnt see the community edition for it … while downloading the latest could see it is downloading the sonarqube-25.2.0.102705 is this also a LTA ?

Hi @naveen1,

after the 9.9 LTA there is no LTA anymore for the SonarQube Community Build (what used to be SonarQube Community Version - it was renamed) anymore.

The version you found, 25.2.0.102705 is the latest version, this is correct, but there is now a release every month of Community Build and no LTA - this is only for SonarQube Server, the paid options.

Best,
Tobias

1 Like

Thanks Tobias. but in the website could see 25.1 is the latest LTA (after 9.9 LTA) . unfortunately, couldn’t find the community version for 25.1

Hey @naveen1,

yes there is the information about the 2025.1 LTA on the website but this only applies to SonarQube Server, not SonarQube Community Build.
Therefore the release cycles of SonarQube Server and SonarQube Community Build differ.

When updating the SonarQube Community Build you always have to update to the latest release as there is no LTA for it anymore.

Best,
Tobias

1 Like

Thanks Tobias, I have upgraded to latest community build.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.