Add support for migrating qdrant collections

README.md

@@ -101,7 +101,7 @@ To migrate from [Pinecone serverless](https://www.pinecone.io/blog/serverless/)
 
 From the Supabase instance we need the connection parameters. Retrive them [here](https://supabase.com/dashboard/project/_/settings/database)
 
-![supabsae connection parameters](/assets/supabase_connection_params.png)
+![supabase connection parameters](/assets/supabase_connection_params.png)
 
 And substitute those values into a valid Postgres connection string
 ```
@@ -120,7 +120,7 @@ The CLI provies a progress bar to monitor the migration.
 
 On completion, you can view a copy of the Pinecone index data in Supabase Postgres at `vec2pg.<pinecone index name>`
 
-![view results](/assets/view_results.png)
+![view results](/assets/pinecone_view_results.png)
 
 From there you can transform and manipulate the data in Postgres using SQL.
 
@@ -145,6 +145,48 @@ vec2pg qdrant migrate --help
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 ```
 
+To migrate from Qdrant collection to Postgres you'll need to log in at https://cloud.qdrant.io/ and collect your:  
+
+- Qdrant API Key
+
+![Qdrant api key](/assets/qdrant_api_key.png)
+
+- Qdrant URL and collection name
+
+![Qdrant cluster url](/assets/qdrant_nav_dashboard.png)
+
+The URL is the "Cluster URL". To find the collection name, select "Open Dashboard".
+
+![Qdrant collection name](/assets/qdrant_collection_name.png)
+
+- A Supabase instance
+
+From the Supabase instance we need the connection parameters. Retrive them [here](https://supabase.com/dashboard/project/_/settings/database)
+
+![supabase connection parameters](/assets/supabase_connection_params.png)
+
+And substitute those values into a valid Postgres connection string
+```
+postgresql://<User>:<Password>@<Host>:<Port>/postgres
+```
+e.g.
+```
+postgresql://postgres.ahqsutirwnsocaaorimo:<Password>@aws-0-us-east-1.pooler.supabase.com:6543/postgres
+```
+
+Then we can call `vec2pg qdrant migrate` passing our values. You can supply all parameters directly to the CLI, but its a good idea to pass the Qdrant API Key (QDRANT_API_KEY) and Supabase connection string (POSTGRES_CONNECTION_STRING) as environment variables to avoid logging credentials to your shell's history.
+
+![sample output](/assets/qdrant_to_supabase_output.png)
+
+The CLI provies a progress bar to monitor the migration.
+
+On completion, you can view a copy of the Pinecone index data in Supabase Postgres at `vec2pg.<qdrant collection name>`
+
+![view results](/assets/qdrant_view_results.png)
+
+From there you can transform and manipulate the data in Postgres using SQL.
+
+
 
 # Requisites
 - Python >= 3.8