Skip to main content
Version: User Guides (BYOC)

Migrate from Qdrant to Zilliz Cloud

Qdrant is a vector database that provides similarity search capabilities. Migrating data from Qdrant to Zilliz Cloud allows users to leverage Zilliz Cloud's advanced search and analytics features while maintaining compatibility with the multi-vector structure supported by Qdrant.

This guide provides step-by-step instructions for migrating your data from Qdrant to Zilliz Cloud, including establishing the connection, configuring data mappings, and troubleshooting any issues that arise during the process.

Considerations​

  • When you migrate data from Qdrant to Zilliz Cloud, vector fields are transferred directly, while payloads from Qdrant are stored as JSON in a dynamic field on Zilliz Cloud. For details on the dynamic field feature, refer to Dynamic Field.

  • Null payload values are not supported for migration. Instead of setting a key to hold a null value, remove the key from the payload.

  • To ensure compatibility, Auto ID will be disabled and cannot be modified for each target collection on Zilliz Cloud.

  • Each migration task is limited to a single source Qdrant cluster. You may enable multiple migration jobs if you have data in multiple source clusters.

Before you start​

  • The source Qdrant cluster is accessible from the public internet.

  • If you have an allowlist configured in your network environment, ensure that Zilliz Cloud IP addresses are added to it. For more information, refer to Zilliz Cloud IPs.

  • You have obtained the cluster endpoint and API key with necessary permissions to access the target Qdrant cluster.

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

Migrate from Qdrant to Zilliz Cloud​

migrate_from_qdrant

You can migrate source data to a Zilliz Cloud cluster of any plan tier, provided its CU size can accommodate the source data.

  1. Log in to the Zilliz Cloud console.

  2. Go to the target project page and select Migrations > Qdrant.

  3. In the Connect to Data Source step, enter the Cluster Endpoint and API Key that can be used as credentials to access the target Qdrant cluster. Then, click Next.

    📘Notes

    Database Authentication can guide you on obtaining the required connection information.

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

    📘Notes

    Each source collection you choose to migrate from Qdrant must include at least one vector field and can include up to four vector fields.

  5. In the Configure Schema step,

    1. In Schema Preview, verify the field mapping between your Qdrant collection and the corresponding Zilliz Cloud collection.

      📘Notes

      • The Auto ID is disbaled and cannot be modified.

      • You may rename fields, but the data types are fixed and cannot be changed.

    2. In Advanced Settings, verify the settings of Dynamic Field and Partition Key.

      1. Dynamic Field: Enabled by default and cannot be modified. It stores payloads from the source index, ensuring consistency and maintaining flexibility.

      2. Partition Key: Disabled by default and cannot be modified. This is because payloads from Qdrant are stored as JSON in a dynamic field, which cannot serve as a partition key. In Zilliz Cloud, only scalar fields that are explicitly defined in the schema can be used as partition keys.

    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.

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.