kanungleandAbdon Pijpelink
544708f293
* create Develop and Deploy tabs; move Operations; re-weight pages * move capacity planning page; create section dropdown content * added aliases to frontmatter * update link references to new canonical links; maintain anchoring * address remaining link issues and errors * fix outlier tutorial reference issue * Treat 'develop' and 'deploy' as a unified search space * fix some frontmatter aliases * add section header redirects * fix 'Operations' redirect to go to 'Deploy' tab * update redirects file for * pattern * add :splat to redirect references * Add wildcard to each entry in _redirects file --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
2.7 KiB
draft, title, short_description, description, preview_image, social_preview_image, title_preview_image, date, author, featured, tags
| draft | title | short_description | description | preview_image | social_preview_image | title_preview_image | date | author | featured | tags | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| false | Vector Data Migration Tool | Qdrant’s vector data migration tool (beta) lets you move data across clusters or regions with one command—no snapshots needed. Try it now. | Migrate data across clusters, regions, from open source to cloud, and more with just one command. | /blog/beta-database-migration-tool/tool-beta.jpg | /blog/beta-database-migration-tool/tool-beta.jpg | /blog/beta-database-migration-tool/tool-beta.jpg | 2025-06-16T00:02:00Z | Qdrant | false |
|
Migrating your data just got easier
We’ve launched the beta of our Qdrant Vector Data Migration Tool, designed to simplify moving data between different instances, whether you're migrating between Qdrant deployments or switching from other vector database providers.
This powerful tool streams all vectors from a source collection to a target Qdrant instance in live batches. It supports migrations from one Qdrant deployment to another, including from open source to Qdrant Cloud or between cloud regions. But that's not all. You can also migrate your data from other vector databases directly into Qdrant. All with a single command.
Unlike Qdrant’s included snapshot migration method, which requires consistent node-specific snapshots, our migration tool enables you to easily migrate data between different Qdrant database clusters in streaming batches. The only requirement is that the vector size and distance function must match.
This is especially useful if you want to change the collection configuration on the target, for example by choosing a different replication factor or quantization method.
The easiest way to run the qdrant migration tool is as a container. You can run it on any machine where you have connectivity to both the source and the target Qdrant databases. Direct connectivity between both databases is not required. For optimal performance, you should run the tool on a machine with a fast network connection and minimum latency to both databases.
Resources
Access the Qdrant Migration Tool
Watch this video to learn how to use it for moving data between Qdrant instances: