PolignVector Transfer
Docs

VECTOR TRANSFER

Move your vectors.
Keep your progress.

Move dense embeddings, IDs and metadata between Pinecone, Qdrant, Milvus, pgvector, Polign and 10 more databases. Run transfers in your infrastructure or on Polign, with batch checkpoints and resume after interruptions.

Sign in with Polign Read the guide

Local demo: 1,000 sample vectors. No account or database credentials.

SOURCE & DESTINATION

15 database connectors

Compatibility & requirements
  • Pinecone
  • Qdrant
  • Milvus
  • pgvector
  • Polign
  • Weaviate
  • Elasticsearch
  • OpenSearch
  • S3 Vectors
  • Chroma
  • Redis
  • MongoDB
  • FAISS
  • Solr
  • Turbopuffer

Each connector supports reads and writes within its documented limits. Pinecone sources require serverless ID listing; Polign sources require collection listing support. FAISS uses an HTTP adapter.

TRY IT ON YOUR MACHINE

From download to your first transfer.

Run a real transfer from a built-in sample source to local JSON files. The demo uses the same transfer engine and dashboard, with no cloud database calls.

  1. Choose your platform and run the commands.
  2. Open 127.0.0.1:23005 . Choose New transfer, then Start transfer; the sample connections and dimension are prefilled.
  3. Watch 1,000 records complete. Inspect the JSON files in transfer-demo/demo-vectors/.

The demo listens only on your machine. No sign-in or access token is needed. Stop it with Ctrl+C; its job history stays on disk.

Use your own databases with a self-hosted server →
curl -fSLO https://transfer.polign.com/downloads/vtransfer-darwin-arm64 &&
curl -fSLO https://transfer.polign.com/downloads/SHA256SUMS &&
shasum -a 256 --ignore-missing --check SHA256SUMS &&
chmod +x vtransfer-darwin-arm64 &&
./vtransfer-darwin-arm64 serve -demo -data ./transfer-demo

Run in an empty folder. Requires curl; no Go installation needed.

WHERE YOUR DATA GOES

Choose where the transfer runs.

Worker & credential guide
Your infrastructure

Run your own worker

SourceYour workerDestination

Database credentials, vectors, record metadata and checkpoints stay on your worker and databases. The Polign dashboard schedules jobs and receives connection capabilities, status and progress—not vector payloads.

The worker connects outbound over HTTPS. It can reach private databases on your network; no inbound ports are required.

Set up a worker →
Polign hosted

Run on Polign

SourcePolign serverDestination

Polign connects to both databases and processes your vectors and record metadata. Saved database credentials are encrypted at rest and decrypted by the service to execute transfers.

This mode trusts Polign’s runtime and administrators with those credentials and data. Database endpoints must be publicly reachable with verified TLS.

Hosted setup & credential handling →

TRANSFER BEHAVIOR

Know what a resume will do.

Read the transfer semantics

Checkpoints after acknowledgement

A checkpoint advances after the destination acknowledges the whole batch. Temporary failures retry. Fix a failed job and resume from its saved checkpoint. A crash before checkpointing can replay a batch.

Matching IDs are replaced

Writes are upserts using the source IDs. Existing destination records with those IDs are replaced; IDs are not silently renamed. Canceling a job does not roll back writes already made.

Bring a compatible destination

Keep the source unchanged through transfer and resume. Prepare the destination’s schema, dimensions and ID types. Transfers do not regenerate embeddings, copy index definitions or convert incompatible metadata.

BEFORE YOUR FIRST MIGRATION

Read the guide. Check your connector.

Setup, credential boundaries, recovery and provider requirements—all available without signing in.

New transfer

Choose a connected worker or run on Polign. Review the connections, then start.

Source
Destination
Advanced settings

Temporary failures retry automatically. Resume starts at the last checkpoint.

Matching destination IDs are replaced. Source data stays in place.

Update credentials

Replace credentials without changing database settings or checkpoints.

Control plane access

Enter the operator token configured for this server. It stays in memory for this tab.