LogoLogo
  • Overview
    • Introduction
      • Git-Based Source Control
      • DeviceLink
    • System Requirements
    • Supported Vendors and Device Types
    • Glossary
  • Git-Based Source Control
    • Getting Started
      • Planning
      • Initial Setup
        • Migrations
    • Basic Tasks
      • Navigation
        • Home page
        • Exploring the Web App
        • Exploring the Desktop App
      • Configuration
        • Creating Repositories
        • Creating Templates
        • Cloning Repositories
      • Operations
        • Pulling
        • Committing
        • Pushing
        • Managing History
        • Binary & Large Files
    • Advanced Tasks
      • Branching
        • Branch Protections
      • Pull Requests & Code Review
        • Contributors
        • Reviewers
      • Merging
    • Additional Features
      • Topics
      • Issues
        • Milestones
        • Labels
        • References and Links
      • Wiki
      • Tags & Releases
      • Webhooks
      • Activity
    • Administration
      • Org Settings
      • User Management
        • External Identity Management (SSO + SCIM)
      • Teams & Permissions
        • Permissions by Account Type
      • Registration & Billing
      • Repo Settings
      • Desktop App Options
      • Profile and Settings
        • Notifications
        • Two-Factor Authentication (2FA)
    • Supported Vendors
      • ABB
      • Beckhoff
      • B&R Automation
      • CODESYS
      • Inductive
      • Lenze
      • Rockwell
        • RSLogix 500
        • RSLogix 5000
        • Studio 5000 Logix Designer
      • Schneider
        • Control Expert
        • Machine Expert
      • Siemens
        • Siemens Step7 TIA Portal
        • Siemens Step7 5.x
      • WAGO
    • Integrations
      • Discord
      • Jira
      • Microsoft Teams Connectors
      • Slack
      • Zapier
      • Microsoft Teams Workflows
  • DeviceLink
    • Getting Started
      • Architecture
      • Planning & Installation
    • Sites and Agents
      • Sites
        • Site Settings
        • File Lists
        • Graphs and Metrics
      • Agents
        • Creating a Site-Based Agent
        • Creating a Multi-Site Agent
    • Projects and Devices
    • Vendor Configuration
      • Beckhoff TwinCAT 3
      • CODESYS v3
      • Copia FTP
      • Copia sFTP/SCP
      • Copia Scripting
      • FANUC Robots
      • Rockwell RSLogix 500
        • Smart Filter
      • Rockwell Studio/RSLogix 5000
        • Smart Filter
      • Rockwell PanelView ME HMI
      • Schneider Control Expert
      • Siemens Step7 TIA Portal
      • Siemens Step7 5.x
    • Jobs
      • Job Navigation
      • Creating Jobs
      • Managing Jobs and History
      • Manual Backups
      • Pull Requests
    • Additional Features
      • Webhooks
      • Copia Import Tool
        • Getting Started
        • Preparing your data
        • Importing your data
        • Rolling back a prior import
    • Administration
      • Teams
      • Permissions
      • Notifications
  • Copilot
    • Copia Copilot
    • Getting Started
    • Using Copia Copilot
  • Copilot FAQ
  • Support
    • Best Practices
    • FAQs
      • Git-Based Source Control
        • Troubleshooting
      • DeviceLink
        • Troubleshooting
Powered by GitBook
On this page
  • Overview
  • Migrating with Git-LFS
  • Migrating a Git Repository
  • Migrate a Copia Repository
  • Generating Access Tokens
  • Migrate a Local Directory Structure

Was this helpful?

  1. Git-Based Source Control
  2. Getting Started
  3. Initial Setup

Migrations

PreviousInitial SetupNextBasic Tasks

Last updated 2 years ago

Was this helpful?

Overview

One of the benefits of Git is that it is quick and easy to migrate to. Onboarding your existing files into a Copia Git repository is just as streamlined.

If your source repository is Git-LFS enabled, please contact Copia for guidance at .

Migrating with Git-LFS

When Git-LFS is involved, migration involves either of the following processes:

  • migrating a repository which is not previously Git-LFS enabled

  • migrating a repository from another vendor to Copia that is already configured for Git-LFS

We recommend you contact Copia for assistance while we continue to add additional documentation, guidance, and features surrounding these use-cases.

Migrating a Git Repository

If Git-LFS is not involved, you must use the Copia Web App to migrate an existing Git repository.

Click the + button in the upper right-hand corner and choose the New Migration option.

Next, select your Git provider. Git, GitHub, and GitLab are currently supported.

If you intend to migrate from GitHub, you must select GitHub rather than the vanilla Git migration option. This is because GitHub no longer supports the Username/Password authentication used by the vanilla Git migration option.

Provide a Migration URL and choose an Organization you'd like to migrate your contents into. After filling out the Repository Name field, click the Migrate Repository button.

Migrate a Copia Repository

The Copia migration option allows users to create an identical copy of an existing Copia repository or migrate repos from a self-hosted Copia instance. If you'd like to migrate additional items such as the Wiki, Issues, Pull Request, and Releases, check the boxes in the "Migration Items" section. If you want to migrate any of these additional items, you'll need an Access Token in place of your password.

Generating Access Tokens

Access Tokens are strings of characters that can be used to authenticate Copia users without using their typical username and password. These tokens should not be shared with anyone and should be stored in a secure location. You can generate your access token by following these steps:

  1. Select "Applications" from the left menu

  2. In the "Manage Access Tokens" section, enter a value in the "Token Name" field and click "Generate Token"

  3. The generated token string will be available at the top of the page. Copy and store it somewhere safe.

Migrate a Local Directory Structure

Some Git users might already have their files in a directory structure. If this is the case, follow the steps below:

  1. Create a repository in the Web App

  2. Clone your repository in the Desktop App

  3. Add your files locally to the cloned repository using your file manager.

  4. Using the Desktop App, commit and push your files to the remote Copia repository.

If you follow this process, your files will be tracked under Git and be discoverable in the Copia Web App.

When logged into , click on your user icon in the upper right corner and select "Settings" from the dropdown menu

app.copia.io
support@copia.io