From 707cb22d2da21a6b48ac3254fd791947dde4e4c3 Mon Sep 17 00:00:00 2001 From: kanungle Date: Tue, 24 Mar 2026 15:29:01 -0700 Subject: [PATCH] Migration Guidance title change --- .../content/documentation/migration-guidance/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/migration-guidance/_index.md b/qdrant-landing/content/documentation/migration-guidance/_index.md index e8750bcff..c53b124c4 100644 --- a/qdrant-landing/content/documentation/migration-guidance/_index.md +++ b/qdrant-landing/content/documentation/migration-guidance/_index.md @@ -7,7 +7,7 @@ aliases: - /documentation/migration-verification/ --- -# Migration Verification Guide +# Migration Guidance Switching databases is often necessary to improve the performance and costs of large software systems. As the size of data continues to grow, navigating this migration can be tricky. While a migration might appear to have been successful, several silent errors may be occurring. Some examples include: data loss, metadata drift, and search quality regressions. These problems can hide behind a successful import. To help mitigate these issues, this guide gives you a structured framework to verify that your migration worked correctly.