Skip to main content
Version: User Guides (BYOC)

Cross-cluster Migrations

Cross-cluster migrations transfer all existing data from a source cluster to a target cluster. This method supports migrations both within the same organization and across different organizations. It is ideal for scenarios where temporary write interruptions are acceptable, such as during planned maintenance or smaller-scale database transitions.

Before you start​

  • The source Zilliz Cloud cluster is accessible from the public internet.

  • You have been granted the Organization Owner or Project Admin role. If you do not have the necessary permissions, contact your Zilliz Cloud administrator.

📘Notes

Zilliz Cloud also provides RESTful API endpoints for you to migrate data across clusters programmatically. For details, refer to Migrate to Existing Cluster and Migrate to New Dedicated Cluster.

Migrate data within the same organization​

You can migrate data to either a new or existing cluster within the same organization.

cross_cluster_migration_1

  1. Log in to the Zilliz Cloud console.

  2. Go to the target project and select Migrations > In Current Organization.

  3. In the dialog box that appears, configure the source cluster and database and the target cluster:

    • Source Cluster: Choose a source cluster and a database within it.

    • Migrate to: Choose Existing Cluster or New Cluster as the target.

      • Existing Cluster: Select a previously created cluster within the organization.

      • New Cluster: Create a new cluster for the migration.

    • Migration Type: Choose Offline Migration.

  4. Click Next to proceed.

    • If migrating to an existing cluster, you’ll be redirected to the Migrate to an Existing Cluster page to select a target project and target cluster.

    • If migrating to a new cluster, you’ll be redirected to the cluster creation page to set up a new cluster.

  5. Click Migrate to complete.

Monitor the migration process​

Once you click Migrate, a migration job will be generated. You can check the migration progress on the Jobs page. When the job status switches from IN PROGRESS to SUCCESSFUL, the migration is complete.

📘Notes

After migration, verify that the number of collections and entities in the target cluster matches the data source. If discrepancies are found, delete the collections with missing entities and re-migrate them.

verify_collection

Cancel migration job​

If the migration process encounters any issues, you can take the following steps to troubleshoot and resume the migration:

  1. On the Jobs page, identify the failed migration job and cancel it.

  2. Click View Details in the Actions column to access the error log.