Migrate from DigitalOcean to KiviDB

This guide moves a dataset from a DigitalOcean Valkey cluster 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.

DigitalOcean's Redis product, Managed Caching, was discontinued on 30 June 2025, and DigitalOcean converted the remaining clusters to Valkey clusters. If you still think of yours as "Managed Redis" or "Managed Caching", it is now a Valkey cluster, and this guide applies to it.

DigitalOcean gives you no file to take away:

• There are no backups. Valkey clusters do not support backups or restoring from them; forking a cluster is the only copy DigitalOcean makes, and the fork is another DigitalOcean cluster.
• The replication and snapshot commands are disabled. REPLICAOF, SLAVEOF, SAVE, BGSAVE, CONFIG, ACL, MIGRATE, MONITOR and a few others are not allowed.
• DigitalOcean's migration feature only moves data in. Set Up Migration in the control panel copies from an outside server into a DigitalOcean cluster, not the other way.

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