Rutas de migración a

En este artículo

If you're moving between products, such as from Enterprise Server to Enterprise Cloud, or from another code hosting platform, such as Bitbucket Server or GitLab, to , 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 's Sales team or see the 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.

Nota:

Enterprise Cloud Importer (ECI) and the GraphQL endpoints for importing migration data to 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 's cloud-based products. We recommend using Enterprise Importer (GEI). See About Enterprise Importer.

You can review the scope and tooling for your migration to .com, which includes migrations to Enterprise Cloud. You can also review any additional information or caveats.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 40GB, consider engaging our 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 .com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 40GB, consider engaging our 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 .com.

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

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer or Expert Services
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 40GB, consider engaging our 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 .com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For repositories with git or metadata archives greater than 40GB, consider engaging our 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 .com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information: Expert Services website
  • Caveats:
    • If you want to migrate GitLab repositories to using Enterprise Importer, please contact our Expert Services team.
    • 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 .com.

This path is not currently supported with our official tools. Please contact Expert Services.

If you're migrating to Enterprise Cloud with data residency, your migration destination is GHE.com.

Migrations to GHE.com use similar tools as migrations to .com. However, the Importer is not available.

Follow a link below to review the scope and tooling for your migration to GHE.com, plus any additional information or caveats.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For complex repositories larger than around 40GB, we recommend contacting Expert Services.
    • 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 GHE.com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For complex repositories larger than around 40GB, we recommend contacting Expert Services.
    • 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 GHE.com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer or Expert Services
  • More information:
  • Caveats:
    • For complex repositories larger than around 40GB, we recommend contacting Expert Services.
    • 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 GHE.com.

  • Scope: Source, history, and metadata
  • Tooling: Enterprise Importer
  • More information:
  • Caveats:
    • For complex repositories larger than around 40GB, we recommend contacting Expert Services.
    • 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 GHE.com.

  • Scope: Source, history, and metadata
  • Tooling: Contact Expert Services
  • More information: Expert Services website
  • Caveats:

You can review the scope and tooling for your migration to Enterprise Server, including any additional information or caveats.

Migrations from .com include Enterprise Cloud.

This path is not currently supported with our official tools. Please contact Expert Services.