Migrate from Valkey to KiviDB
Valkey is the open-source fork of Redis 7.2.4. It speaks the Redis protocol, and so does KiviDB, so applications move without code changes. How you move the…
Valkey is the open-source fork of Redis 7.2.4. It speaks the Redis protocol, and so does KiviDB, so applications move without code changes. How you move the data depends on the Valkey version:
| Valkey | Snapshot format | Into KiviDB |
|---|---|---|
| 7.2, 8.0, 8.1 | Redis RDB (REDIS0011) | Every method: replication, RDB file, RedisShake, RIOT, MIGRATE |
| 9.0, 9.1 | Valkey's own RDB (VALKEY080) | An RDB file fetched with valkey-cli --rdb, which Valkey sends in Redis's format; or RedisShake sync_reader. Replication, dump.rdb from disk and DUMP-based tools don't work |
Valkey 9 writes its snapshots in RDB version 80 with a VALKEY header, and
KiviDB 1.2.0 reads only Redis's format. Two things get around it: Valkey 9 still
sends a Redis-format (REDIS0011) snapshot to a client that fetches one with
valkey-cli --rdb, and RedisShake reads version 80 and rewrites each key in
Redis's format.
This guide covers standalone Valkey and Valkey cluster mode, into a KiviDB server you run yourself or into KiviDB Cloud. For a managed Valkey service (ElastiCache, Memorystore, Aiven, DigitalOcean), start from that provider's guide in Migrate to KiviDB.