Skip to main content

[Repositories / Projects] Transfer a repository from cloud repo to cloud repo using GUI app

Updated

This article describes how to transfer a Unity Version Control (UVCS) repository from a legacy Cloud organization to a new Unity organization using the Desktop GUI application. This method allows you to sync the history between two remote servers directly using the "Sync Repositories" feature.

Question:

I have a repository on a legacy Org1@cloud. How do I transfer this repository to Org2@unity using the GUI/Desktop app?

Answer:

You can transfer a UVCS repository from a Legacy Cloud account to a new Unity organization using the GUI application’s Sync Repositories feature.

  1. Install the Client: If you don’t have the GUI/Desktop app installed, download it from https://www.plasticscm.com/download.

  2. Sign In: Install the application, open it, and sign in with your credentials.

  3. Open the side menu: On the Repositories page, click the left arrow in the upper-left corner to open the left-side menu.

  4. Open Sync View: Go to the Sync Repositories view in the side menu.

  5. Create Sync View: Create a new sync view.

    Note: A Sync View establishes a saved relationship between two repositories. It is not a one-time transfer operation; this configuration is persistent, allowing you to return to this view later to perform incremental updates (pushes or pulls) or monitor synchronization status without needing to reconfigure the connection.

  6. Add Base Repo: Click Add src repo and select the destination repository (Unity-Project/Repo@Org2@UNity) for example  New_Destination_Project/New_Repo_Name@Org2@unity)

     

  7. Select Object: Click on the repository object you just added to highlight it.

  8. Add Remote Repo: Click Add dst repo and select the source repository under the legacy Cloud server (Original_Repo@Org1@cloud).

  9. Sync Data: Click the Refresh button to calculate the differences between the two servers.

  10. Click the Pull visible button to begin the transfer of data from the source to the destination.

 

Why does it feel "backward"? 

In the Sync View, the "src repo" is treated as your active/local side, and the "dst repo" is the remote side you are comparing against. By adding the New Repo first (as the "src"), you are telling the application that this is where you are "standing." Therefore, to get data from your old organization, you must Pull it from the remote legacy repo into your active new repo.

Additional Notes:

Permissions: Ensure you have administrative rights or "Replicate" permissions on both organizations to perform the sync.

Repository Specs: * Legacy Cloud format: repo_name@organization_name@cloud

  • New Unity format: project_name/repo_name@organization_name@unity

Workspaces: After the transfer is complete, team members should create new workspaces pointing to the new repository at @unity to continue working.

 

Related to

Related articles