We currently have a SonarCloud organization that is bound to GitHub and has an active Team plan subscription.
We are migrating our repositories and CI from GitHub to Azure DevOps. Our intention is to create a new SonarCloud organization bound to Azure DevOps and move our analysis there.
However, at the moment we are not able to create a new Azure DevOps–bound organization. When attempting to create a new organization, SonarCloud only allows GitHub as the binding option because our existing organization is already GitHub-bound.
Sonarcloud doesn’t let one account have two active paid orgs at the same time, especially if they are in different ALM bindings.
if you already have a Team plan org bound to GitHub, the UI will force new org creation to reuse that binding.
The best way to get around it is to move the subscription instead of “cloning” it. you have to ask SonarCloud support to detach the Team subscription from the GitHub-bound org so you can create a fresh Azure DevOps–bound org and reattach the plan there.
There is no way for users to switch from GitHub to Azure DevOps on their own.
important bits to plan for:
projects, history, and issues do not transfer between orgs
you’ll re-run analysis from scratch in Azure DevOps pipelines
quality gates and profiles need to be recreated manually
Most teams keep the GitHub organization going until the Azure DevOps analysis is stable, and then they shut it down. It’s annoying, but that’s how SonarCloud keeps ALM separate right now.