Migration guide

Migrating from Redis to Valkey: what changes and how to switch

Move Redis open source or ElastiCache to Valkey, run in our cloud, your cloud account or your data center, with replication keeping both servers live.

  • Operated by AceMQ
  • 160+ customers
The migration in phases

Redis to Valkey migration is effectively an upgrade from Redis OSS 7.2 and earlier, because Valkey is compatible with those versions: attach Valkey as a replica with REPLICAOF, wait for the link to sync, then switch clients. Data files from Redis Community Edition 7.4 and later are not compatible with Valkey and need another method.

What the licence change means for the move

Redis moved from a BSD licence to source-available licences in 2024 and added AGPLv3 with Redis 8 in 2025 (InfoQ, May 2025). Valkey is the BSD-licensed fork of Redis 7.2. Moving is a choice about licence policy, and the effort depends on the Redis version you run today.

Illustrative: each phase is planned and rehearsed with your team before traffic moves.

The licence history, and when to stay on Redis, are set out in Redis vs Valkey. This guide covers only how to move.

Which migration method fits

Replication is the method that keeps both servers live. The Valkey docs also describe a snapshot copy, which is the simplest but needs a shutdown, and a cluster procedure that adds Valkey nodes as replicas of the Redis primaries.

MethodWhat it doesBoth sides liveSource
Replication with REPLICAOFValkey is set as a replica of the Redis server. When the link is up and synced, applications connect to Valkey, Redis is shut down and replication is stopped with REPLICAOF NO ONE.YesValkey docs
Cluster migrationValkey nodes join the Redis Cluster as replicas, one Valkey replica per primary is promoted, and the Redis nodes are removed.YesValkey docs
Physical migration (RDB copy)A fresh snapshot is copied to Valkey, which loads it at start. The Valkey docs list the shutdown time and a data loss risk on heavily written instances.NoValkey docs
Migrating specific keysOnly chosen keys move, for partial moves.Depends on the key setValkey docs
ElastiCache in-place upgradeOn ElastiCache, a cluster can be upgraded from Redis OSS to Valkey by modifying it. The endpoint DNS name stays, and the cluster stays readable throughout with a few seconds of write failover.AWS docs

Sources: Valkey and AWS documentation, linked in each row; checked 30 Oct 2026.

How the methods were chosen: the first four come from the Valkey project's own migration guide, and the ElastiCache row from AWS. If the only concern is the licence and the cache already lives on ElastiCache, the in-place upgrade is the lowest-effort route.

Check these before you start

The Redis version decides everything. Valkey reads data files from Redis OSS 7.2 and earlier, and not from Redis Community Edition 7.4 and later.

Redis sourceValkey targetWhat the Valkey docs say
OSS 2.x to 7.2.xCompatible protocol, configuration and RDB and AOF formats. Moving is effectively an upgrade.
Community Edition 7.4 and laterNot applicableData files are not compatible with Valkey. Another method is needed, and it is not covered by the Valkey guide.

Source: Valkey docs; checked 30 Oct 2026.

Clients.
Valkey speaks RESP2 and RESP3, and existing Redis client libraries connect without code changes. The INFO output reports redis_version 7.2.4 for compatibility, so use valkey_version to tell the servers apart (Valkey docs).
Scripts and modules.
Lua scripts that use the redis namespace keep working, and modules written against the RedisModule API work in Valkey (Valkey docs). Features added to Redis after 7.2 are checked one by one.
ElastiCache as the source.
ElastiCache lists replicaof, sync and several other commands as unavailable for Redis OSS clusters (AWS docs). The documented way to get data out is a backup export to an Amazon S3 bucket in the same Region (AWS docs), which is a point-in-time copy, not a live link.
Caches versus stores.
A pure cache can often start empty and warm up, and a data store needs the data carried across. That choice is made in the design.

Sources: Valkey and AWS documentation, linked above; checked 30 Oct 2026.

The migration in phases

Valkey is built and attached as a replica while Redis keeps serving the application. Clients only move once the link reports synced and the key counts match.

  1. Review

    Redis version, persistence settings, clients, scripts, modules, memory and the key count from INFO KEYSPACE.

  2. Build Valkey

    Version, memory, replicas and configuration come from the design, and the node count and topology match the Redis setup.

  3. Replicate

    Valkey is attached to Redis as a replica and INFO REPLICATION is checked until the master link is up.

  4. Verify

    Key counts and sample reads are compared, and the applications are tested against Valkey.

  5. Cut over

    Writes are quiesced for the final sync, clients are pointed at Valkey, replication is stopped with REPLICAOF NO ONE, and Redis is kept as the fallback until Valkey has run normally.

The timeline and runbook for Redis to Valkey migrations are written in the design step, from your data volume, traffic and change windows, and you approve them before the cutover is scheduled.

Cutover and rollback

The Valkey docs warn that data can be lost if writes are active on Redis while it shuts down and syncs with the replica. So the cutover pauses writes for the final sync and keeps Redis untouched until Valkey has run normally.

  1. Replication is synced and the key counts match.
  2. Writes to Redis pause, and the final changes reach Valkey.
  3. Clients connect to Valkey, and REPLICAOF NO ONE promotes it.
  4. Redis is shut down only after Valkey has served normal traffic. Until then it is the fallback.

Source: the Valkey migration guide (Valkey docs); checked 30 Oct 2026.

How OSStend runs the move

We run the migration and own the cutover, with both sides live until you switch. Zero downtime is the plan.

OSStend designs, moves and runs Valkey around the workload, in our cloud, your cloud account or your data center, through managed Redis and Valkey. Teams comparing vendor pricing can read the Redis Enterprise and Redis Cloud alternatives page. The engine choice is covered in Redis vs Valkey, and the migration hub lists the other moves.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue

AceMQ names a customer only with that customer's written permission, so most of this record stays anonymous. Ask for a similar workload in the 45-minute review.

When this move fits, and when it does not

The move fits when the licence, the hosting place or the configuration limits are the reason to change. It does not when the cache already runs well on ElastiCache and the licence is the only concern.

Contact us if

  • A policy against source-available or AGPL software rules out the current Redis version.
  • You need full configuration, or a place the managed service does not run.
  • You run Redis OSS 7.2 or earlier, where the move is effectively an upgrade.
Talk to an engineer

Not a fit if

  • The cache runs on ElastiCache and only the licence is a concern: the in-place upgrade to Valkey is a smaller step.
  • You use Redis features added after 7.2 that Valkey does not have.
  • You want to run the move yourselves: the Valkey methods above work without OSStend.

Questions about moving to Valkey

Is Valkey a drop-in replacement for Redis?

For Redis OSS 7.2 and earlier, the Valkey docs describe it as compatible in protocol, configuration and data files. Data files from Redis Community Edition 7.4 and later are not compatible (Valkey docs, checked 30 Oct 2026).

Can Redis be migrated to Valkey without downtime?

With replication, both servers stay live until clients move. The Valkey docs note that writes arriving on Redis during the final shutdown can be lost, so writes are paused for that moment (Valkey docs, checked 30 Oct 2026).

Do client libraries need changes?

The Valkey docs say existing Redis client libraries can connect to Valkey without code changes, because it supports RESP2 and RESP3 (Valkey docs, checked 30 Oct 2026).

Talk to an engineer

Plan your move to Valkey with an engineer

45 minutes with an engineer: the current setup is reviewed against the documented method and the cutover is sketched. No ticket queue.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.