diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough.md b/content/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough.md
index 4427de5d675a..83636b22f493 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough.md
@@ -23,7 +23,7 @@ You can enable step debug logging in {% data variables.product.prodname_actions
 ## Creating {% data variables.product.prodname_codeql %} debugging artifacts
 
 You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}.
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow.
+The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), extracted source code files, and any SARIF file(s) produced by the workflow.
 
 These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data.
 
diff --git a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
index 814f897a701c..d90ad38e03ab 100644
--- a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
+++ b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
@@ -68,7 +68,7 @@ Failures that include a `404` status code usually indicate a typo in one of your
 
 ### `Archive generation failed` response
 
-If you receive a `Archive generation failed...` response when migrating from {% data variables.product.prodname_ghe_server %}, your repository is probably too large. For more information about repository size limits, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer#:~:text=Different%20size%20limits%20per%20repository%20apply%20depending%20on%20your%20GHES%20version.)."
+If you receive a `Archive generation failed...` response when migrating from {% data variables.product.prodname_ghe_server %}, your repository is probably too large. For more information about repository size limits, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products#data-that-is-migrated-from-github-enterprise-server)."
 
 First, try excluding releases from the migration by using the `--skip-releases` flag with the `migrate-repo` command.
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md
new file mode 100644
index 000000000000..ef7508638067
--- /dev/null
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md
@@ -0,0 +1,125 @@
+---
+title: About migrations between GitHub products
+shortTitle: About migrations
+intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate between {% data variables.product.company_short %} products.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+---
+
+## About migrations between GitHub products
+
+With {% data variables.product.prodname_importer_proper_name %}, you can migrate data from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, or migrate data between accounts on {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer)."
+
+If your migration source is another account on {% data variables.product.prodname_dotcom_the_website %}, you can migrate individual repositories between organizations, or migrate entire organizations between enterprises. If your migration source is {% data variables.product.prodname_ghe_server %}, you can migrate repositories.
+
+The data that {% data variables.product.prodname_importer_proper_name %} migrates depends on the source of the migration and whether you are migrating a repository or organization.
+
+## Data that is migrated from {% data variables.product.prodname_ghe_server %}
+
+To migrate from {% data variables.product.prodname_ghe_server %} (GHES), you must have GHES version 3.4.1 or higher. The data that is migrated depends on the version you're using.
+
+Item | GHES 3.4.1+ | GHES 3.5.0+ |
+---- | ---------- | ---------- |
+Git source (including commit history) | **X** | **X** |
+Pull requests | **X** | **X** |
+Issues | **X** | **X** |
+Milestones | **X** | **X** |
+Wikis | **X** | **X** |
+Projects (classic) at the repository level | **X** | **X** |
+{% data variables.product.prodname_actions %} workflows | **X** | **X** |
+Commit comments | **X** | **X** |
+Active webhooks | **X** | **X** |
+Branch protections | **X** | **X** |
+{% data variables.product.prodname_pages %} settings | **X** | **X** |
+User history for the above data | **X** | **X** |
+Releases | | **X** |
+
+Different size limits per repository apply depending on your GHES version.
+
+Limit | GHES <3.8.0 | GHES 3.8.0+ |
+----- | ----------- | ----------- |
+Git source | 2GB | 10GB
+Metadata | 2GB | 10GB
+
+{% data reusables.enterprise-migration-tool.data-not-migrated %}
+- Teams
+- User or team access to the repository
+- Repository settings for pull requests
+
+### Branch protections
+
+{% data reusables.enterprise-migration-tool.branch-protection-migration %}
+
+## Data that is migrated from other accounts on {% data variables.product.prodname_dotcom_the_website %}
+
+If your migration source is another account on {% data variables.product.prodname_dotcom_the_website %}, you can migrate individual repositories between organizations, or migrate entire organizations between enterprises.
+
+### Migrated data for an organization
+
+When you migrate an organization, a new organization is created within the destination enterprise account. Then, the following data is migrated to the new organization.
+
+- Teams
+- Repositories
+- Team access to repositories
+- Member privileges
+- Organization-level webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)")
+- Default branch name for new repositories created in the organization
+
+All repositories are migrated with private visibility. If you want to set a repository's visibility to public or internal, you can do this after the migration using the UI or API.
+
+Team membership is **not** migrated. After the migration, you'll need to add members to migrated teams. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#recreating-teams)."
+
+{% note %}
+
+**Note:** {% data reusables.enterprise-migration-tool.team-references %} For more information about how to prevent and resolve these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#team-references-are-broken-after-an-organization-migration)."
+
+{% endnote %}
+
+### Migrated data for a repository
+
+When you migrate a repository, either directly or as part of an organization migration, only the following data is migrated.
+
+- Git source (including commit history)
+- Pull requests
+- Issues
+- Milestones
+- Wikis (excluding attachments)
+- Projects (classic) at the repository level
+- {% data variables.product.prodname_actions %} workflows
+- Commit comments
+- Active webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)")
+- Repository topics
+- Repository settings
+  - Branch protections (see "[Branch protections](#branch-protections)" for more details)
+  - {% data variables.product.prodname_pages %} settings
+  - Autolink references
+  - {% data variables.product.prodname_GH_advanced_security %} settings
+  - Pull request settings
+    - Automatically delete head branches
+    - Allow auto-merge
+    - Allow merge commits (commit message setting is reset to the default message)
+    - Allow squash merging (commit message setting is reset to the default message)
+    - Allow rebase merging
+- Releases (up to 10 GB per repository)
+- User history for the above data
+
+{% data reusables.enterprise-migration-tool.data-not-migrated %}
+- User access to the repository
+
+When you migrate a repository directly, teams and team access to repositories are not migrated.
+
+#### Branch protections
+
+{% data reusables.enterprise-migration-tool.branch-protection-migration %}
+
+## Limitations on migrated data
+
+{% data reusables.enterprise-migration-tool.limitations-of-migrated-data %}
+
+## Getting started
+
+Before you migrate between {% data variables.product.company_short %} products, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first.
+
+For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products)."
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/index.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/index.md
index aef20ff510ee..33595582822e 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/index.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/index.md
@@ -7,6 +7,7 @@ versions:
   ghes: '*'
   ghec: '*'
 children:
+  - /about-migrations-between-github-products
   - /overview-of-a-migration-between-github-products
   - /migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud
   - /migrating-repositories-from-githubcom-to-github-enterprise-cloud
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
index 507248e8dfc6..eded5b606ea2 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
@@ -1,6 +1,6 @@
 ---
 title: Overview of a migration between GitHub products
-shortTitle: Overview
+shortTitle: Overview of a migration
 intro: 'Learn how to complete the entire process of migrating from one {% data variables.product.company_short %} product to another with {% data variables.product.prodname_importer_proper_name %}, from planning to implementation to completing follow-up tasks.'
 versions:
   fpt: '*'
@@ -12,11 +12,11 @@ redirect_from:
   - /migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migrating-between-github-products-with-github-enterprise-importer
 ---
 
-## About migrations between {% data variables.product.company_short %} products
+## Overview
 
 With {% data variables.product.prodname_importer_proper_name %}, you can migrate to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer)".
 
-If you're migrating between {% data variables.product.company_short %} products, such as from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, you can use this guide to plan and implement your migration and complete follow-up tasks. For a full list of supported migration paths, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer#supported-migration-paths)."
+If you're migrating between {% data variables.product.company_short %} products, such as from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, you can use this guide to plan and implement your migration and complete follow-up tasks. For a full list of supported migration paths, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer#supported-migration-paths)."
 
 ## Planning your migration
 
@@ -64,7 +64,7 @@ Migration timing is largely based on the number of pull requests and issues in a
 
 Ensure that you and your stakeholders understand what data can be migrated by {% data variables.product.prodname_importer_proper_name %}.
 
-1. Review the data that's migrated for your migration source. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer)."
+1. Review the data that's migrated for your migration source. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products)."
 1. Make a list of any data that you'll need to manually migrate or recreate.
 
 ### Who will run the migration?
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud.md
new file mode 100644
index 000000000000..6176a003ccc1
--- /dev/null
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud.md
@@ -0,0 +1,38 @@
+---
+title: About migrations from Azure DevOps to GitHub Enterprise Cloud
+shortTitle: About migrations
+intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+---
+
+## About migrations from Azure DevOps
+
+You can use {% data variables.product.prodname_importer_proper_name %} to migrate repositories from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}.
+
+You can only use {% data variables.product.prodname_importer_proper_name %} to migrate from Azure DevOps Cloud, not from Azure DevOps Server. If you currently use Azure DevOps Server and want to migrate to {% data variables.product.prodname_dotcom %}, you can migrate to Azure DevOps Cloud first. For more information, see [Migrate to Azure DevOps](https://azure.microsoft.com/en-us/services/devops/migrate/) on the Azure site.
+
+## Data that is migrated
+
+We currently only support migrating the following repository data from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}.
+
+- Git source (including commit history)
+- Pull requests
+- User history for pull requests
+- Work item links on pull requests
+- Attachments on pull requests
+- Branch protections for the repository (user-scoped branch protections not included)
+
+If you want to migrate Azure Pipelines to {% data variables.product.prodname_actions %}, contact your {% data variables.product.prodname_dotcom %} account manager.
+
+## Limitations on migrated data
+
+{% data reusables.enterprise-migration-tool.limitations-of-migrated-data %}
+
+## Getting started
+
+Before you migrate from Azure DevOps, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first.
+
+For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud)."
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/index.md b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/index.md
index 5ce83495577c..5776138dcab0 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/index.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/index.md
@@ -7,6 +7,7 @@ versions:
   ghes: '*'
   ghec: '*'
 children:
+  - /about-migrations-from-azure-devops-to-github-enterprise-cloud
   - /overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud
   - /migrating-repositories-from-azure-devops-to-github-enterprise-cloud
 ---
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
index 54c4aa6aa984..9ea70a078a49 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: Overview of a migration from Azure DevOps to GitHub Enterprise Cloud
-shortTitle: Overview
+shortTitle: Overview of a migration
 intro: 'Learn how to complete the entire process of migrating from Azure DevOps to {% data variables.product.prodname_dotcom %} with {% data variables.product.prodname_importer_proper_name %}, from planning to implementation to completing follow-up tasks.'
 versions:
   fpt: '*'
@@ -12,7 +12,7 @@ redirect_from:
   - /migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migrating-from-azure-devops-with-github-enterprise-importer
 ---
 
-## About migrations from Azure DevOps
+## Overview
 
 With {% data variables.product.prodname_importer_proper_name %}, you can migrate to {% data variables.product.prodname_ghe_cloud %} on a repository-by-repository basis. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer)".
 
@@ -56,7 +56,7 @@ Because permissions work differently in {% data variables.product.prodname_dotco
 
 Service hooks are not migrated from ADO, so you will need to recreate them separately.
 
-1. Review the data that's migrated from Azure DevOps. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer#azure-devops-migration-support)."
+1. Review the data that's migrated from Azure DevOps. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud)."
 1. Make a list of any data that you'll need to manually migrate or recreate.
 
 ### Who will run the migration?
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md
new file mode 100644
index 000000000000..95d6807af11b
--- /dev/null
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md
@@ -0,0 +1,40 @@
+---
+title: About migrations from Bitbucket Server to GitHub Enterprise Cloud
+shortTitle: About migrations
+intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+---
+
+## About migrations from Bitbucket Server
+
+You can use {% data variables.product.prodname_importer_proper_name %} to migrate repositories from Bitbucket Server to {% data variables.product.prodname_ghe_cloud %}. Migrations from Bitbucket Server are only supported for Bitbucket Server or Bitbucket Data Center version 5.14+ or higher.
+
+## Data that is migrated
+
+We currently only support migrating the following repository data from Bitbucket Server to {% data variables.product.prodname_ghe_cloud %}.
+
+- Git source (including commit history)
+- Pull requests (including comments, pull request reviews, pull request review comments at the file and line level, required reviewers, and attachments)
+
+## Data that is not migrated
+
+Currently, the following data is **not** migrated.
+
+- Personal repositories owned by users
+- Branch permissions
+- Commit comments
+- Repository settings
+- CI pipelines
+
+## Limitations on migrated data
+
+{% data reusables.enterprise-migration-tool.limitations-of-migrated-data %}
+
+## Getting started
+
+Before you migrate from Bitbucket Server, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first.
+
+For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud)."
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/index.md b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/index.md
index e9646fce7f73..882d91f90c7b 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/index.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/index.md
@@ -7,6 +7,7 @@ versions:
   ghes: '*'
   ghec: '*'
 children:
+  - /about-migrations-from-bitbucket-server-to-github-enterprise-cloud
   - /overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud
   - /migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud
 ---
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud.md
index fd55d56052b4..552ab2cbfe0e 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: Overview of a migration from Bitbucket Server to GitHub Enterprise Cloud
-shortTitle: Overview
+shortTitle: Overview of a migration
 intro: 'Learn about the process of migrating from Bitbucket Server to {% data variables.product.prodname_dotcom %} with {% data variables.product.prodname_importer_proper_name %}, from planning to implementation to completing follow-up tasks.'
 versions:
   fpt: '*'
@@ -11,7 +11,7 @@ redirect_from:
   - /migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migrating-from-bitbucket-server-with-github-enterprise-importer
 ---
 
-## About migrations from Bitbucket Server
+## Overview
 
 With {% data variables.product.prodname_importer_proper_name %}, you can migrate to {% data variables.product.prodname_ghe_cloud %} on a repository-by-repository basis. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer)".
 
@@ -49,7 +49,7 @@ For migrations from Bitbucket Server, {% data variables.product.prodname_importe
 
 Because permissions work differently in {% data variables.product.prodname_dotcom %} than in Bitbucket Server, {% data variables.product.prodname_importer_proper_name %} does not attempt to migrate repository permissions from Bitbucket Server. For more information, see "[Configuring permissions](#configuring-permissions)."
 
-1. Review the data that's migrated from Bitbucket Server. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer#bitbucket-server-migration-support)."
+1. Review the data that's migrated from Bitbucket Server. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud)."
 1. Make a list of any data that you'll need to manually migrate or recreate.
 
 ### Who will run the migration?
diff --git a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md
index 9608e503e533..3cd6f674ee82 100644
--- a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md
+++ b/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md
@@ -10,6 +10,9 @@ redirect_from:
   - /early-access/github/migrating-with-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer
   - /early-access/enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer
   - /migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer
+  - /early-access/github/migrating-with-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer
+  - /early-access/enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer
+  - /migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer
 ---
 
 ## About {% data variables.product.prodname_importer_proper_name %}
@@ -31,12 +34,10 @@ You can migrate on a repository-by-repository basis or, if your migration source
 
 {% data reusables.enterprise-migration-tool.supported-migration-paths %}
 
-For more information about which data is migrated for each source, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer)."
+## Getting started
 
-## Getting started with {% data variables.product.prodname_importer_proper_name %}
+To learn more about the migration path you require, and the data that {% data variables.product.prodname_importer_proper_name %} migrates, see the following articles.
 
-To get started with {% data variables.product.prodname_importer_proper_name %}, read the guide for your migration source. Each guide includes all the information you need to plan and implement a migration from that source, as well as follow-up tasks to complete after your migration.
-
-- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud)"
-- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud)"
-- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products)"
+- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud)"
+- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud)"
+- "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products)"
diff --git a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/index.md b/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/index.md
index 8d9f6ed0f42d..f1151c050632 100644
--- a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/index.md
+++ b/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/index.md
@@ -8,7 +8,6 @@ versions:
   ghec: '*'
 children:
   - /about-github-enterprise-importer
-  - /migration-support-for-github-enterprise-importer
 redirect_from:
   - /early-access/github/migrating-with-github-enterprise-importer/understanding-github-enterprise-importer
   - /early-access/enterprise-importer/understanding-github-enterprise-importer
diff --git a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer.md
deleted file mode 100644
index 8701f54c7517..000000000000
--- a/content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer.md
+++ /dev/null
@@ -1,180 +0,0 @@
----
-title: Migration support for GitHub Enterprise Importer
-shortTitle: Migration support
-intro: '{% data variables.product.prodname_importer_proper_name %} migrates a variety of data to {% data variables.product.prodname_dotcom %} from our supported sources.'
-versions:
-  fpt: '*'
-  ghes: '*'
-  ghec: '*'
-redirect_from:
-  - /early-access/github/migrating-with-github-enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer
-  - /early-access/enterprise-importer/understanding-github-enterprise-importer/migration-support-for-github-enterprise-importer
----
-
-## About migration support for {% data variables.product.prodname_importer_proper_name %}
-
-{% data variables.product.prodname_importer_proper_name %} can migrate to {% data variables.product.prodname_ghe_cloud %} from any of our supported migration sources. The data included in each migration depends on the source.
-
-{% data reusables.enterprise-migration-tool.supported-migration-paths %}
-
-During the beta, there are known limitations for the {% data variables.product.prodname_importer_secondary_name %} that apply to all sources.
-
-## Azure DevOps migration support
-
-If your migration source is Azure DevOps, you can migrate repositories.
-
-You can only use {% data variables.product.prodname_importer_proper_name %} to migrate from Azure DevOps Cloud, not from Azure DevOps Server. If you currently use Azure DevOps Server and want to migrate to {% data variables.product.prodname_dotcom %}, you can migrate to Azure DevOps Cloud first. For more information, see [Migrate to Azure DevOps](https://azure.microsoft.com/en-us/services/devops/migrate/) on the Azure site.
-
-We currently only support migrating the following repository data from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}.
-
-- Git source (including commit history)
-- Pull requests
-- User history for pull requests
-- Work item links on pull requests
-- Attachments on pull requests
-- Branch protections for the repository (user-scoped branch protections not included)
-
-If you want to migrate Azure Pipelines to {% data variables.product.prodname_actions %}, contact your {% data variables.product.prodname_dotcom %} account manager.
-
-## Bitbucket Server migration support
-
-Migrations from Bitbucket Server are only supported for Bitbucket Server or Bitbucket Data Center version 5.14+ or higher.
-
-If your migration source is Bitbucket Server, you can migrate repositories. We currently only support migrating the following repository data from Bitbucket Server to {% data variables.product.prodname_ghe_cloud %}.
-
-- Git source (including commit history)
-- Pull requests (including comments, pull request reviews, pull request review comments at the file and line level, required reviewers, and attachments)
-
-Currently, the following data is **not** migrated.
-
-- Personal repositories owned by users
-- Branch permissions
-- Commit comments
-- Repository settings
-
-{% data variables.product.prodname_importer_proper_name %} does not migrate CI pipelines from Bitbucket Server.
-
-## {% data variables.product.prodname_dotcom_the_website %} migration support
-
-If your migration source is {% data variables.product.prodname_dotcom_the_website %}, you can migrate individual repositories or entire organizations.
-
-When you migrate an organization, a new organization is created within the destination enterprise account. Then, the following data is migrated to the new organization.
-
-- Teams
-- Repositories
-- Team access to repositories
-- Member privileges
-- Organization-level webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)")
-- Default branch name for new repositories created in the organization
-
-All repositories are migrated with private visibility. If you want to set a repository's visibility to public or internal, you can do this after the migration using the UI or API.
-
-Team membership is **not** migrated. After the migration, you'll need to add members to migrated teams. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#recreating-teams)."
-
-{% note %}
-
-**Note:** {% data reusables.enterprise-migration-tool.team-references %} For more information about how to prevent and resolve these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#team-references-are-broken-after-an-organization-migration)."
-
-{% endnote %}
-
-When you migrate a repository, either directly or as part of an organization migration, only the following data is migrated.
-
-- Git source (including commit history)
-- Pull requests
-- Issues
-- Milestones
-- Wikis (excluding attachments)
-- Projects (classic) at the repository level
-- {% data variables.product.prodname_actions %} workflows
-- Commit comments
-- Active webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)")
-- Repository topics
-- Repository settings
-  - Branch protections (see "[Branch protections](#branch-protections)" for more details)
-  - {% data variables.product.prodname_pages %} settings
-  - Autolink references
-  - {% data variables.product.prodname_GH_advanced_security %} settings
-  - Pull request settings
-    - Automatically delete head branches
-    - Allow auto-merge
-    - Allow merge commits (commit message setting is reset to the default message)
-    - Allow squash merging (commit message setting is reset to the default message)
-    - Allow rebase merging
-- Releases (up to 10 GB per repository)
-- User history for the above data
-
-{% data reusables.enterprise-migration-tool.data-not-migrated %}
-- User access to the repository
-
-When you migrate a repository directly, teams and team access to repositories are not migrated.
-
-### Branch protections
-
-Branch protections apply a specified set of rules to a specific branch name or branch name pattern. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)."
-
-Branch protections will always be migrated, but certain rules will not be migrated. The following branch protection rules are not migrated.
-
-- Allow specific actors to bypass required pull requests
-- Require approval of the most recent push
-- Require deployments to succeed before merging
-- Lock branch
-- Restrict pushes that create matching branches
-- Allow force pushes
-
-The following limitations also apply:
-
-- If a branch protection rule optionally allows you to specify people, teams, or apps that are exempt from the rule, such as "Restrict who can dismiss pull request reviews," the exceptions will not be migrated.
-- If the "Allow force pushes" rule is enabled in "Specify who can force push" mode, the rule will not be migrated.
-
-## {% data variables.product.prodname_ghe_server %} migration support
-
-If your migration source is {% data variables.product.prodname_ghe_server %}, you can migrate repositories.
-
-To migrate from {% data variables.product.prodname_ghe_server %} (GHES), you must have GHES version 3.4.1 or higher.
-
-Item | GHES 3.4.1+ | GHES 3.5.0+ |
----- | ---------- | ---------- |
-Git source (including commit history) | **X** | **X** |
-Pull requests | **X** | **X** |
-Issues | **X** | **X** |
-Milestones | **X** | **X** |
-Wikis | **X** | **X** |
-Projects (classic) at the repository level | **X** | **X** |
-{% data variables.product.prodname_actions %} workflows | **X** | **X** |
-Commit comments | **X** | **X** |
-Active webhooks | **X** | **X** |
-Branch protections | **X** | **X** |
-{% data variables.product.prodname_pages %} settings | **X** | **X** |
-User history for the above data | **X** | **X** |
-Releases | | **X** |
-
-Different size limits per repository apply depending on your GHES version.
-
-Limit | GHES <3.8.0 | GHES 3.8.0+ |
------ | ----------- | ----------- |
-Git source | 2GB | 10GB
-Metadata | 2GB | 10GB
-
-{% data reusables.enterprise-migration-tool.data-not-migrated %}
-- Teams
-- User or team access to the repository
-- Repository settings for pull requests
-
-## Limitations
-
-There are limits to what {% data variables.product.prodname_importer_proper_name %} can migrate. Some are due to limitations of {% data variables.product.prodname_dotcom_the_website %}, while others are limitations of {% data variables.product.prodname_importer_proper_name %} itself.
-
-### Limitations of {% data variables.product.prodname_dotcom_the_website %}
-
-- **2 GB size limit for a single Git commit:** No single commit in your Git repository can be larger than 2 GB. If any of your commits are larger than 2 GB, you will need to split the commit into smaller commits that are each 2 GB or smaller.
-- **255 byte limit for Git references:** No single [Git reference](https://git-scm.com/book/en/v2/Git-Internals-Git-References), commonly known as a "ref", can have a name larger than 255 bytes. Usually, this means that your references cannot be more than 255 characters long, but any non-[ASCII](https://en.wikipedia.org/wiki/ASCII) characters, such as emojis, may consume more than one byte. If any of your Git references are too large, we'll return a clear error message.
-- **100 MB file size limit:** No single file in your Git repository can be larger than 100 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files)."
-
-### Limitations of {% data variables.product.prodname_importer_proper_name %}
-
-- **10 GB size limit for a Git repository:** This limit only applies to the source code. To inspect the size of your repository, use the [git-sizer](https://github.com/github/git-sizer) tool and check the total size of blobs.
-- **10 GB limit for metadata**: The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 10 GB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
-- **{% data variables.large_files.product_name_short %} objects not migrated**: The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects)."
-- **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks)."
-- **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
-- **Rulesets configured for your organization can cause migrations to fail**: For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
diff --git a/data/reusables/enterprise-migration-tool/branch-protection-migration.md b/data/reusables/enterprise-migration-tool/branch-protection-migration.md
new file mode 100644
index 000000000000..5f516b17fdf7
--- /dev/null
+++ b/data/reusables/enterprise-migration-tool/branch-protection-migration.md
@@ -0,0 +1,15 @@
+Branch protections apply a specified set of rules to a specific branch name or branch name pattern. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)."
+
+Branch protections will always be migrated, but certain rules will not be migrated. The following branch protection rules are not migrated.
+
+- Allow specific actors to bypass required pull requests
+- Require approval of the most recent push
+- Require deployments to succeed before merging
+- Lock branch
+- Restrict pushes that create matching branches
+- Allow force pushes
+
+The following limitations also apply:
+
+- If a branch protection rule optionally allows you to specify people, teams, or apps that are exempt from the rule, such as "Restrict who can dismiss pull request reviews," the exceptions will not be migrated.
+- If the "Allow force pushes" rule is enabled in "Specify who can force push" mode, the rule will not be migrated.
diff --git a/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md b/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md
new file mode 100644
index 000000000000..fa9f2a770371
--- /dev/null
+++ b/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md
@@ -0,0 +1,16 @@
+There are limits to what {% data variables.product.prodname_importer_proper_name %} can migrate. Some are due to limitations of {% data variables.product.prodname_dotcom_the_website %}, while others are limitations of {% data variables.product.prodname_importer_proper_name %} itself.
+
+### Limitations of {% data variables.product.prodname_dotcom_the_website %}
+
+- **2 GB size limit for a single Git commit:** No single commit in your Git repository can be larger than 2 GB. If any of your commits are larger than 2 GB, you will need to split the commit into smaller commits that are each 2 GB or smaller.
+- **255 byte limit for Git references:** No single [Git reference](https://git-scm.com/book/en/v2/Git-Internals-Git-References), commonly known as a "ref", can have a name larger than 255 bytes. Usually, this means that your references cannot be more than 255 characters long, but any non-[ASCII](https://en.wikipedia.org/wiki/ASCII) characters, such as emojis, may consume more than one byte. If any of your Git references are too large, we'll return a clear error message.
+- **100 MB file size limit:** No single file in your Git repository can be larger than 100 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files)."
+
+### Limitations of {% data variables.product.prodname_importer_proper_name %}
+
+- **10 GB size limit for a Git repository:** This limit only applies to the source code. To inspect the size of your repository, use the [git-sizer](https://github.com/github/git-sizer) tool and check the total size of blobs.
+- **10 GB limit for metadata**: The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 10 GB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
+- **{% data variables.large_files.product_name_short %} objects not migrated**: The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects)."
+- **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks)."
+- **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
+- **Rulesets configured for your organization can cause migrations to fail**: For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."