From a28befaf3d09c7819fa79fb00a333cebbb381ce9 Mon Sep 17 00:00:00 2001 From: Derrick Mwiti <10187095+mwitiderrick@users.noreply.github.com> Date: Wed, 11 Jun 2025 09:29:49 +0300 Subject: [PATCH] Update qdrant-landing/content/documentation/guides/migration.md Co-authored-by: Anush --- qdrant-landing/content/documentation/guides/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/guides/migration.md b/qdrant-landing/content/documentation/guides/migration.md index 6fd0ee49e..60b4e61ef 100644 --- a/qdrant-landing/content/documentation/guides/migration.md +++ b/qdrant-landing/content/documentation/guides/migration.md @@ -5,7 +5,7 @@ weight: 180 # Migration -Migrating data between vector databases, especially across regions, platforms, or deployment types, can be a hassle. That’s where the [Qdrant Migration Tool](https://github.com/qdrant/migration) comes in. The tool supports all your migration needs, including moving from a self-hosted instance to Qdrant Cloud and switching cloud providers. The tool also works with self-hosted OSS Qdrant. You can also use the tool to migrate data between Qdrant instances, which is especially useful when migrating from Qdrant OSS to Qdrant Cloud. +Migrating data between vector databases, especially across regions, platforms, or deployment types, can be a hassle. That’s where the [Qdrant Migration Tool](https://github.com/qdrant/migration) comes in. It supports a wide range of migration needs, including transferring data between Qdrant instances and migrating from other vector database providers to Qdrant. You can run the migration tool 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.