Migrations, Migrations, Migrations

One of the benefits of Git is that it is super easy to migrate to. This document highlights the ways to onboard your existing files into a Copia Git repository. Our goal is for it to never take more than 10-minutes for you to fully migrate into Copia. If there is a migration case we don't handle, please, please email us at [email protected] so we can build tools to ease adoption.
If your source repository is Git-LFS enabled, please contact Copia for guidance, as there is an additional process for this to migrate the Git LFS objects.

Migrating Existing Git

Migrating an existing Git repository to Copia is easy to do and supported right in our web UI.
Click the + button in the upper right-hand corner and choose the New Migration option.
Select your Git provider.
For migrations from GitHub, you must use the GitHub migration option (second option in the screenshot below) rather than the vanilla Git migration option. Github no longer supports the Username and Password authentication used by the vanilla Git migration option.
Fill in the details of your migration.

Existing directory structure

Some users may already have files in a directory structure. If this is the case, follow the steps below
  1. 1.
    Create a repository.
  2. 2.
    Clone the repository.
  3. 3.
    Add your files locally to the cloned repository.
  4. 4.
    Commit and push your files to the remote repository.
Now your files are tracked under Git and discoverable on

Other Common Formats

Some users may already be storing their files in a consistent file format (for example, filename_date.acd). If this is the case, please reach out directly to [email protected] and we may have some internal tools that we can use to help you to migrate.