This article addresses the process of transferring repositories between Unity organizations, specifically from legacy organizations to Unity organizations. Direct transfers are not possible via the web UI; instead, repositories must be manually cloned using command-line instructions. The article provides the necessary steps and conditions for successfully cloning repositories to ensure data integrity and security. Additionally, it outlines prerequisites such as membership and roles within the respective organizations.
Symptoms
- I am unable to transfer repositories between two organizations, OrgA (a legacy one) and OrgB (a Unity org), through the web UI.
- I need to move repositories from OrgA to OrgB.
Causes
A direct transfer, or "move", of repositories between Unity organizations is not available through the user interface for security and data integrity reasons.
Resolution
The recommended process is to clone each repository using command-line instructions. That creates an exact copy of the repository, including its full history, in the new organization.
Ensure the following conditions are met before proceeding:
- Membership in the source project within the OrgA organization (Legacy).
- An existing Unity Cloud project in the OrgB organization to receive the repositories.
- Owner or Manager role in the destination project within the OrgB organization.
Use the following command for each repository:
cm clone <repository-name>@OrgA@cloud <destination-project>/<repository-name>@OrgB@unity
- Replace
<repository-name>and<destination-project>, with the appropriate names, and add your own organization names.
Finally, verify the cloned repositories in the OrgB organization before deleting originals from the OrgA organization.
More Information
In this article, you can find the differences between legacy @cloud orgs and new @unity orgs.