From b9ac89ea284dded8919a8350ea350022e2f321f2 Mon Sep 17 00:00:00 2001 From: Maddie Duhon Date: Wed, 4 Jun 2025 11:15:32 -0400 Subject: [PATCH] competitors --- .../content/blog/beta-database-migration-tool.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/qdrant-landing/content/blog/beta-database-migration-tool.md b/qdrant-landing/content/blog/beta-database-migration-tool.md index 64c7d3e25..51994b264 100644 --- a/qdrant-landing/content/blog/beta-database-migration-tool.md +++ b/qdrant-landing/content/blog/beta-database-migration-tool.md @@ -25,12 +25,7 @@ This is especially useful if you want to change the collection configuration on 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. -You can also migrate from: -- Chroma -- Pinecone -- Milvus -- Weaviate -- Redis +You can also migrate from, Chroma, Pinecone, Milvus, Weaviate, and Redis. ## Learn more and start migrating easily