From 10efb63a46ff9ea6b759a1a4ca8f8bdc1d6793f0 Mon Sep 17 00:00:00 2001 From: Derrick Mwiti <10187095+mwitiderrick@users.noreply.github.com> Date: Wed, 11 Jun 2025 09:29:33 +0300 Subject: [PATCH] Update qdrant-landing/content/documentation/guides/migration.md Co-authored-by: Anush --- qdrant-landing/content/documentation/guides/migration.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/qdrant-landing/content/documentation/guides/migration.md b/qdrant-landing/content/documentation/guides/migration.md index bb68596ba..6fd0ee49e 100644 --- a/qdrant-landing/content/documentation/guides/migration.md +++ b/qdrant-landing/content/documentation/guides/migration.md @@ -11,13 +11,6 @@ You can run the migration tool on any machine where you have connectivity to bot In this tutorial, we will learn how to use the migration tool and walk through a practical example of migrating from other vector databases to Qdrant. -## What is the Qdrant Migration Tool? - -We recently released the **Qdrant Migration Tool (beta)** to make the process of migrating data between vector databases seamless. The tool: - -* Streams vectors in batches from a source Qdrant collection to a target Qdrant collection. -* Works across cloud regions, providers, or deployment types. -* Supports migration of vectors from other providers and other Qdrant instances into Qdrant. ## Why use this instead of Qdrant’s Native Snapshotting?