diff --git a/qdrant-landing/content/documentation/database-tutorials/migration.md b/qdrant-landing/content/documentation/database-tutorials/migration.md
index 60b4e61ef..d3b467d99 100644
--- a/qdrant-landing/content/documentation/database-tutorials/migration.md
+++ b/qdrant-landing/content/documentation/database-tutorials/migration.md
@@ -41,16 +41,19 @@ Here is an example of how to perform a Qdrant to Qdrant migration:
 
 ```bash  
 docker run --rm -it \
-    -e SOURCE_API_KEY='your-source-key' \
-    -e TARGET_API_KEY='your-target-key' \
     registry.cloud.qdrant.io/library/qdrant-migration qdrant \
-    --source-url 'https://source-instance.cloud.qdrant.io' \
-    --source-collection 'benchmark' \
-    --target-url 'https://target-instance.cloud.qdrant.io' \
-    --target-collection 'benchmark'
-
+    --source.url 'https://source-instance.cloud.qdrant.io:6334' \
+    --target.api-key 'qdrant-source-key' \
+    --source.collection 'benchmark' \
+    --target.url 'https://target-instance.cloud.qdrant.io:6334' \
+    --target.api-key 'qdrant-target-key' \
+    --target.collection 'benchmark'
 ```
 
+<aside role="alert">
+    Note: The migration CLI uses the Qdrant GRPC API, this means you must always configure the GRPC port for Qdrant URLs with the Migration CLI (default: 6334).
+</aside>
+
 ## Example: Migrate from Pinecone to Qdrant
 
 Let’s now walk through an example of migrating from Pinecone to Qdrant. Assuming your Pinecone index looks like this: