Clarify recommended migration tools for each migration path to GitHub (#41812)

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

Author: timrogers

content/migrations/overview/index.md

@@ -9,5 +9,6 @@ versions:
 children:
   - /about-githubs-migration-tooling
   - /planning-your-migration-to-github
+  - /migration-paths-to-github
   - /about-locked-repositories
 ---

content/migrations/overview/migration-paths-to-github.md

@@ -141,88 +141,7 @@ To learn more about expert-led migrations, contact your account representative o
 
 ## Deciding what tools to use
 
-Next, determine the best migration tooling for your desired migration fidelity.
-
-### Source, history, and metadata migrations
-
-For some migration paths, we offer specialist tools that allow you to migrate source, history, and metadata. The appropriate tool depends on your migration path.
-
-<table>
-  <tr>
-    <th></th>
-    <th scope="colgroup" colspan="2" style="text-align: center"><b>Destination</b></th>
-  </tr>
-  <tr>
-    <th scope="col"><b>Origin</b></th>
-    <th scope="col"><b>{% data variables.product.prodname_dotcom_the_website %}, including {% data variables.product.prodname_ghe_cloud %}</b></th>
-    <th scope="col"><b>{% data variables.product.prodname_ghe_server %}</b></th>
-  </tr>
-  <tr>
-    <th scope="row"><b>Azure DevOps (Cloud only)</b></th>
-    <td>{% data variables.product.prodname_importer_proper_name %}</td>
-    <td>None</td>
-  </tr>
-  <tr>
-    <th scope="row"><b>Bitbucket Server</b></th>
-    <td><ul><li><code>bbs-exporter</code> (expert-led migrations only)</li><li>{% data variables.product.prodname_importer_proper_name %} (public beta)</li></ul></td>
-    <td><code>bbs-exporter</code> (expert-led migrations only)</td>
-  </tr>
-  <tr>
-    <th scope="row"><b>GitLab (self-managed or SaaS)</b></th>
-    <td><code>gl-exporter</code> (expert-led migrations only)</td>
-    <td><code>gl-exporter</code> (expert-led migrations only)</td>
-  </tr>
-  <tr>
-    <th scope="row"><b>{% data variables.product.prodname_dotcom_the_website %}, including {% data variables.product.prodname_ghe_cloud %}</b></th>
-    <td><ul><li>{% data variables.product.prodname_importer_proper_name %}</li><li>Enterprise Cloud Importer (expert-led migrations only)</li></ul></td>
-    <td>ghe-migrator</td>
-  </tr>
-  <tr>
-    <th scope="row"><b>{% data variables.product.prodname_ghe_server %}</b></th>
-    <td><ul><li>{% data variables.product.prodname_importer_proper_name %}</li><li>Enterprise Cloud Importer (expert-led migrations only)</li></ul></td>
-    <td>ghe-migrator</td>
-  </tr>
-  </table>
-
-{% data reusables.enterprise-migration-tool.bbs-release-phase %}
-
-If your migration path is not included in the table, then we don’t offer any specialist tools to migrate source, history and metadata. As an alternative, you could run a "source snapshot" or "source and history" migration.
-
-You can learn more about each tool and its use, review the tool's documentation or contact your expert:
-
-- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
-- "[AUTOTITLE]({% ifversion ghae %}/enterprise-server@latest{% endif %}/migrations/using-ghe-migrator)"
-- For tools that are only available with expert-led migrations, contact your account representative or [Expert Services](https://github.com/services/).
-
-### Limitations of specialist tools
-
-Each of our specialist tools has different limitations to consider.
-
-Pay particular attention to restrictions on the repository size. If you need to migrate large repositories, you may need to use a different tool than the one we normally recommend for your migration path.
-
-{% rowheaders %}
-
-| | Tooling available with expert-led migrations | {% data variables.product.prodname_importer_proper_name %} | ghe-migrator |
-|---|---|---|---|
-Supported sources | <ul><li>Bitbucket Server</li><li>GitLab (self-managed and SaaS)</li></ul> | <ul><li>Azure DevOps</li><li>Bitbucket Server (private beta)</li><li>{% data variables.product.company_short %} products (all)</li></ul> | <ul><li>{% data variables.product.prodname_ghe_cloud %}</li><li>{% data variables.product.prodname_ghe_server %}</li></ul>
-Supported targets | {% data variables.product.company_short %} products (all) | {% data variables.product.prodname_dotcom_the_website %}, including {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_server %} |
-Availability | Only when working with Expert Services or a {% data variables.product.prodname_dotcom %} Partner | Open to all | Open to all
-Support  | Provided by your Expert Services team member or {% data variables.product.prodname_dotcom %} Partner | Open to all | Open to all
-Repository size | < 30GB |< 10GB | Unlimited, but subject to your server’s resources
-Data migrated | <ul><li>For Bitbucket, see the [`bbs-exporter`](https://github.github.com/enterprise-migrations/#/./2.2.3.0-export-from-bitbucket-features) documentation</li><li>For GitLab, see the [`gl-exporter`](https://github.github.com/enterprise-migrations/#/./2.2.2.0-export-from-gitlab-features) documentation</li><li>For {% data variables.product.product_name %}, see "[AUTOTITLE]({% ifversion ghae %}/enterprise-server@latest{% endif %}/migrations/using-ghe-migrator/about-ghe-migrator#migrated-data)"</li></ul> | See "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer)" | See "[AUTOTITLE]({% ifversion ghae %}/enterprise-server@latest{% endif %}/migrations/using-ghe-migrator/about-ghe-migrator#migrated-data)"
-
-{% endrowheaders %}
-
-### Source code and history migrations
-
-If your migration path isn’t listed above, then you won’t be able to complete a source, history, and metadata migration. Instead, you’ll be limited to a source snapshot migration or a source and history migration.
-
-- If your repository is hosted on a code hosting service using Git, Subversion (SVN), Mercurial, or Team Foundation Version Control (TFVC/TFS) and is accessible from the public internet, you can use {% data variables.product.company_short %}-provided tools to migrate your source and history.
-  - If you're migrating to {% data variables.product.prodname_dotcom_the_website %}, use {% data variables.product.prodname_dotcom %} Importer. For more information, see "[AUTOTITLE]({% ifversion ghes or ghae %}/free-pro-team@latest{% endif %}/migrations/importing-source-code/using-github-importer)."
-  - If you're migrating to {% data variables.product.prodname_ghe_server %}, use the administrative shell. For more information, see "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-from-other-version-control-systems-with-the-administrative-shell)."
-- If your repository uses SVN for version control and is not accessible from the public internet, you can use the `git svn` command to convert your repository to Git, then push the repository to {% data variables.product.prodname_dotcom %}. For more information, see [Migrating to Git](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git) in the "Pro Git" book.
-- If your repository uses Mercurial for version control and is not accessible from the public internet, you can use `hg-fast-export` to convert your repository to Git, then push the repository to {% data variables.product.prodname_dotcom %}. For more information, see [Migrating to Git](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git) in the "Pro Git" book.
-- If your repository uses Team Foundation Version Control (TFVC) for version control and is not accessible from the public internet, you can use `git-tfs` to convert your repository to Git, then push the repository to {% data variables.product.prodname_dotcom %}. For more information, see the [git-tfs/git-tfs](https://github.com/git-tfs/git-tfs) repository.
+{% data reusables.migrations.about-migration-paths %} For more information, see "[AUTOTITLE](/migrations/overview/migration-paths-to-github)."
 
 ## Designing your organization structure for the migration destination
 

content/migrations/overview/planning-your-migration-to-github.md

@@ -0,0 +1 @@
+To plan for your migration, consider the destination and source. These considerations determine the path for your migration.

data/reusables/migrations/about-migration-paths.md

@@ -1 +1 @@
-If you’re moving between {% data variables.product.company_short %} products, such as from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, or from another code hosting platform, such as Bitbucket Server or GitLab, to {% data variables.product.company_short %}, you’ll want to bring your work with you: your code, the code's history, and all of your past conversations and collaboration.
+If you're moving between {% data variables.product.company_short %} products, such as from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, or from another code hosting platform, such as Bitbucket Server or GitLab, to {% data variables.product.company_short %}, you'll want to bring your work with you: your code, the code's history, and all of your past conversations and collaboration.

data/reusables/migrations/about-migrations.md

@@ -0,0 +1 @@
+For complex repositories larger than around 5 GB, you may need to use `ghe-migrator` and Enterprise Cloud Importer instead. Enterprise Cloud Importer is only available for expert-led migrations.

data/reusables/migrations/large-repositories-require-expert-services.md

@@ -0,0 +1 @@
+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 "[Any Git repository to {% data variables.product.prodname_ghe_server %}](#any-git-repository-to-github-enterprise-server)."

data/reusables/migrations/migration-instructions-for-any-git-repository-to-ghes.md

@@ -0,0 +1 @@
+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 {% data variables.product.prodname_dotcom_the_website %}](#any-git-repository-to-githubcom)."

data/reusables/migrations/migration-instructions-for-any-git-repository-to-githubcom.md

@@ -60,6 +60,9 @@ prodname_student_leader_program_singular: 'GitHub Campus Expert'
 prodname_octernships: 'GitHub Octernships'
 prodname_octernship_singular: 'GitHub Octernship'
 
+# GitHub Expert Services
+prodname_expert_services: 'GitHub Expert Services'
+
 # GitHub CLI
 prodname_cli: 'GitHub CLI'