CUJ3 — Migration Journey Map

Redis UXR

{{ pageTitle }}

?

{{ overallScore }} / 5 {{ overallRating }}

{{ themeLabel }}

What migrates (layer) i

          ●required
          ◐optional
          ○n/a
          
          insight
          ticket
        

Path

What type of migration is it?

{{ s.short }}

{{ s.name }} i

All paths

cross-cutting

{{ sup.label }} {{ sup.count }}

{{ chip.glyph }}{{ chip.label }}

{{ chip.more }}

{{ chip.tkCount }}

{{ familyA }}

{{ familyB }}

{{ row.id }} i

{{ row.name }}

{{ row.sub }}

{{ sup.count }}

{{ chip.glyph }}{{ chip.label }}

{{ chip.more }}

{{ chip.tkCount }}

Loading research data…

{{ overallScore }} / 5

{{ overallRating }}

Weighted CEOA score across 4 stages

› {{ st.id }} {{ st.name }} weight {{ st.weight }}

{{ st.insightCount }} insights {{ st.status }} {{ st.composite }}

{{ d.label }}{{ d.value }}

{{ ins.dim }}

{{ ins.impact }}

{{ ins.pathLabel }}

{{ ins.insight }}

{{ ins.source }}

{{ ly.id }}|{{ ly.label }}

{{ fc.name }}

Sort

{{ insightCount }} insights

{{ ins.dim }}

{{ ins.impact }}

{{ ins.pathLabel }}

{{ ins.stageLabel }}

{{ ins.insight }}

{{ ins.source }}

{{ ly.id }}|{{ ly.label }}

{{ st.id }}{{ st.name }}

{{ st.status }}

{{ st.goal }}

{{ st.currentState }}

Layers

{{ l.id }}{{ l.name }}

{{ l.description }}

Data modes

{{ m.id }}{{ m.name }}

{{ m.description }}

Typical: {{ m.typicalCase }}

{{ tooltip.eyebrow }}

{{ tooltip.title }}

{{ note }}

Insights & tickets

{{ it.text }}

{{ it.sub }}

+ {{ tooltip.more }} more · click to open

{{ selected.crumb }}

{{ selected.title }}

Insights · {{ selected.insightCount }}

{{ i.dim }} {{ i.impact }}

{{ i.insight }}

{{ i.source }}

Support tickets · {{ selected.ticketCount }}

{{ t.customer }} #{{ t.id }} ↗

{{ t.summary }}

No tagged items for this combination.

Demo data All insights, scores, tickets and customer names on this site are fabricated and unrelated to the real project's data.

Walkthrough

{{ counter }}

Source

Your app + data

ElastiCache · OSS · Heroku · another tier

endpoint + data

4 steps

Target

Redis Cloud

correctly sized, validated, cut over

What is a migration?

Migration means moving an application onto Redis Cloud — reconnecting its endpoint, and moving data when it's worth keeping — with minimal downtime and validation before cut-over. It is never a single data-transfer event: every migration is a path (where you come from), walked through four steps, changing one or more layers along the way. This map lays all of that out in one grid.

Path A — into Redis Cloudfrom outside

A1 Redis-compatible A2 KV / cache A5 vector DB …

Path B — within Redis Clouda move inside

B1 Free↔Ess B2 Ess↔Pro B6 region …

Two types of migration

Every migration is one of two paths:

Path A — migrating into Redis from an external source (ElastiCache, OSS Redis, Heroku, a vector DB, a message queue…).

Path B — moving within Redis Cloud (tiers, storage, region, billing…).

Each path breaks into concrete subtypes — the rows down the left (A1, A2… / B1, B2…), each answering "what type of migration is it?"

Step 1Decide & Plan

Step 2Prepare

Step 3Execute

Step 4Validate & Cut Over

The four steps

Read the grid left to right — every migration moves through the same four steps:

Step 1 · Decide & Plan — what to move, the method, the tool.

Step 2 · Prepare — size and provision the target, check compatibility.

Step 3 · Execute — transfer the data.

Step 4 · Validate & Cut Over — confirm integrity, then repoint the app.

Hover the ⓘ on any step in the grid for what it involves.

●Data

●Infrastructure

◐Control plane

● required◐ optional○ n/a

The layers — what migrates

A migration can change three things independently:

Data — the keys and values.

Infrastructure — tier, storage, region, cluster.

Control plane — account, subscription, billing.

Each cell shows whether a layer is required (●), optional (◐), or not relevant (○) for that path at that step.

●Data

OrientationHigh

The provisioning layer labels the tier choice as "Pro" without naming or surfacing that this selection commits operators to a dedicated VPC architecture, obscuring the infrastructure shift from the subscription decision itself.

Acme Corp — sync failed, no error detail#158545 ↗

Insights & support tickets

The marks inside each cell are the research. Filled dots are tagged insights; rings are support tickets. Hover a cell for a quick summary, or click it to open a panel with every insight (dimension + impact) and linked Zendesk ticket behind that path, step, and layer.

Demo data

insights · scores · tickets · customers

every value on every screen is generated

All data here is fabricated

This is a portfolio demonstration of a research method, not a set of findings. Every insight, score, support ticket and customer name shown is synthetic and bears no relation to the real project, its data, or any real product. Nothing here should be read as evidence about anything.