This version of GitHub Enterprise Server was discontinued on 2025-04-03. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

Migration paths to GitHub

See an overview of the paths available for migration to GitHub from other products, or between GitHub products.

In this article

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.

Note

Enterprise Cloud Importer (ECI) and the GraphQL endpoints for importing migration data to GitHub Enterprise Cloud from an archive are closing down on March 31, 2025. After this date, these tools can not be used to import repository data into GitHub's cloud-based products. We recommend using GitHub Enterprise Importer (GEI). See About GitHub Enterprise Importer.

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

  • Scope: Source, history, and metadata
  • Tooling: GitHub Enterprise Importer
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 20GB, consider engaging our GitHub Expert Services to help bring your large repositories within Enterprise Cloud Importer limits.
    • If an expert-led migration isn't right for you, you can perform a "source and history" migration of the affected repositories instead. For more information, see Migrations from any Git repository to GitHub.com.

GitHub Enterprise Server 3.4.0 or older to GitHub.com

  • Scope: Source, history, and metadata
  • Tooling: GitHub Enterprise Importer
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 20GB, consider engaging our GitHub Expert Services to help bring your large repositories within Enterprise Cloud Importer limits.
    • If an expert-led migration isn't right for you, you can perform a "source and history" migration of the affected repositories instead. For more information, see Migrations from any Git repository to GitHub.com.

GitHub.com to GitHub.com

Migrations from GitHub.com include GitHub Enterprise Cloud. This path includes adoption of Enterprise Managed Users or a move between managed enterprises.

  • Scope: Source, history, and metadata
  • Tooling: GitHub Enterprise Importer or GitHub Expert Services
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 20GB, consider engaging our GitHub Expert Services to help bring your large repositories within Enterprise Cloud Importer limits.
    • If an expert-led migration isn't right for you, you can perform a "source and history" migration of the affected repositories instead. For more information, see Migrations from any Git repository to GitHub.com.

Azure DevOps Services (Azure DevOps Cloud) to GitHub.com

Azure DevOps Server to GitHub.com

  • Scope: Source, history, and metadata
  • Tooling: Migration to Azure DevOps Services, then GitHub Enterprise Importer
  • More information: