Cloud migration

Azure tenant-to-tenant migration strategy

Move a made-up game house from an old cloud tenant to a new cloud castle by matching each Azure resource to the right migration method.

AdvancedStateful dataStateless computeSecretsIdentityNetworkCutover validation

Interactive migration control room

Move the game house to a new cloud castle

Drag each resource from the old tenant into the migration method that fits it. The kid version explains the moving-house idea; the Azure label underneath shows the real platform concept.

Failing is part of the lesson.

Try the risky plan, validate it, then fix the failed checks until the cutover turns green.

Old tenant

Things to move

Selected: Treasure chestsSaved game items live here. Copy them carefully and count them after the move.

Copy data

Move the treasure carefully

Replicate stateful data early, validate counts, then cut over.

Drop or tap selected resource here

Redeploy from blueprint

Build a fresh game machine

Redeploy stateless compute from source-controlled configuration.

Drop or tap selected resource here

Recreate secret

Make new locked keys

Recreate secrets in Key Vault with controlled access and validation.

Drop or tap selected resource here

Rebuild identity

Issue new player badges

Rebuild app registrations, groups, permissions, and trust relationships.

Drop or tap selected resource here

Reconnect network

Connect roads and signposts

Recreate private endpoints, DNS links, peering, and route validation.

Drop or tap selected resource here

New tenant

Cutover checks

0/5Checks passing

Can the app start?Validate to test this step.

Can the app read secrets?Validate to test this step.

Can the app find the database?Validate to test this step.

Does login work?Validate to test this step.

Is the data count matching?Validate to test this step.

5 resource cards still need a migration method.

Visual Firestore move

Move one learner session between deve and prod

loading

Firestore database

loading

empty

demoInventorySessions/session

No session document.Seed this side or migrate into it.

deve to prodLoading database view...

Firestore database

loading

empty

demoInventorySessions/session

No session document.Seed this side or migrate into it.

Why it matters

Cloud migrations fail when teams treat all resources the same. Data, compute, secrets, identity, and networks each need a different migration path and a validation check.

Field notes

Stateful data is like treasure: copy it carefully and verify counts before cutover.
Stateless compute is like a game machine: rebuild it from source-controlled blueprints.
Secrets are locked keys: recreate them safely in the new tenant and validate access.
Identity is a badge system: rebuild trust, app registrations, groups, and permissions.
Network is roads and signposts: private endpoints and DNS decide whether apps can find data.