Skip to main content

Migrate to Aiven for Dragonfly®

Migrate to Aiven for Dragonfly® from Aiven for Caching or Aiven for Valkey™, or from an external Redis®* or Valkey service.

Choose your migration path​

Which migration guide you follow depends on where your source database runs.

  • Choose the Aiven for Caching or Aiven for Valkey path when Aiven already manages your source service. You only select the project and service to migrate from.
  • Choose the external Redis or Valkey path when your source runs outside Aiven, for example on your own infrastructure or with another cloud provider. You enter its connection details yourself, including a VPC peering connection if the source isn't reachable over the public internet.

Things to know before you migrate​

  • Check API compatibility first. Dragonfly closely mirrors the Redis API, but some commands differ, especially in newer Redis and Valkey versions. Review the Dragonfly API compatibility documentation before you migrate.
  • Migration runs as replication either way. Once you start a migration, Aiven streams data from the source in real time and the target Dragonfly service stays read-only. When the initial sync completes, you choose whether to keep replicating from the source or stop it and switch over.

Related pages