# Migrate project from one org to another

**URL:** <https://community.sonarsource.com/t/migrate-project-from-one-org-to-another/189850>\
**Category:** SonarQube Cloud\
**Tags:** sonarqube, sonarqube-cloud\
**Created:** [October 14, 2026, 5:31pm UTC](https://community.sonarsource.com/t/migrate-project-from-one-org-to-another/189850 "2026-10-14T17:31:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ReenigneArcher](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/reenignearcher/32/64454_2.png) [@ReenigneArcher](https://community.sonarsource.com/u/ReenigneArcher)\
**Post date:** [October 14, 2026, 5:31pm UTC](https://community.sonarsource.com/t/migrate-project-from-one-org-to-another/189850/1 "2026-10-14T17:31:30Z")

</div>

I am planning to move a GitHub repo from one GitHub org to another, and have already created the new org in Sonarqube cloud.

But looking at [Migrating projects | SonarQube Cloud | Sonar Documentation](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/migrate-projects-to-another-org) it seems there is really no way to migrate the project in sonar. Sure, it will import it as a new project, but it seems that all the historical data will be lost.

Is there anything planned for the future that would make an actual migration possible? I really don’t want to lose all the historical records and decisions on this project if possible.

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [October 16, 2026, 3:28pm UTC](https://community.sonarsource.com/t/migrate-project-from-one-org-to-another/189850/2 "2026-10-16T15:28:25Z")

</div>

Hey @ReenigneArcher, you are right, it’s not possible to migrate a SonarQube Cloud project from one organization to another. This is a commonly requested feature, and as such, there is [a public roadmap item for it](https://portal.productboard.com/sonarsource/1-sonarqube-cloud/c/646-administrators-can-transfer-projects-between-organizations?&utm_medium=social&utm_source=share). You can vote for it and add a comment.

Some users run into this limitation when trying to move from one DevOps platform/org to another. For example, if you were migrating all your GitHub projects from one GitHub org to another. In this case, what we typically recommend is to keep the old SonarQube Cloud organization and [change its binding](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/changing-organization-binding) from the old GH org to the new one. I think this is not what you’re trying to do, but I’m letting you know anyways just in case.

---

<div class="post-metadata">

**Author:** ![ReenigneArcher](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/reenignearcher/32/64454_2.png) [@ReenigneArcher](https://community.sonarsource.com/u/ReenigneArcher)\
**Post date:** [October 16, 2026, 4:54pm UTC](https://community.sonarsource.com/t/migrate-project-from-one-org-to-another/189850/3 "2026-10-16T16:54:05Z")

</div>

Thanks for the response, but changing the org binding isn’t going to help because I’m not renaming the GitHub org, only moving some of the repos (not all).