Migrate into Qdrant
Tested with: Qdrant 1.19 on Databasezy · zb CLI 0.1
Sources: Qdrant Cloud or self-hosted Qdrant (connection string), another Databasezy instance.
How the copy works
Section titled “How the copy works”Per collection, the fast path is a snapshot: create it on the source, download it into the migration Job and
upload it to the target, when both versions are compatible and the source is a single node. Otherwise the collection
is created from the source config (vectors, HNSW, quantization, payload indexes) and points are scrolled and upserted
with their vectors and payloads. The API key goes in the URL password slot or ?api_key=.
Run it
Section titled “Run it”# --dry-run prints the preflight checklist and the exact plan without changing anythingFollow it with zb migrate status <mig_id>, or in the portal under the instance’s Migrate in tab.
What is verified
Section titled “What is verified”Exact point count per collection (/points/count) and a hash of the vector configuration. Mismatches are listed in the result; nothing is switched for you.
Not carried over
Section titled “Not carried over”- Aliases and shard keys are not copied.
- Points upserted during the copy may be missed (no sync).
How migrations work covers preflight, verification and cutover; engine conversions covers moves between engines.