jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-21 10:57:10 -05:00
Code Issues Projects Releases Wiki Activity
Files
c774c238e21d53a513ff96d86a8e9480b51a2807
docs/content/migrations/overview/migration-paths-to-github.md

27 KiB
Raw Blame History

title, shortTitle, intro, versions
title shortTitle intro versions
Migration paths to GitHub Migration paths See an overview of the paths available for migration to {% data variables.product.prodname_dotcom %} from other products, or between {% data variables.product.prodname_dotcom %} products.
fpt ghes ghec
* * *

About migration paths to {% data variables.product.prodname_dotcom %}

{% data reusables.migrations.about-migrations %}

{% data reusables.migrations.about-migration-paths %} 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 {% data variables.contact.contact_enterprise_sales %} or see the {% data variables.product.prodname_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 {% data variables.product.prodname_dotcom_the_website %}

You can review the scope and tooling for your migration to {% data variables.product.prodname_dotcom_the_website %}, which includes migrations to {% data variables.product.prodname_ghe_cloud %}. You can also review any additional information or caveats.

{% data variables.product.prodname_ghe_server %} 3.4.1 or newer to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}

{% data variables.product.prodname_ghe_server %} 3.4.0 or older to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}

{% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_dotcom_the_website %}

Migrations from {% data variables.product.prodname_dotcom_the_website %} include {% data variables.product.prodname_ghe_cloud %}. This path includes adoption of {% data variables.product.prodname_emus %} or a move between managed enterprises.

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %} or {% data variables.product.prodname_expert_services %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}

Azure DevOps Services (Azure DevOps Cloud) to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information: AUTOTITLE

Azure DevOps Server to {% data variables.product.prodname_dotcom_the_website %}

Bitbucket Cloud (Bitbucket.org) to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: Git CLI or {% data variables.product.prodname_importer %}
  • More information:
    • AUTOTITLE
    • [AUTOTITLE]({% ifversion ghes %}/free-pro-team@latest{% endif %}/migrations/importing-source-code/using-github-importer/about-github-importer)

Bitbucket Server or Bitbucket Data Center to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • For complex repositories larger than around 5 GB, you may need to use bbs-exporter and Enterprise Cloud Importer instead. Enterprise Cloud Importer is only available for expert-led migrations.
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}

GitLab to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source, history, and metadata
  • Tooling: gl-exporter, then Enterprise Cloud Importer (expert-led migrations only)
  • More information: {% data variables.product.prodname_expert_services %} website
  • Caveats:
    • Enterprise Cloud Importer is only available for expert-led migrations.
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}

Any Git repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: Git CLI or {% data variables.product.prodname_importer %} if the repository is accessible over the public internet
  • More information:
    • AUTOTITLE
    • [AUTOTITLE]({% ifversion ghes %}/free-pro-team@latest{% endif %}/migrations/importing-source-code/using-github-importer/about-github-importer)

Any Mercurial repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: Mercurial, Git CLI, and Python
  • More information: AUTOTITLE

Any Subversion (SVN) repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: Subversion and Git CLI
  • More information: AUTOTITLE

Any Team Foundation Version Control (TFVC) repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: Azure Repos, then Git CLI
  • More information: AUTOTITLE

Any Perforce repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source and history
  • Tooling: git-p4, then Git CLI
  • More information:

Any other repository to {% data variables.product.prodname_dotcom_the_website %}

  • Scope: Source snapshot
  • Tooling: {% data variables.product.prodname_cli %} or Git CLI
  • More information: AUTOTITLE

{% data variables.enterprise.data_residency_site %} to {% data variables.product.prodname_dotcom_the_website %}

This path is not currently supported with our official tools. Please contact {% data variables.product.prodname_expert_services %}.

Migrations to {% data variables.enterprise.data_residency_site %}

If you're migrating to {% data variables.enterprise.data_residency %}, your migration destination is {% data variables.enterprise.data_residency_site %}.

Migrations to {% data variables.enterprise.data_residency_site %} use similar tools as migrations to {% data variables.product.prodname_dotcom_the_website %}. However, the {% data variables.product.prodname_importer %} and Enterprise Cloud Importer are not available.

Follow a link below to review the scope and tooling for your migration to {% data variables.enterprise.data_residency_site %}, plus any additional information or caveats.

{% data variables.product.prodname_ghe_server %} 3.4.1 or newer to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services-ghecom %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}

{% data variables.product.prodname_ghe_server %} 3.4.0 or older to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services-ghecom %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}

{% data variables.product.prodname_dotcom_the_website %} to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %} or {% data variables.product.prodname_expert_services %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services-ghecom %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}

Azure DevOps Services (Azure DevOps Cloud) to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information: AUTOTITLE

Azure DevOps Server to {% data variables.enterprise.data_residency_site %}

Bitbucket Cloud (Bitbucket.org) to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: Git CLI
  • More information:

Bitbucket Server or Bitbucket Data Center to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: {% data variables.product.prodname_importer_proper_name %}
  • More information:
  • Caveats:
    • {% data reusables.migrations.large-repositories-require-expert-services-ghecom %}
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}

GitLab to {% data variables.enterprise.data_residency_site %}

  • Scope: Source, history, and metadata
  • Tooling: Contact {% data variables.product.prodname_expert_services %}
  • More information: {% data variables.product.prodname_expert_services %} website
  • Caveats:
    • {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}

Any Git repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: Git CLI
  • More information:

Any Mercurial repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: Mercurial, Git CLI, and Python
  • More information: AUTOTITLE

Any Subversion (SVN) repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: Subversion and Git CLI
  • More information: AUTOTITLE

Any Team Foundation Version Control (TFVC) repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: Azure Repos, then Git CLI
  • More information: AUTOTITLE

Any Perforce repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source and history
  • Tooling: git-p4, then Git CLI
  • More information:

Any other repository to {% data variables.enterprise.data_residency_site %}

  • Scope: Source snapshot
  • Tooling: {% data variables.product.prodname_cli %} or Git CLI
  • More information: AUTOTITLE

Migrations to {% data variables.product.prodname_ghe_server %}

You can review the scope and tooling for your migration to {% data variables.product.prodname_ghe_server %}, including any additional information or caveats.

{% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}

Migrations from {% data variables.product.prodname_dotcom_the_website %} include {% data variables.product.prodname_ghe_cloud %}.

  • Scope: Source, history, and metadata
  • Tooling: Organization migrations API, then ghe-migrator
  • More information:

{% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_server %}

  • Scope: Source, history, and metadata
  • Tooling: Organization migrations API, then ghe-migrator
  • More information:

Azure DevOps to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Git CLI
  • More information: AUTOTITLE

Bitbucket Cloud (Bitbucket.org) to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Git CLI
  • More information: AUTOTITLE

Bitbucket Server or Bitbucket Data Center to {% data variables.product.prodname_ghe_server %}

GitLab to {% data variables.product.prodname_ghe_server %}

Any Git repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Git CLI
  • More information: AUTOTITLE

Any Mercurial repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Mercurial, Git CLI, and Python
  • More information: AUTOTITLE

Any Subversion (SVN) repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Subversion and Git CLI
  • More information: AUTOTITLE

Any Team Foundation Version Control (TFVC) repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: Azure Repos, then Git CLI
  • More information: AUTOTITLE

Any Perforce repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source and history
  • Tooling: git-p4, then Git CLI
  • More information:

Any other repository to {% data variables.product.prodname_ghe_server %}

  • Scope: Source snapshot
  • Tooling: {% data variables.product.prodname_cli %} or Git CLI
  • More information: AUTOTITLE

{% data variables.enterprise.data_residency_site %} to {% data variables.product.prodname_ghe_server %}

This path is not currently supported with our official tools. Please contact {% data variables.product.prodname_expert_services %}.

Reference in New Issue View Git Blame Copy Permalink