Sonarqube 2025.4.2 version update on test instance server

Must-share information (formatted with Markdown):

  • Sonarqube version 2025.4.2 on Test instance and 9.9 LTS version on Live instance
  • SonarQube deployed through zip methodology
  • We want to restore live Sonarqube database in test Sonarqube database
  • Database restore has not started till now.

Query - I wanted to confirm that is there any issue if we restore LIVE database of Sonarqube on Test Sonarqube server. Because Live instance is having 9.9 LTS version and all rules are related to 9.9 version. And we have updated the latest version 2025.4.2 on Test instance. Kindly confirm that this database restore activity impact our test instance in which areas. It will impact quality profiles section or not. LIVE & Test instance is having different version. Is there any other points we need to take care while restore live database on test database of Sonarqube ?

When reading the update path documentation, I would expect that you cannot directly upgrade. Upgrade path says 9.9 LTA > 2025.1 LTA > 2025.4 and it would be currious, if you could skip the intermediate step by backup and restore.
Personally, if I would keep my analyses database I would restore with 9.9 and then do two upgrade migrations (2025.1 LTA and 2025.5).

As always, the Sonar way quality profiles and rules have been updated in the mean time and will impact your instance if you use or inherit them.

Also the the quality mode for the categories of issues was introduced or changed since 9.9.

Maybe someone from Sonarsource will add further topics to observe.

If you restore your live SonarQube 9.9 database onto your test server, it will completely overwrite your current test server data.

After restoring, you’ll need to start SonarQube 9.9 against that database to ensure compatibility—using a newer version of SonarQube like 2025.4.2 directly against a 9.9 database is not supported.

As Volker mentioned, the upgrade path supported by SonarQube is 9.9 → 2025.1 LTA → 2025.4.

Restoring a 9.9 database onto a 2025.4 instance will affect all data, including quality profiles, projects, and user information.