variable, remove duplicate migration processes

Author: shainaraskas

deploy-manage/deploy/elastic-cloud/heroku-getting-started-accessing.md

@@ -11,7 +11,7 @@ applies_to:
 You use the console to manage your cluster from a web browser. Tasks that are available from the console include upgrading versions, configuring security features, working with custom plugins, and more.
 
 :::{image} ../../../images/cloud-heroku-ech-console.png
-:alt: [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body)
+:alt: [{{heroku}} console](https://cloud.elastic.co?page=docs&placement=docs-body)
 :::
 
 To access the console in a browser from the Heroku CLI:
@@ -21,7 +21,7 @@ heroku addons:open foundelasticsearch --app MY_APP
 Opening https://addons-sso.heroku.com/apps/e286f875-cbdb-47a9-b445-e94bnnnnnnnn/addons/9b883e93-3db3-4491-b620-c3dfnnnnnnnn...
 ```
 
-Alternatively, you can access the console by visiting the [Heroku Dashboard](https://dashboard.heroku.com/), selecting your app, and opening the Elasticsearch link.
+Alternatively, you can access the console by visiting the [Heroku Dashboard](https://dashboard.heroku.com/), selecting your app, and opening the {{es}} link.
 
 
 To learn how to access {{kib}}, refer to [](/deploy-manage/deploy/elastic-cloud/access-kibana.md).

deploy-manage/deploy/elastic-cloud/heroku-getting-started-installing.md

@@ -9,14 +9,14 @@ applies_to:
 
 # Install the add-on [ech-getting-started-installing]
 
-These steps walk you through installing the Elasticsearch Add-On for Heroku from the Heroku CLI. You can either install the latest default version of the add-on or you can install a specific version and include plugins at the same time.
+These steps walk you through installing the {{heroku}} from the Heroku CLI. You can either install the latest default version of the add-on or you can install a specific version and include plugins at the same time.
 
 
 ## Before you begin [echbefore_you_begin] 
 
-The installation steps in this section assume that you have a basic working knowledge of the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) and are familiar with using the command line. To work with the Elasticsearch Add-On for Heroku from the command line, you need to have the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) already installed.
+The installation steps in this section assume that you have a basic working knowledge of the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) and are familiar with using the command line. To work with the {{heroku}} from the command line, you need to have the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) already installed.
 
-If you prefer to install the add-on through your web browser, go to the [Elasticsearch add-on](https://elements.heroku.com/addons/foundelasticsearch) page in the Elements Marketplace, select **Install Elasticsearch**, pick the add-on plan you want, and select **Provision add-on**.
+If you prefer to install the add-on through your web browser, go to the [{{es}} add-on](https://elements.heroku.com/addons/foundelasticsearch) page in the Elements Marketplace, select **Install Elasticsearch**, pick the add-on plan you want, and select **Provision add-on**.
 
 
 ## Steps [echsteps] 
@@ -27,7 +27,7 @@ To install the latest add-on for `MY_APP` using the Heroku CLI:
 heroku addons:create foundelasticsearch --app MY_APP
 ```
 
-After the Elasticsearch Add-On for Heroku gets added, you can find the canonical URL you use to access your newly provisioned cluster in the configuration for the app. Look for the `FOUNDELASTICSEARCH_URL` setting when you grep on the output of the `heroku config` command:
+After the {{heroku}} gets added, you can find the canonical URL you use to access your newly provisioned cluster in the configuration for the app. Look for the `FOUNDELASTICSEARCH_URL` setting when you grep on the output of the `heroku config` command:
 
 ```bash
 heroku config --app MY_APP | grep FOUNDELASTICSEARCH_URL
@@ -38,7 +38,7 @@ FOUNDELASTICSEARCH_URL: https://74f176887fdef36bb51e6e37nnnnnnnn.us-east-1.aws.f
 
 If you want your add-on to run a specific version of Elasticsearch, use the `--elasticsearch-version` parameter. We also provide many of the plugins that are available for Elasticsearch. You use the `--plugins` parameter to specify a comma-separated list of plugins that you want installed.
 
-To find which Elasticsearch versions and plugins are currently available, you can omit the version to default to the latest one and add plugins later on from the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). To use your own custom plugins, you can upload and select these plugins in the console as well.
+To find which {{es}} versions and plugins are currently available, you can omit the version to default to the latest one and add plugins later on from the [{{heroku}} console](https://cloud.elastic.co?page=docs&placement=docs-body). To use your own custom plugins, you can upload and select these plugins in the console as well.
 
 For example: Install the add-on version {{stack-version}} and include the phonetic analysis plugin for  MY_APP:
 

deploy-manage/deploy/elastic-cloud/heroku-migrating.md

@@ -8,14 +8,14 @@ applies_to:
 
 # Migrate between plans [ech-migrating]
 
-Plans for the Elasticsearch Add-On for Heroku differ based on:
+Plans for the {{heroku}} differ based on:
 
 * How much memory and disk space are available
 * How many data centers your cluster is replicated across to achieve high availability
 
-Available memory is an important factor for performance when sizing your Elasticsearch cluster, and replicating across multiple data centers is important for the resilience of production applications.
+Available memory is an important factor for performance when sizing your {{es}} cluster, and replicating across multiple data centers is important for the resilience of production applications.
 
-To learn more about what plans are available for Heroku users, check the [Elasticsearch add-on](https://elements.heroku.com/addons/foundelasticsearch) in the Elements Marketplace.
+To learn more about what plans are available for Heroku users, check the [{{es}} add-on](https://elements.heroku.com/addons/foundelasticsearch) in the Elements Marketplace.
 
 You should time the migration to a new plan to ensure proper application function during the migration process. A cluster that is already overwhelmed with requests will take much longer to migrate to a larger capacity; if your workload warrants a plan change to increase capacity, migrate to a larger plan early.
 

deploy-manage/deploy/elastic-cloud/heroku-reference-hardware.md

@@ -9,18 +9,18 @@ applies_to:
     ess:
 ---
 
-# Elasticsearch Add-On for Heroku hardware [ech-reference-hardware]
+# {{heroku}} hardware [ech-reference-hardware]
 
 {{ech}} deployments use a range of virtualized hardware resources from a cloud provider, such as Amazon EC2 (AWS). Instance configurations enable the products and features of the {{stack}} to run on suitable resources that support their intended purpose. For example, if you have a logging use case that benefits from large amounts of slower but more cost-efficient storage space, you can use large spindle drives rather than more expensive SSD storage. Each instance configuration provides a combination of CPU resources, memory, and storage, all of which you can scale from small to very large.
 
 ::::{note}
 All instances are set to UTC timezone.
 ::::
 
-The Elasticsearch Add-On for Heroku runs exclusively on AWS. To understand the available hardware, refer to the following resources: 
+The {{heroku}} runs exclusively on AWS. To understand the available hardware, refer to the following resources: 
 
 * [The {{ech}} hardware overview](cloud://reference/cloud-hosted/hardware.md)
 * [AWS hardware](cloud://reference/cloud-hosted/aws.md)
 * [AWS default hardware](cloud://reference/cloud-hosted/aws-default.md)
 
-Some hardware profiles might not be available in your region. To learn about regions used by the Elasticsearch Add-On for Heroku, refer to [](/deploy-manage/deploy/elastic-cloud/heroku-reference-regions.md).
+Some hardware profiles might not be available in your region. To learn about regions used by the {{heroku}}, refer to [](/deploy-manage/deploy/elastic-cloud/heroku-reference-regions.md).

deploy-manage/deploy/elastic-cloud/heroku-reference-regions.md

@@ -7,14 +7,14 @@ applies_to:
     ess:
 ---
 
-# Elasticsearch Add-On for Heroku regions [ech-reference-regions]
+# {{heroku}} regions [ech-reference-regions]
 
-A region is the geographic area where the data center of the cloud provider that hosts your deployment is located. Use the information listed here to decide which Elasticsearch Add-On for Heroku region to use. Your choice should be based on:
+A region is the geographic area where the data center of the cloud provider that hosts your deployment is located. Use the information listed here to decide which {{heroku}} region to use. Your choice should be based on:
 
 * Your geographic proximity to the region. Picking a region that is closer to you typically reduces latency for indexing and search requests.
 * The features that we support for the region. Not all regions support the same set of features.
 
-Elasticsearch Add-On for Heroku handles all hosting details for you, no additional accounts with the underlying cloud provider required. The region you select cannot be changed after you create a deployment. If you want to use a different region later on, you can create a new deployment and reindex your data into it.
+{{heroku}} handles all hosting details for you, no additional accounts with the underlying cloud provider required. The region you select cannot be changed after you create a deployment. If you want to use a different region later on, you can create a new deployment and reindex your data into it.
 
 ::::{tip} 
 If you are not sure what to pick, choose a region that is geographically close to you to reduce latency. You should always use HTTPS to connect to the {{stack}} components of your deployment.

deploy-manage/deploy/elastic-cloud/heroku.md

@@ -26,7 +26,7 @@ The {{es}} Add-on for Heroku has several limitations that do not apply to [other
 
 Not all features of {{ecloud}} are available to Heroku users. Specifically, you cannot create additional deployments or use different deployment templates.
 
-Generally, if a feature is shown as available in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body), you can use it.
+Generally, if a feature is shown as available in the [{{heroku}} console](https://cloud.elastic.co?page=docs&placement=docs-body), you can use it.
 
 [{{es}} Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the {{es}} Add-On for Heroku.
 
@@ -63,15 +63,15 @@ Find more information about {{ech}} on the following pages. This information is
 
 ## Next steps [next-steps]
 
-After have provisioned your first deployment, you’re ready to index data into the deployment and explore the advanced capabilities of Elasticsearch Add-On for Heroku.
+After have provisioned your first deployment, you’re ready to index data into the deployment and explore the advanced capabilities of {{heroku}}.
 
 ### Index data [ech-ingest-data] 
 
 There are several ways to ingest data into the deployment:
 
 * Use the sample data available from the {{kib}} home page without loading your own data. There are multiple data sets available and you can add them with one click.
 * Ingest your own data. [Learn more](/manage-data/ingest.md).
-* Have existing Elasticsearch data? Consider your [migration options](../../../manage-data/migrate.md).
+* Have existing {{es}} data? Consider your [migration options](../../../manage-data/migrate.md).
 
 
 ### Increase security [ech-increase-security] 

docset.yml

@@ -421,4 +421,5 @@ subs:
   eck_version: "3.0.0"
   apm_server_version: "9.0.0"
   version: "9.0.0"
-  release-date: "2-April-2025"
+  release-date: "2-April-2025"
+  heroku: "Elasticsearch Add-on for Heroku"

manage-data/migrate.md

@@ -14,7 +14,7 @@ applies_to:
 
 # Migrate your {{es}} data
 
-You might have switched to {{ech}}, {{ece}}, or Elasticsearch Add-On for Heroku for any number of reasons, and you’re likely wondering how to get your existing {{es}} data into your new infrastructure. Along with easily creating as many new deployments with {{es}} clusters that you need, you have several options for moving your data over. Choose the option that works best for you:
+You might have switched to {{ech}} or {{ece}} for any number of reasons, and you’re likely wondering how to get your existing {{es}} data into your new infrastructure. Along with easily creating as many new deployments with {{es}} clusters that you need, you have several options for moving your data over. Choose the option that works best for you:
 
 * Index your data from the original source, which is the simplest method and provides the greatest flexibility for the {{es}} version and ingestion method.
 * Reindex from a remote cluster, which rebuilds the index from scratch.
@@ -36,7 +36,7 @@ Restore from a snapshot
 :   The new cluster must be the same size as your old one, or larger, to accommodate the data. The new cluster must also be an Elasticsearch version that is compatible with the old cluster (check [Elasticsearch snapshot version compatibility](/deploy-manage/tools/snapshot-and-restore.md#snapshot-restore-version-compatibility) for details). If you have not already done so, you will need to [set up snapshots for your old cluster](/deploy-manage/tools/snapshot-and-restore/self-managed.md) using a repository that can be accessed from the new cluster.
 
 Migrating internal {{es}} indices
-:   For {{ech}} and Elasticsearch Add-On for Heroku, if you are migrating internal {{es}} indices from another cluster, specifically the `.kibana` index or the `.security` index, there are two options:
+:   For {{ech}}, if you are migrating internal {{es}} indices from another cluster, specifically the `.kibana` index or the `.security` index, there are two options:
 
     * Use the steps on this page to reindex the internal indices from a remote cluster. The steps for reindexing internal indices and regular, data indices are the same.
     * Check [Migrating internal indices](migrate/migrate-internal-indices.md) to restore the internal {{es}} indices from a snapshot.
@@ -55,7 +55,7 @@ If the original source isn’t available or has other issues that make it non-vi
 
 Through the {{es}} reindex API, you can connect your new {{es}} Service deployment remotely to your old {{es}} cluster. This pulls the data from your old cluster and indexes it into your new one. Reindexing essentially rebuilds the index from scratch and it can be more resource intensive to run.
 
-1. Log in to {{ech}}, {{ece}}, or Elasticsearch Add-On for Heroku.
+1. Log in to {{ech}} or {{ece}}.
 2. Select a deployment or create one.
 3. If the old {{es}} cluster is on a remote host (any type of host accessible over the internet), you need to make sure that the host can be accessed. Access is determined by the {{es}} `reindex.remote.whitelist` user setting.
 
@@ -147,7 +147,7 @@ For {{ece}} users, while it is most common to have Amazon S3 buckets, you should
 
     ::::{tab-set}
 
-    :::{tab-item} {{ech}} and Elasticsearch Add-On for Heroku
+    :::{tab-item} {{ech}}
 
     From the [console](https://cloud.elastic.co?page=docs&placement=docs-body) of the **new** {{es}} cluster, add the snapshot repository.
 

manage-data/migrate/migrate-internal-indices.md

@@ -51,28 +51,12 @@ To restore internal indices from a snapshot, the procedure is a bit different fr
 
 3. To restore internal {{es}} indices, you need to register the snapshot repository in `read-only` mode. 
 
-    ::::{tab-set}
-    
-    :::{tab-item} {{ech}}
     First, add the authentication information for the repository to the {{ech}} keystore, following the steps for your cloud provider:
     * [AWS S3](../../deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md#ec-snapshot-secrets-keystore)
     * [Google Cloud Storage](../../deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md#ec-configure-gcs-keystore)
     * [Azure Blog storage](../../deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md#ec-configure-azure-keystore)
 
     Next, register a read-only repository. Open an {{es}} [API console](../../explore-analyze/query-filter/tools/console.md) and run the [Read-only URL repository](../../deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md) API call.
-    :::
-    
-    :::{tab-item} Elasticsearch Add-On for Heroku
-    First, add the authentication information for the repository to the Elasticsearch Add-On for Heroku keystore, following the steps for your cloud provider:
-    * [AWS S3](../../deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md)
-    * [Google Cloud Storage](../../deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md)
-    * [Azure Blog storage](../../deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md)
-
-    Next, register a read-only repository. Open an {{es}} [API console](../../explore-analyze/query-filter/tools/console.md) and run the [Read-only URL repository](../../deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md) API call.
-
-    :::
-
-    ::::
 
 4. Once the repository has been registered and verified, you are ready to restore the internal indices to your new cluster, either all at once or individually.