Migrate a Unity Collab project to Plastic SCM

Motivation

We write this article to help teams that want to change their version control solution from Unity Collab to Plastic SCM.

Lack of big files support, performance issues and data corruption are some of the common issues that lead Unity Collab users to try Plastic SCM. The process described below explains how to download the Collab project in a git format to later import it to Plastic SCM using GitSync.

How to do it

1. Sign into the Unity Developer Dashboard.
2. Select the Project to export.
3. In the left navigation window, click Collaborate, then click Storage.
4. In the main window, click the START EXPORT button.
5. When the export is complete, click the DOWNLOAD EXPORT button. A zip file downloads onto your local machine.
6. The Zip file contains a Git repository that looks like the one below. Unzip the file.
   
7. Install git in your machine. Once you have git, please run the following command at the parent directory of the git repository. In my case, "C:\data\CollabExport" contains the "de500c48-4e6b-43db-bacd-8f4a9613760d" git repository directory.
   

   C:\C:\Users\manu\Desktop>cd C:\data\CollabExport
   C:\data\CollabExport>git daemon --reuseaddr --verbose --export-all --base-path=.
   [5532] Ready to rumble

8. Create a new repository at the plastic SCM Cloud (If you use an on-premise Plastic SCM server use the server ip and port instead)
   
9. Create a new Plastic SCM workspace to work with the new Plastic SCM repository, open the branch explorer view and, right-click the main branch. It's very important to click the branch, not the changeset. Select "Push/Pull" -> "Sync with Git"
   
10. At the "Repository URL" please write "git://localhost/" followed by the git repository GUID you downloaded.
    
11. Click the sync button.
12. Once the process finishes, you have the Collab repository migrated to a Plastic SCM repository.

Both the export and the import can take a while depending on your project size.