Qdrant Model Migration

QdrantOfficialPublished by Qdrant

Skill
Guidelines
Cloud and DevOps
Apache-2.0
No issues found

From the author

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.

— the description by Qdrant

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to updating or changing embedding models within Qdrant collections. It covers strategies for zero-downtime migrations, side-by-side model testing, and hybrid search implementation. The guide distinguishes between version-specific capabilities—such as adding named vector fields in newer versions versus recreating collections in older ones—and offers best practices for data backfilling, dual writes, and alias management to ensure system stability during transitions.

What it does

Outlines zero-downtime migration workflows for updating embedding models.
Explains how to add new vector fields to existing collections on Qdrant v1.18+.
Provides strategies for A/B testing multiple models simultaneously.
Details the process for migrating from dense-only to hybrid search configurations.
Offers guidance on bulk re-embedding and data backfilling performance.
Defines safety protocols for alias swapping and rollback preparation.

When to use it

When you need to switch embedding models without taking your application offline.
When upgrading to a model with different dimensions or a different provider.
When implementing A/B testing for two different embedding models.
When adding sparse vectors or BM25 full-text search to an existing collection.
When you need to validate a new model's quality before fully committing to the switch.

Advantages

Minimizes production downtime through dual-write and alias-swap strategies.
Leverages version-specific features to avoid unnecessary full collection recreations.
Provides clear decision trees for handling different Qdrant server versions.
Includes performance optimization tips for large-scale data migrations.
Reduces risk by emphasizing validation and rollback observation periods.

Usage examples

“How can I switch my Qdrant collection to a new embedding model without downtime?”: The agent will guide you through setting up dual writes to your new collection or adding a new named vector field to your existing collection, followed by a backfill and final alias swap.
“Can I test a new embedding model alongside my current one in Qdrant?”: The agent will explain how to add a second named vector field to your collection (v1.18+) or create a new collection with both fields, allowing you to query both models for comparison.
“I need to add BM25 search to my existing dense vector collection, what is the best way?”: The agent will recommend using a full-text index on v1.20+ if your text is in the payload, or explain the process of adding a sparse vector field if you are on an older version.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/qdrant/qdrant-model-migration/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip qdrant-model-migration.zip -d .agents/skills

Documentation by Qdrant

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. On v1.18+, you can add or delete named vector fields on an existing collection — migration no longer always requires a new collection. On v1.17 or earlier, all named vectors must be defined at collection creation time.

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), or switching to a model with a different dimension count.

You do NOT need to re-embed existing dense vectors if:

Adding BM25 for hybrid search on v1.20+: no vectors to generate. Create a text payload index with scoring enabled on the payload field; Qdrant builds it from the stored payload BM25 scoring
Adding sparse vectors for hybrid search: generate only the sparse vectors. On v1.18+, add the sparse field to the existing collection and backfill it with UpdateVectors. On v1.17 or earlier, copy the dense vectors into the new collection instead of recomputing them Update vectors
Using Matryoshka models: use the dimensions parameter to output lower-dimensional embeddings (some recall loss, good for 100M+ datasets)
Changing quantization (binary to scalar): Qdrant re-quantizes automatically Quantization

Need Zero Downtime

Use when: production must stay available. Recommended for model replacement at scale.

Enable dual writes before backfill, preserving point IDs. Retry and reconcile failed writes to either destination Migration workflow
If the cluster is v1.18 or later AND the collection has named vectors:
- Add the new vector field directly to the existing collection Update vector schema
- Write both embeddings on incoming upserts; backfill only the new field with UpdateVectors. Pause updates/deletes to existing points and drain in-flight operations first, or implement conflict handling to prevent stale backfill Named-vector migration
- After validating completeness and quality, switch the query embedding model and using together; an alias cannot select a vector field
If the cluster is v1.17 or earlier OR the collection doesn't have named vectors:
- Create a new collection with the new model's dimensions and distance metric
- Dual-write live upserts to both collections; backfill embeddings and payloads with update_mode: insert_only (v1.17+) to preserve points already written live. Pause deletes/partial updates or reconcile them so backfill cannot resurrect deleted data Blue-green migration
- Point your application at a collection alias instead of a direct collection name
- Validate completeness and quality before swapping the alias; coordinate the query-model change so requests use the matching vector space Switch collection

Keep dual writes through an observation period for rollback. Retire old vectors or collections only after all readers switch and rollback is no longer needed. Aliases redirect requests; they do not copy payloads.

Need Both Models Live (Side-by-Side)

Use when: A/B testing models, multi-modal (dense + sparse), or evaluating a new model before committing.

For a live collection, apply the write-consistency and cutover safeguards in Need Zero Downtime.

If the cluster is v1.18 or later:
- Add the new vector field directly to the existing collection Update vector schema
- Backfill new model embeddings incrementally using UpdateVectors Update vectors
If the cluster is v1.17 or earlier: You cannot add a named vector to an existing collection. Create a new collection with both vector fields defined upfront:
- Create new collection with old and new named vectors both defined Collection with multiple vectors
- Migrate data from old collection, preserving existing vectors in the old named field
- Backfill new model embeddings incrementally using UpdateVectors Update vectors
- Compare quality by querying with using: "old_model" vs using: "new_model"
- Swap alias to new collection once satisfied

Co-locating large multi-vectors (especially ColBERT) with dense vectors degrades ALL queries, even those only using dense. At millions of points, users report 13s latency dropping to 2s after removing ColBERT. Put large vectors on disk during side-by-side migration.

If you anticipate future model migrations, define both vector fields upfront at collection creation.

Dense to Hybrid Search Migration

Use when: adding sparse/BM25 vectors to an existing dense-only collection. Most common migration pattern.

If the cluster is v1.20 or later and the text is in the payload, prefer BM25 on a full-text index over sparse vectors: create a text index with scoring enabled (plus the language's stemmer and stopwords) on the text field and add a text query prefetch next to the dense one. It needs no schema change, no vector backfill, and no avg_len, and works on a collection of any age. Re-indexing a large collection can take a while BM25 on a full-text index
Use the sparse vector options below on v1.19 or earlier, or when the text isn't stored in the payload.
If the cluster is v1.18 or later, add the sparse vector field directly, even if the dense vector is unnamed Update vector schema
- Generate sparse vectors for existing points and backfill with UpdateVectors; existing dense vectors stay as they are Update vectors
If the cluster is v1.17 or earlier, you cannot add sparse vectors to an existing collection. Recreate it:
- Create new collection with both dense and sparse vector configs defined
- Scroll the old collection with with_vectors=True to copy the dense vectors, and generate only the sparse vectors
- Migrate payloads, swap alias

Sparse vectors and full-text BM25 statistics at chunk level have different TF-IDF characteristics than document level. Test retrieval quality after migration, especially for non-English text without stop-word removal.

Re-embedding Is Too Slow

Use when: dataset is large and re-embedding is the bottleneck.

Use update_mode: insert_only (v1.17+) for backfill into a new collection; it skips existing destination points, so it is not a replacement for UpdateVectors when adding embeddings to existing points Update mode
Scroll the old collection with with_vectors=False, re-embed in batches, upsert into new collection
Upload in parallel batches (64-256 points per request, 2-4 parallel streams) Bulk upload
For Qdrant Cloud inference, switching models is a config change, not a pipeline change Inference docs

For 400GB+ datasets, expect days. For small datasets (<25MB), re-indexing from source is faster than using the migration tool.

What NOT to Do

Assume you can add named vectors to an existing collection on v1.17 or earlier servers; check your server version first
Delete old vectors or collections before validation, reader cutover, and the rollback observation period
Assume dual writes or insert_only alone resolve concurrent deletes and partial updates
Forget to update the query embedding model in your application code
Skip payload migration when using alias swap (aliases redirect requests, they do not copy data)
Keep ColBERT vectors co-located with dense vectors during a long migration (I/O cost degrades all queries)
Migrate to hybrid search without testing BM25 quality at chunk level

Files

ATTRIBUTION.mdAdded by AutoGineer856 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md9.4 KiB

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Qdrant Solutions GmbH

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by

Qdrant

Publisher

Qdrant (Official)

Source

qdrant/skills · skills/qdrant-model-migration · commit 9f55f6a

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

AutoGineer is not affiliated with or endorsed by Qdrant.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download qdrant-model-migration.zip