further migration section updates

qdrant-landing/content/documentation/data-synchronization/_index.md

@@ -0,0 +1,21 @@
+---
+title: Data Synchronization
+weight: 400
+partition: ecosystem
+---
+
+# Keeping Your Data in Sync with Qdrant
+
+After migrating to Qdrant, maintaining consistency between Qdrant and your primary data store is an ongoing operational concern. As records are created, updated, or deleted in your source of truth, those changes need to be reflected in Qdrant to keep search results accurate and fresh.
+
+The guides in this section cover database-specific synchronization patterns for keeping Qdrant aligned with your existing infrastructure.
+
+## Synchronization Strategies
+
+How you sync depends on your source system and write volume:
+
+- **Event-driven sync** — listen for change events (CDC, triggers, or message queues) and upsert or delete points in Qdrant in real time.
+- **Batch sync** — periodically re-index records that have changed since the last run, using a timestamp or version field to identify updates.
+- **Dual-write** — write to both systems simultaneously in application code, with a background reconciliation job to catch divergence.
+
+Each approach involves trade-offs between latency, complexity, and consistency guarantees. The guides below cover patterns for specific databases.

qdrant-landing/content/documentation/data-synchronization/with-postgres.md

@@ -1,6 +1,6 @@
 ---
-title: Keeping Postgres in Sync
-weight: 400
+title: With Postgres
+weight: 5
 partition: ecosystem
 ---