krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-04 18:38:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

update migration guide

Browse Source
This commit is contained in:
Derrick Mwiti
2025-06-10 09:11:58 +03:00
parent 1c295690cc
commit f3bdf024bb
1 changed files with 0 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/migration.md
-8
View File
@@ -88,14 +88,6 @@ When the migration is complete, you will see the new collection on Qdrant with a
![Migration](/documentation/guides/qdrant-migration.gif) ![Migration](/documentation/guides/qdrant-migration.gif)
## Tips & Best Practices
Here are some best practices to keep in mind when using the Qdrant migration tool:
* Run the tool **close to both source and target** to minimize latency.
* The vector size and distance function must match.
* Always test with a small collection first to validate the setup.
## Conclusion ## Conclusion
The **Qdrant Migration Tool** makes data transfer across vector database instances effortless. Whether you're moving between cloud regions, upgrading from self-hosted to Qdrant Cloud, or switching from other databases such as Pinecone, this tool saves you hours of manual effort. [Try it today](https://github.com/qdrant/migration). The **Qdrant Migration Tool** makes data transfer across vector database instances effortless. Whether you're moving between cloud regions, upgrading from self-hosted to Qdrant Cloud, or switching from other databases such as Pinecone, this tool saves you hours of manual effort. [Try it today](https://github.com/qdrant/migration).