All Products
Search

This Product

    Elasticsearch:migrate using the online migration tool

    Document Center

    Elasticsearch:migrate using the online migration tool

    Last Updated:Mar 11, 2026

    Migration Solution Description

    The node merge migration solution combines an existing Elasticsearch cluster (old Elasticsearch) and a new Elasticsearch cluster into a single large cluster. After the merge, perform a grayscale migration of the old Elasticsearch data. The migration process proceeds sequentially, involving replica migration, primary node migration, and primary shard migration. After the data migration completes, use the new Elasticsearch for subsequent services. Concurrently, stop services for the old Elasticsearch.

    Note

    • Old Elasticsearch: The Elasticsearch to be migrated or upgraded.

    • New Elasticsearch: The Elasticsearch used after migration or upgrade.

    Supported Migration or Upgrade Scenarios

    The online migration tool supports the following migration or upgrade scenarios:

    • Migrate self-managed Elasticsearch data to Alibaba Cloud: Migrate self-managed Elasticsearch cluster data, deployed on IDC ECS, to fully managed Alibaba Cloud Elasticsearch. This ensures a smooth, highly available, and zero-downtime migration.

      Note

      During migration:

      • To ensure Alibaba Cloud Elasticsearch can access your self-managed cluster, add the Alibaba Cloud Elasticsearch service CIDR block to the security group of the ECS instance that hosts your self-managed cluster. This allows the specified CIDR block to access the ECS instance through ports 9200 and 9300.

      • Prepare the decrypted ES p12 file beforehand. During subsequent data migration, the P12 file ensures normal communication between nodes.

    • Upgrade Alibaba Cloud Elasticsearch V2 architecture instances to V3 architecture: Efficiently and seamlessly upgrade Alibaba Cloud Elasticsearch instances deployed in Basic Management (V2) mode to Cloud-Native New Management (V3) deployment mode. Data migration automatically completes during the upgrade. The instance endpoint remains unchanged before and after the architecture upgrade and data migration.

      Note

      During the upgrade, the system automatically detects the configuration of the V2 architecture instance and creates a V3 architecture instance based on this configuration.

    For more information on migration or upgrade limits and operation details, see the detailed documentation for the corresponding scenarios.