Migrate from Aiven to KiviDB

This guide moves a dataset from Aiven for Valkey to KiviDB, either a server you run yourself or KiviDB Cloud. It covers getting the data out, loading it, switching over with little downtime, and the changes your application needs.

Aiven for Caching, Aiven's Redis service, reached end of life on 31 March 2025, and Aiven upgraded the remaining services to Aiven for Valkey. If you still think of your service as "Aiven for Redis", it is now a Valkey service, and this guide applies to it.

Aiven makes moving out harder than moving in:

• Backups cannot be downloaded. Aiven keeps them encrypted in its own storage and says so in its documentation.
• The replication and snapshot commands are disabled. REPLICAOF, SLAVEOF, SAVE, BGSAVE, CONFIG, ACL, MIGRATE, MONITOR and a few others answer ERR unknown command.
• Aiven's migration tools only move data into Aiven. The console's migration wizard and the migration settings in avn copy from an outside server into an Aiven service, not the other way.

That leaves a copy tool that reads keys over normal commands (SCAN, DUMP, TYPE, PTTL) as the dependable way out. It works on every plan, and it can keep following changes until you switch.