Lift-and-Shift Migration Vocabulary

Key vocabulary

Term	Meaning
lift-and-shift	Moving a workload to the cloud with no code or architecture changes; synonymous with rehost.
migrate as-is	Phrase used to describe moving a workload exactly as it exists today, without modification.
minimal changes	Small adjustments (e.g. OS version, storage type) made during rehost that do not alter the application architecture.
cut-over	The moment production traffic is switched from the old environment to the new cloud environment.
cut-over plan	A step-by-step runbook that coordinates the exact sequence of actions during the switch to cloud production.
cut-over window	The scheduled time period (often overnight or at weekend) during which the cut-over takes place.
rollback plan	A documented procedure to revert to the on-premises environment if the cut-over fails.

1. The architect says: "We chose rehost for this application because we needed to be in the cloud within six weeks and could not afford a redesign." Which phrase below best paraphrases the migration approach?

"We refactored the application for cloud-native performance." "We migrated the application as-is — lift-and-shift — to meet the deadline." "We replaced the application with a managed SaaS product."

2. The team explains: "We made minimal changes — we swapped the local file storage for object storage — but left everything else identical." What does "minimal changes" mean in a rehost context?

The application was completely rewritten to use cloud-native services. Small, targeted adjustments were made without altering the overall application architecture. The application was retired and replaced with a SaaS product.

3. The project manager says: "We need to schedule the cut-over window for Saturday night between midnight and 4 a.m." What is a cut-over window?

The period of elevated monitoring after migration completes. The scheduled time slot during which production traffic is switched to the new cloud environment. The time allowed for the team to roll back if the migration fails.

4. The team has a detailed runbook listing every step: stop replication, update DNS, verify health checks, confirm go-live. What document is this?

A rollback plan A cut-over plan A discovery report

5. The lead engineer says: "If anything goes wrong during the cut-over, we revert DNS, re-enable the on-premises database, and declare the rollback." What document details these steps?

A cut-over plan A migration wave plan A rollback plan

Key vocabulary

Exercise complete!