cyborgdb-migrate
A TUI wizard and CLI for migrating vector data from popular vector databases into CyborgDB — the encrypted vector database.
Supports Pinecone, Qdrant, Weaviate, ChromaDB, and Milvus as sources, with encrypted-at-rest indexes, checkpoint & resume, and post-migration verification built in.
Key Features
- Interactive TUI — step-by-step wizard powered for migration
- Headless CLI — non-interactive mode for scripts and CI/CD pipelines
- Checkpoint & resume — automatically saves progress; resume interrupted migrations
- Spot-check verification — post-migration vector and metadata integrity checks
- Double-buffered I/O — overlaps extraction and upsert for maximum throughput
Getting Started
To get started in minutes, check out the CyborgDB Quickstart Guide.
Installation
pip install cyborgdb-migrate
Install with support for your source database:
# Individual sources
pip install "cyborgdb-migrate[pinecone]"
pip install "cyborgdb-migrate[qdrant]"
pip install "cyborgdb-migrate[weaviate]"
pip install "cyborgdb-migrate[chromadb]"
pip install "cyborgdb-migrate[milvus]"
# All sources at once
pip install "cyborgdb-migrate[all]"
Usage
Interactive (TUI)
cyborgdb-migrate
The wizard walks you through selecting a source, entering credentials, connecting to CyborgDB, and running the migration with live progress.
Headless (CLI)
Create a TOML config file (see example-config.toml):
[source]
type = "pinecone"
api_key = "${PINECONE_API_KEY}"
index = "my-index"
[destination]
host = "http://localhost:8000"
api_key = "${CYBORGDB_API_KEY}"
create_index = true
index_name = "my-cyborgdb-index"
# kms_name = "aws-kms" # optional: use a KMS-wrapped key
[options]
batch_size = 200
checkpoint_every = 10
cyborgdb-migrate --config migration.toml
Resume an interrupted migration:
cyborgdb-migrate --config migration.toml --resume
Supported Sources
| Source | Extras | Notes |
|---|---|---|
| Pinecone | pinecone |
Supports namespaces |
| Qdrant | qdrant |
Scroll-based pagination |
| Weaviate | weaviate |
Supports named vectors |
| ChromaDB | chromadb |
Local and remote modes |
| Milvus | milvus |
Supports partitions, content field heuristic |
Configuration Reference
For full configuration details, CLI options, and exit codes, see the Configuration Guide.
Documentation
For more information on CyborgDB, see the Cyborg Docs.
License
The CyborgDB Migration Tool is licensed under the MIT License.
Metadata
Release files for cyborgdb-migrate 0.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cyborgdb_migrate-0.18.0.tar.gz | 46.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cyborgdb_migrate-0.18.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.2 kB
Release files / cyborgdb_migrate-0.18.0.tar.gz
| Download URL | cyborgdb_migrate-0.18.0.tar.gz |
|---|---|
| Size | 46.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f48c699e8b4cad642fb4ab56765870952efab2a995223b341a916254154c6b3a
|
|
BLAKE2b-256 checksum How to use checksums |
910537073eaa8ead21bb7db1232e2b5ba551c6c6feb09664450f9a93731b5a0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / cyborgdb_migrate-0.18.0-py3-none-any.whl
| Download URL | cyborgdb_migrate-0.18.0-py3-none-any.whl |
|---|---|
| Size | 48.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c775d4a0a12436bf2db297065b6bedfe7d40c39886f0ccb6cb2de3281b3dfabf
|
|
BLAKE2b-256 checksum How to use checksums |
093c400cd44081d09c644ab1f8116f4c7ea1be1332541631438896d95b16039f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log