Plastic SCM joins Unity! Here is the Collaborate to Plastic SCM Migration Guide. Hello fellow creators! As you may have read on the blog, we are thrilled to welcome Codice Software, the company behind Plastic SCM, to the Unity family! We built Collaborate to give users the ability to share projects amongst small teams who want an easy way to sync their projects without navigating the complexity of version control. We brought Plastic SCM into the fold for larger teams looking for more advanced features like branching, locking, merging and a standalone GUI. We believe that it’s important for creators to have the flexibility to pick the tools that fit their development and team needs. That is why we are committed to making sure that Plastic SCM, Collaborate and other third party version control services continue to receive support. If you wish to migrate your Collaborate projects to Plastic SCM, you can check out the step-by-step migration guide below to get started. This guide will walk you through the process of migrating Collaborate projects with the Collaborate migration tool, inviting your team members, setting up your Plastic SCM workspace and getting the new Plastic SCM for Unity plugin (now in beta). Collaborate to Plastic SCM Migration Guide Videos Migration Wizard Plastic SCM Plugin Dev Mode Plastic SCM Plugin Gluon Mode Migration Steps Step 1. Access the Collaborate migration tool available on the Plastic SCM website. Step 2. Click on Get Started and follow the wizard to migrate your Collaborate project(s) to Plastic SCM. Step 3. Download and install the Plastic SCM Cloud Client. Step 4. Open the Plastic SCM Cloud Client and log in. Step 5. Select the Organization that you have created with the migration tool. Step 6. Select the workflow that fits your needs. Gluon Mode, a workflow tailored for artists. This workflow lets you pick the files you want to work on and check them back in without having to update your whole workspace. If you need to work inside the Unity Editor, make sure that you configure Gluon so that it pulls down all Unity project files required to open a Unity project. Developer Mode. If you want to check in your changes directly to your cloud repository, create your workspace using the centralized tab. Step 7. Create a workspace. If your Unity project files are already on your machine, select the path on disk that corresponds to the root of your Unity project. If your Unity project files are not on your machine, you can select any location in which you want to create your workspace. Step 8. Update or Configure your Workspace. If you choose to use Gluon Mode, make sure you configure the workspace so that it pulls down all Unity project files required to open a Unity project. If you choose Developer Mode, update your workspace in order to ensure your project is up to date with all incoming changes. Step 9. Open your Unity project through the Hub. Step 10. Go to the asset store and import the Plastic SCM Plugin for Unity (beta) plugin. Step 11. Disable Collaborate from your migrated project by clicking the Off button on the Unity Services window or in your Project Settings. Step 12. Check in your modified Project Settings. You are now ready to work on your project using Plastic SCM! FAQ What does this mean for the development plan you had before? We are committed to ensuring we provide you with a choice between a workflow that allows smaller teams to sync projects without navigating the complexity of version control and one that can benefit larger teams looking for more advanced features like branching, locking and a standalone GUI. This means we will continue to support Collab with its current feature set. Where should I post questions related to Plastic SCM? You can post questions in the Plastic SCM forums. For any questions related specifically to the migration tool, the Plastic SCM plugin and using Plastic SCM with Unity, you can reach out through the Plastic SCM Unity forum.