Migrate into Weaviate
Tested with: Weaviate 1.39 on Databasezy · zb CLI 0.1
Sources: Weaviate Cloud or self-hosted Weaviate (connection string), another Databasezy instance.
How the copy works
Section titled “How the copy works”Schema first (classes, then cross-references, then tenants), then per class the cursor API
(/v1/objects?after=, with vectors) into /v1/batch/objects. Vectors are copied, so nothing is re-vectorised.
The backup module is not used: it needs a shared storage backend between both sides.
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”Object count per class (and tenant) via Aggregate, and a schema hash. Mismatches are listed in the result; nothing is switched for you.
Not carried over
Section titled “Not carried over”- A class whose vectorizer module is not enabled on the target is created with vectorizer
none. - Only active (HOT) tenants can be read; inactive tenants are created but stay empty.
How migrations work covers preflight, verification and cutover; engine conversions covers moves between engines.