Load into KiviDB: migrate from KeyDB to KiviDB

Load into KiviDB. Migrate to KiviDB: Move from Redis, Valkey, ElastiCache, Redis Cloud, Aiven, Aerospike, Hazelcast and more: getting the data out, loading it

Self-hosted KiviDB

As for Redis:

# An RDB file in the data directory, read at startup when there is no dump.kdb
cp dump.rdb /var/lib/kividb/dump.rdb
kividb --dir /var/lib/kividb

# Or named
kividb --dir /var/lib/kividb --preload-file rdb:/backups/dump.rdb

Don't copy keydb.conf across: KiviDB's config file is read strictly, and KeyDB's directives (server-threads, active-replica, storage-provider and others) stop the server. Start from an empty config and carry over maxmemory, maxmemory-policy, the password or ACL file, and appendonly.

KiviDB Cloud

Create the database first (Lua on if the application runs scripts, or if you copy with RedisShake sync_reader), then either:

upload KeyDB's dump.rdb under Snapshots → Import a snapshot and create the database from it, or restore it into an existing one; or
run RedisShake sync_reader or RIOT --struct with the database as the target, as in the Redis guide: your-name.cloud.kividb.io:6380, user kividbapp, TLS on.

A KiviDB Cloud database cannot replicate from KeyDB.