Closing down of Enterprise Cloud Importer (ECI) and supporting repository import GraphQL endpoints [Closing down] (#55030)

Author: rachaelrenk

content/migrations/overview/about-locked-repositories.md

@@ -53,16 +53,6 @@ If you're sure you want to use the repository, a site administrator can unlock t
 
 The source repository is not locked by default, only if the `--lock` argument is specified when preparing the repository for export with the `ghe-migrator add` command. To unlock the repository, use the `ghe-migrator unlock` command. For more information, see [AUTOTITLE](/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server#unlocking-repositories-on-the-source).
 
-## Repositories locked by Enterprise Cloud Importer
-
-When you use Enterprise Cloud Importer, the destination repository is locked by default and is not automatically unlocked.
-
-If the import succeeded, you can unlock the repository by clicking the **Unlock** button in Enterprise Cloud Importer.
-
-If the import failed, you cannot unlock the repository yourself. Because a failed migration means that not all of your data has been migrated, we recommend deleting the repository and retrying the migration, to prevent data loss.
-
-If you’re sure you want to unlock the repository, contact {% data variables.contact.contact_support %}.
-
 ## Repositories locked by the `startImport` GraphQL mutation
 
 When you use the `startImport` GraphQL mutation, the destination repository is locked by default and is not automatically unlocked.

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

@@ -18,6 +18,13 @@ Some migration paths require tools that are only available with expert-led migra
 
 In our recommendations, we'll assume that you want the highest level of fidelity if possible, which includes source, history, and metadata.
 
+<!-- expires 2025-06-30 -->
+
+> [!NOTE]
+> Enterprise Cloud Importer (ECI) and the GraphQL endpoints for importing migration data to {% data variables.product.prodname_ghe_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 {% data variables.product.prodname_importer_proper_name %} (GEI). See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer).
+
+<!-- end expires 2025-06-30 -->
+
 ## 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.
@@ -104,16 +111,16 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
   * [AUTOTITLE](/migrations/using-github-enterprise-importer)
   * [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
 * **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.large-repositories-require-expert-services %}
   * {% 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)
+* **Tooling:** {% data variables.product.prodname_importer_proper_name %}
 * **More information:** [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
 * **Caveats:**
-  * Enterprise Cloud Importer is only available for expert-led migrations.
+  * If you want to migrate GitLab repositories to GitHub using {% data variables.product.prodname_importer_proper_name %}, please contact our {% data variables.product.prodname_expert_services %} team.
   * {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}
 
 ### Any Git repository to {% data variables.product.prodname_dotcom_the_website %}
@@ -164,7 +171,7 @@ This path is not currently supported with our official tools. Please contact {%
 
 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.
+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 %} is 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/reusables/migrations/large-repositories-require-expert-services.md

@@ -1 +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.
+For repositories with git or metadata archives greater than 20GB, consider engaging our {% data variables.product.prodname_expert_services %} to help bring your large repositories within Enterprise Cloud Importer limits.

data/reusables/support/scope-of-support.md

@@ -1,7 +1,6 @@
 If your support request is outside of the scope of what our team can help you with, we may recommend next steps to resolve your issue outside of {% data variables.contact.github_support %}. Your support request is possibly out of {% data variables.contact.github_support %}'s scope if the request is primarily about:
 
-* Third party integrations, such as Jira
-* Enterprise Cloud Importer (available only with expert-led migrations){% ifversion ghes %}
+* Third party integrations, such as Jira{% ifversion ghes %}
 * Hardware setup{% endif %}
 * CI/CD, such as Jenkins
 * Writing scripts