Agent skill · research science · github
qdrant-model-migration
Guides embedding model migration in Qdrant without downtime. Use when someone asks 'how to switch embedding models', 'how to migrate vectors', 'how to update to a new model', 'zero-downtime model change', 'how to re-embed my data', or 'can I use two models at once'. Also use when upgrading model dimensions, switching providers, or A/B testing models.
Why this skill is useful
Provides detailed strategies for migrating embedding models in Qdrant, including specific procedures and considerations that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
What to Do When Changing Embedding Models Vectors from different models are incompatible. You cannot mix old and new embeddings in the same vector space. You also cannot add new named vector fields to an existing collection. All named vectors must be defined at collection creation time. Both migration strategies below require creating a new collection. Understand collection aliases before choosing a strategy Collection aliases Can I Avoid Re-embedding? Use when: looking for shortcuts before committing to full migration. You MUST re-embed if: changing model provider (OpenAI to Cohere), changing architecture (CLIP to BGE), incompatible dimension counts across different models, or adding sparse vectors to dense-only collection. You CAN avoid re-embedding if: using Matryoshka models (use dimensions parameter to output lower-dimensional embeddings, learn linear transformation from sample data, some recall loss, good for 100M+ datasets). Or changing quantization (binary to scalar): Qdrant re-quantizes automatically. Quantization Need Zero Downtime (Alias Swap) Use when: production must stay available. Recommended for model replacement at scale. Create a new collection with the new model's dimensions and distance metric Re-embed all data into the new collection in the background Point your application at a collection alias instead of a direct collection name Atomically swap the alias to the new collection Switch collection Verify search quality, then delete the old collection Careful, the alias swap only redirects queries. Payloads must be re-uploaded separately. Need Both Models Live (Side-by-Side) Use when: A/B testing models, multi-modal (dense + sparse), or evaluating a new model before committing. You cannot add a named vector to an existing collection. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/qdrant-model-migration