Skip to main content
Version: User Guides (BYOC)

Migrate from Milvus to Zilliz Cloud Via Endpoint

Zilliz Cloud offers Milvus as a fully managed, cloud-hosted solution for users who want to use the Milvus vector database without the need to manage the infrastructure themselves. To enable smooth migration, you can migrate data from Milvus to Zilliz Cloud in these ways - connecting to source Milvus via database endpoint or uploading backup files directly.

This topic describes how to migrate from Milvus via database endpoint. For information on how to upload backup files, refer to Via Backup Files.

Considerations​

  • Each migration task is limited to a single source Milvus database. If you have data in multiple source databases, you can set up separate migration jobs for each one.

  • During the migration process, Zilliz Cloud will replicate the exact collection schema from the source Milvus collection. Modifying the schema is not allowed while the migration is in progress.

Before you start​

  • The source Milvus instance is running version 2.x or later and is accessible from the public internet.

  • If authentication has been enabled for the source Milvus, make sure you have obtained necessary connection credentials. For details, refer to Authenticate User Access.

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

Migrate from Milvus via database endpoint​

You can migrate one or more collections from a single Milvus database at a time.

  1. Log in to the Zilliz Cloud console.

  2. Go to the target project and select Migrations > Milvus > Via Endpoint.

  3. In the Database Endpoint field of the Connect to Data Source step, enter the server address of the source Milvus. If authentication has been enabled for the source Milvus, enter Username and Password as access credentials. Then, click Next.

  4. In the Select Source and Target step, configure settings for the source Milvus and target Zilliz Cloud cluster. Then, click Next.

  5. In the Configure Schema step,

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

    2. In Advanced Settings, verify Dynamic Field and Partition Key settings, which inherits the settings of the source collection and cannot be altered. For more information, refer to Dynamic data fields and Use Partition Key.

    3. In Target Collection Name and Description, 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.

migrate_from_milvus_via_endpoint_1

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.