Understanding Lift and Shift Migration
Lift and shift, formally called rehosting, is the fastest and lowest-risk of the migration strategies in the 6 R’s framework. It moves an application from its source environment, usually an on-premises hypervisor like VMware vSphere or Hyper-V, into a cloud provider’s compute service, such as Amazon EC2 or Azure Virtual Machines, without redesigning the application. The operating system, middleware, and application code remain effectively unchanged; only the underlying infrastructure moves.
How It Works
Lift and shift relies on physical-to-virtual (P2V) or virtual-to-virtual (V2V) conversion tooling that replicates the source disk image and system state into the target cloud. Common tools include AWS Application Migration Service (MGN), which performs continuous block-level replication and allows a low-downtime cutover, Azure Migrate with its replication appliance, and VMware HCX for VMware-to-VMware moves between on-prem and VMware Cloud on AWS. The process typically involves installing a lightweight replication agent on the source server, letting it sync continuously, then triggering a test launch in an isolated network to validate the migrated instance boots and functions correctly before the final production cutover.
Example Scenario
A retailer runs a legacy inventory management application on an on-premises Windows Server VM with SQL Server installed locally. Facing a data center closure deadline, the team uses AWS MGN to replicate the VM into an equivalent-sized EC2 instance, keeping the same OS version, application binaries, and database engine untouched. Networking is adjusted so the instance sits in a new VPC subnet, DNS is repointed, and the cutover happens over a weekend maintenance window with a rollback plan to fail back to the source VM if issues arise.
Why Teams Choose Lift and Shift
Speed is the primary driver: rehosting requires no application redesign, so it can meet hard deadlines like data center exits or lease expirations. It also carries lower project risk because the application’s behavior doesn’t change, reducing the testing burden compared to refactoring. It’s a common first step for teams with limited cloud experience, letting them build operational familiarity with the target platform before attempting deeper modernization.
Trade-offs and Limitations
- It does not take advantage of cloud-native capabilities like auto scaling, managed databases, or serverless compute, so operational overhead often stays similar to on-premises.
- Costs may not improve, and can sometimes increase, if the instance isn’t right-sized or if licensing costs carry over unfavorably.
- Legacy security configurations, outdated OS patch levels, and existing technical debt move into the cloud unchanged rather than being resolved.
- Without a planned second phase, organizations can get “stuck” running expensive, unoptimized infrastructure indefinitely.
Best Practices
- Right-size the target compute instance during migration rather than matching source specs exactly; on-prem servers are frequently over-provisioned.
- Apply resource tags at launch to enable cost tracking and ownership attribution from day one.
- Plan lift and shift explicitly as phase one of a broader roadmap, with a defined follow-up phase for replatforming or refactoring high-value workloads.
- Patch and harden the OS image during migration rather than carrying forward known vulnerabilities.
- Validate performance and cost post-migration against a 30 to 60 day baseline before declaring the move complete.
Frequently Asked Questions
What is Lift and Shift Migration?
Lift and shift, also called rehosting, is a cloud migration approach that moves an application to the cloud with little or no change to its architecture or code, typically VM to VM.
How does Lift and Shift Migration work?
Lift and Shift Migration works by combining the components described in the sections above. The main page walks through the architecture, the typical use cases, and the trade-offs to weigh before adopting it.
Why does Lift and Shift Migration matter?
Teams adopt Lift and Shift Migration to ship faster, run more reliably, and reduce the cognitive load on engineers. The benefits, limits, and adjacent tools are covered in the body above.
When should you use Lift and Shift Migration?
Use Lift and Shift Migration when the problems it solves match what your team is hitting today. The page above outlines the signals that mean you should adopt it now, and the cases where a simpler approach is fine.
