Skip to main content
Version: User Guides (Cloud)

Cross-Cluster Migrations

Zilliz Cloud allows you to migrate data between clusters, whether they are within the same organization or across different organizations. This capability ensures flexibility in managing and scaling your resources. When migrating data to a cluster in a different organization, you must provide the appropriate authentication credentials, such as an API key or a token consisting of a username and its password.

Considerations​

  • For optimal performance, migrations from a higher plan tier to a lower one (e.g., Dedicated to Serverless, Dedicated to Free, Free to Free clusters) are not supported.

  • For each migration task, you can select only one vector field from each source collection.

Before you start​

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

  • For cross-organization migration, ensure you have the required connection information for the target Zilliz Cloud cluster, including the public endpoint, API key, or cluster username and password.

  • 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.

  1. Log in to the Zilliz Cloud console.

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

  3. In the Migration Settings dialog box, specify the source and target clusters and click Confirm. Ensure the plan tier of the target cluster is not lower than that of the source cluster (e.g., migration from a Dedicated cluster to a Free or Serverless cluster is not supported). For more information on cluster plans, refer to Select the Right Cluster Plan.

    📘Notes

    When migrating data, you have the option to create a new target cluster or use an existing one within the same organization. The source cluster should be selected from the available clusters in the current project.

  4. Click Migrate.

cross_cluster_migration_1

Migrate data across organizations​

Migrating data across organizations requires you to provide the necessary connection credentials (source cluster endpoint, API key, or username and password) to access the source cluster in a different organization.

  1. Log in to the Zilliz Cloud console.

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

  3. In the Connect to Data Source step, configure connection information for the source cluster. Then, click Next.

  4. In the Select Source and Target step, configure settings for the source and target clusters. Then, click Next.

  5. In the Configure Schema step,

    1. Review the target collections and their field settings in the schema preview.

    2. (Optional) In Advanced Settings, configure Dynamic Field and Partition Key. For more information, refer to Dynamic data fields and Use Partition Key.

    3. (Optional) In General Information, customize the target collection name and description. The collection name must be unique in each cluster. If the name duplicates an existing one, rename the collection.

  6. Click Migrate.

cross_cluster_migration_2

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.