About migration paths to GitHub
If you're moving between GitHub products, such as from GitHub Enterprise Server to GitHub Enterprise Cloud, or from another code hosting platform, such as Bitbucket Server or GitLab, to GitHub, you'll want to bring your work with you: your code, the code's history, and all of your past conversations and collaboration.
To plan for your migration, consider the destination and source. These considerations determine the path for your migration. For some migration paths, we offer specialist tools that allow you to migrate source, history, and metadata. For others, you'll need to perform a simpler "source and history" or "source snapshot" migration.
Some migration paths require tools that are only available with expert-led migrations. For more information, contact your account manager on GitHub's Sales team or see the GitHub Expert Services website.
In our recommendations, we'll assume that you want the highest level of fidelity if possible, which includes source, history, and metadata.
Migrations to GitHub.com
You can review the scope and tooling for your migration to GitHub.com, which includes migrations to GitHub Enterprise Cloud. You can also review any additional information or caveats.
- GitHub Enterprise Server 3.4.1 or newer to GitHub.com
- GitHub Enterprise Server 3.4.0 or older to GitHub.com
- GitHub.com to GitHub.com
- Azure DevOps Services (Azure DevOps Cloud) to GitHub.com
- Azure DevOps Server to GitHub.com
- Bitbucket Cloud (Bitbucket.org) to GitHub.com
- Bitbucket Server or Bitbucket Data Center to GitHub.com
- GitLab to GitHub.com
- Any Git repository to GitHub.com
- Any Mercurial repository to GitHub.com
- Any Subversion (SVN) repository to GitHub.com
- Any Team Foundation Version Control (TFVC) repository to GitHub.com
- Any Perforce repository to GitHub.com
- Any other repository to GitHub.com
- GHE.com to GitHub.com