Sonarqube migration in Azure Cloud from one subscription to another and different tenant

Must-share information:

  • Which versions are you using: SonarQube Server Developer Edition v2025.1.2 (build 108896)
  • How is SonarQube deployed: Currently ZIP installation on an Azure VM. We plan to migrate to AKS (Helm chart) in first step, and in second version upgrade.
  • What are you trying to achieve: Two things: upgrade to a currently active SonarQube Server version, and move the instance to a different Azure subscription/tenant. The database is Azure SQL (MSSQL). We have not decided yet whether we will move the Azure SQL resource itself, or export/restore the database into a new Azure SQL database. As is different tenant, I am almost sure it is NOT possible to migrate DB itself, but we will need to recreate same server/DB name.
  • What have you tried so far: Nothing yet, we are still in the planning and investigation phase.

Hello everyone :slight_smile:

Some context first: as far as I know, my company has both a Developer Edition and an Enterprise Edition license, but I currently only have access to the Developer Edition instance. I may contact technical support later, but in the meantime I’d like to get some guidance here.

We are reorganizing our Azure infrastructure, and part of my team will move workloads to a new Azure subscription/tenant. SonarQube is one of the resources that needs to be migrated.

Target setup:

  • We are aware the ZIP installation is deprecated, and we don’t consider Docker on a VM a good fit for production in our environment, so the plan is to run SonarQube on AKS using the official Helm chart.
  • We use a hub-and-spoke network topology. SonarQube is a shared service, so it will run in the hub AKS cluster.
  • The database will remain Azure SQL (MSSQL).
  • The instance will get a new URL.

My main concern is the URL change. In the past, SonarQube stored URLs in the database, and moving an instance to a different URL was not straightforward. Is that still the case with current versions?

More specifically:

  1. Is changing the URL just a matter of updating sonar.core.serverBaseURL after the migration, or is the old URL stored elsewhere in the database?
  2. Does the server ID (and therefore the license) change if the URL and/or the database host changes? Would we need a new license key?
  3. Which integrations need to be reconfigured manually after the URL change (e.g. Azure DevOps integration, PR decoration, webhooks, SAML/SSO)?
  4. What is the recommended order: migrate first on the same version and upgrade afterwards, or upgrade during the migration? Our understanding is that the upgrade path is 2025.1 LTA → 2026.1 LTA → 2026.5 LTA.

Any advice or experience with a similar migration would be greatly appreciated. Thanks!

Hey @zeenmc, welcome to the Community!

1. Is changing the URL just a matter of updating sonar.core.serverBaseURL after the migration, or is the old URL stored elsewhere in the database?

If you are setting this prop via UI (Administration → Configuration > General Settings > General > Server base URL), then it is saved in the DB and will preserve its value. If you were setting it instead via a properties file (sonar.core.serverBaseURL) on application startup, then it won’t be persisted and you will need to pass it in the helm chart’s values.

2. Does the server ID (and therefore the license) change if the URL and/or the database host changes? Would we need a new license key?

The SonarQube URL doesn’t have an impact on the server ID, but the DB URL/connection string (sonar.jdbc.url property) does. We document some license invalidation scenarios, but in your particular case, it sounds like you’re not going to change the DB deployment, so normally the JDBC connection string should stay the same, right? If you are changing this value, then you will need to request a new license key.

3. Which integrations need to be reconfigured manually after the URL change (e.g. Azure DevOps integration, PR decoration, webhooks, SAML/SSO)?

If you’re using SSO, you will have to update the callback URL on your IdP side. If you’re using DevOps platform integrations, you might also have configured the URL there, I suggest you have a look there. SonarQube’s own outbound webhooks are not affected, typically.

4. What is the recommended order: migrate first on the same version and upgrade afterwards, or upgrade during the migration? Our understanding is that the upgrade path is 2025.1 LTA → 2026.1 LTA → 2026.5 LTA.

I don’t think the order (migration 1st, upgrade 2nd, or viceversa) matters much. I would, however, recommend that you don’t do both at once, so that if something goes wrong it’s easier to understand what happened. The upgrade path is correct, yes.

I recommend that you rehearse all this (both migration and upgrade) on a test/non-prod instance before touching your production instance.

PS. could you verify if you have commercial support as part of your license? Because if you do, I would recommend that you reach out via support tickets instead of coming to Community. You will get a higher level of service (SLAs, a private communication channel, etc).