Products
Migration endpoint coverage
Endpoint recognition, executable movement and a completed migration qualification are distinct. Use the runtime capability/preflight result for the exact source-to-target direction and selected image. The release compatibility reference records the build/profile boundary.
| Family | Executable scope | Operational boundary |
|---|---|---|
| Redis / Valkey | Same-family key mover and Redis-compatible live routing; guided workflow | Command/session support and evidence, exact backend versions/ACL/TLS/topology and TTL validation |
| PostgreSQL | Same-kind table movement and selected heterogeneous routes | Transaction/schema-aware planning; ordinary PostgreSQL movement does not select a provider-neutral vector adapter |
| MongoDB | Same-kind document movement and selected heterogeneous routes | Collection/index/session/provider checks; Atlas vector semantics are separate |
| PostgreSQL / MongoDB / MySQL | Selected heterogeneous mappings | Registry direction, complete schema/request mapping and preflight gates |
| Qdrant | Same-provider offline historical-copy preview | Quiesced source, Replace conflict rule, supported collection schema; no live replay/traffic cutover |
| Elasticsearch / OpenSearch | Offline search/document-copy preview | Quiesced source, supported index schema and identity mapping; no live capture/replay |
| Other vector providers | Catalog recognition only | Does not authorize provider-neutral migration workers |
| Kafka-compatible | Homogeneous non-transactional movement | Classic groups and fixed topic/partition inventory; transactional, compacted-topic and multi-producer-gateway HA limits |
The guided /migration-workflows/redis API is Redis-specific. Other executable families use the lower-level migration lifecycle and their own adapter contracts; there are no documented guided /postgres or /mongo aliases.
For heterogeneous routes begin with LogAndReplay planning, validate schema and request mappings, and require explicit replay/cutover evidence. For offline previews, stop writes before scanning and maintain quiescence through completion; an operator attestation does not install a provider write fence.
Use Redis, PostgreSQL, and MongoDB endpoint guides for configuration. Use migration operations, validation runs and recovery runbooks for execution decisions.