Rework data migration docs and add reindex to Serverless steps

deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md

@@ -260,7 +260,7 @@ $$$azure-integration-migrate$$$How do I migrate my data from the classic Azure m
     3. Navigate to Azure and log in as the user that manages the {{es}} resources.
     4. Before proceeding, ensure the new account is configured according to the [prerequisites](#azure-integration-get-started).
     5. Create a [new {{es}} resource](#azure-integration-get-started) for each existing deployment that needs migration from the classic Azure account.
-    6. In the new {{es}} resource, follow the steps in [Restore from a snapshot](../../../manage-data/migrate.md#ec-restore-snapshots) to register the custom snapshot repository from Step 1.
+    6. In the new {{es}} resource, follow the steps in [Restore from a snapshot](/manage-data/migrate/migrate-to-ech-or-ece.md#ec-restore-snapshots) to register the custom snapshot repository from Step 1.
     7. In the same set of steps, restore the snapshot data from the snapshot repository that you registered.
     8. Confirm the data has moved successfully into your new {{es}} resource on Azure.
     9. To remove the old Azure subscription and the old deployments, go to the [Azure SaaS page](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.SaaS%2Fresources) and unsubscribe from the {{ecloud}} ({{es}}) marketplace subscription. This action triggers the existing deployments termination.

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

@@ -80,7 +80,7 @@ A: {{serverless-full}} is available in select AWS, GCP, and Azure regions, with
 ### Data management
 
 **Q: How can I move data to or from {{serverless-short}} projects?**  
-A: We are working on data migration tools. In the interim, [use Logstash](logstash://reference/index.md) with {{es}} input and output plugins to move data to and from {{serverless-short}} projects.
+A: You can migrate data into your {{serverless-short}} projects using either the reindex API or {{ls}}. Refer to [Migrate data to {{serverless-short}}](/manage-data/migrate/migrate-to-serverless.md) to learn more.
 
 **Q: Can I request backups or restores for my serverless projects?**  
 A: Request for project backups or restores is currently unsupported, and we are working on data migration tools to better support this.

manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md

@@ -34,7 +34,7 @@ Before you migrate, review the prerequisites and requirements.
 ### Prerequisites
 * Learn how to [set up and manage snapshot repositories](/deploy-manage/tools/snapshot-and-restore/manage-snapshot-repositories.md). 
 * If restoring to a different cluster, review [Restore to a different cluster](/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#restore-different-cluster).
-* As an alternative migration method, you can [reindex from a remote cluster](/manage-data/migrate.md#ech-reindex-remote).
+* As an alternative migration method, you can [reindex from a remote cluster](/manage-data/migrate/migrate-to-ech-or-ece.md#ech-reindex-remote).
 
 ### Requirements
 * **Cluster size** – The new cluster must be the same size or larger than the old cluster. 
@@ -45,7 +45,7 @@ Before you migrate, review the prerequisites and requirements.
 * **Custom integrations** – Some integrations that use the {{es}} API directly, such as the [Elasticsearch Java Client library](elasticsearch-java://reference/index.md), can require additional handling during cutover.
 
 ## Recommended migration timeline [recommended-migration-timeline]
-Tp complete the migration with minimal downtime, use incremental snapshots. While the exact sequence may differ depending on your infrastructure and operational requirements, you can use the recommended migration timeline as a reliable baseline that you can adapt. Adjust the steps and times to fit your own operational needs.
+To complete the migration with minimal downtime, use incremental snapshots. While the exact sequence might differ depending on your infrastructure and operational requirements, you can use the recommended migration timeline as a reliable baseline that you can adapt. Adjust the steps and times to fit your own operational needs.
 
 1. **09:00**: Take the initial full snapshot of the old cluster. You can also take the initial full snapshot the day before.
 2. **09:30**: Restore the snapshot to the new cluster.

manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md

@@ -3,7 +3,6 @@ navigation_title: Reindex using a private CA
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-remote-reindex.html
 applies_to:
-  serverless: unavailable
   deployment:
     ess: all
 products:
@@ -70,7 +69,7 @@ The `Destination` cluster should be the same or newer version as the `Source` cl
 
 ## Step 5: Reindex from remote `Source` cluster [ec-remote-reindex-step5]
 
-You can now run a remote reindex operation on the {{ech}} `Destination` cluster from the `Source` cluster, as described in the [migration guide](/manage-data/migrate.md#ech-reindex-remote):
+You can now run a remote reindex operation on the {{ech}} `Destination` cluster from the `Source` cluster, as described in the [migration guide](/manage-data/migrate/migrate-to-ech-or-ece.md#ech-reindex-remote).
 
 ```text
 POST _reindex

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

@@ -18,7 +18,7 @@ However, using snapshot and restore for system indices does not mean you must us
 
 ## Migrate system indices using snapshot and restore
 
-To restore system indices from a snapshot, follow the same procedure described in [](../migrate.md#ec-restore-snapshots) and select the appropriate feature states when preparing the restore operation, such as `kibana` or `security`.
+To restore system indices from a snapshot, follow the same procedure described in [](/manage-data/migrate/migrate-to-ech-or-ece.md#ec-restore-snapshots) and select the appropriate feature states when preparing the restore operation, such as `kibana` or `security`.
 
 For more details about restoring feature states, or the entire cluster state, refer to [](/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#restore-feature-state).