By Fredrik Karlsson | 30. März 2026 | 12 min read | 2957 words
Lift and shift migration relocates applications from on-premises data centers to cloud infrastructure without rewriting application code, delivering the fastest path to cloud adoption for most enterprise workloads. Also known as rehosting, this approach replicates your existing compute, storage, and networking in an infrastructure-as-a-service (IaaS) environment so teams can exit physical data centers, convert capital expenses to operational spend, and establish a cloud operating foundation in weeks rather than months.
For organizations facing lease expirations, compliance deadlines, or aging hardware, rehosting removes the immediate pressure while preserving the option to modernize applications later. According to Gartner's 2025 cloud forecast, worldwide public cloud spending surpassed $723 billion, with IaaS remaining the fastest-growing segment. Direct rehosting continues to be the most common first step for enterprises beginning their cloud journey.
This guide explains what lift and shift means, when it delivers the best return, how it compares to replatforming and refactoring, and how to execute a successful migration from discovery through post-move optimization.
Key Takeaways
- Rehosting moves applications as-is to cloud IaaS with minimal code changes, delivering value in weeks.
- Best suited for data center exits, disaster recovery, stable workloads, and vendor-locked applications.
- Converting CapEx to OpEx improves financial flexibility, but rightsizing within 30 days prevents long-term cost creep.
- Dependency discovery, phased rollouts, and governance guardrails control risk from day one.
- Treat rehosting as the opening move in a portfolio modernization strategy that includes replatforming and refactoring where the business case supports it.
What Is Lift and Shift Migration?
Lift and shift migration means moving an application and its data from physical servers to a cloud IaaS provider with minimal or no code modifications. The existing architecture, including compute instances, storage volumes, networking configurations, and middleware, is replicated in the cloud environment so day-to-day operations continue without disruption.
The name describes the two-phase action: lift the workload out of the physical data center, then shift it onto cloud infrastructure. Industry analysts use the term "rehosting" interchangeably because the application is simply hosted on different infrastructure without changing its internal design or dependencies.
Key characteristics of a lift and shift approach:
- One-to-one infrastructure mapping -- compute instances, storage volumes, and network configurations mirror the on-premises setup.
- Short migration timelines -- typically weeks rather than months because no application redesign is required.
- Limited initial use of cloud-native features -- autoscaling, managed databases, and serverless functions are adopted in later optimization phases.
- VM and managed storage compatibility -- works with VMware, Hyper-V, KVM, and other hypervisor environments.
Rehosting works best for stable applications with urgent migration deadlines, workloads that cannot be refactored due to vendor licensing restrictions, and situations where teams must vacate a data center quickly. It is less suitable for applications with deep performance inefficiencies or workloads that depend on cloud-native services to deliver their core value.
Benefits and Trade-Offs of Rehosting
The primary advantage of a rehosting migration is speed: organizations can move workloads with minimal downtime while keeping business services running throughout the transition.
Speed and minimal disruption
Because the application architecture stays the same, teams complete the migration without retraining users or redesigning integrations. The end-user experience remains consistent, which reduces support calls and preserves business continuity during the transition window.
CapEx to OpEx conversion
Moving to the cloud converts upfront hardware purchases into pay-as-you-use service fees. Elastic pricing and on-demand scaling align infrastructure costs with actual demand, improving predictability for finance teams and freeing capital for strategic initiatives. Organizations typically see immediate savings from decommissioning hardware and terminating data center leases.
Infrastructure and security uplift
Running on modern cloud hardware often delivers better compute performance, higher availability, and stronger baseline security controls. Role-based access, multifactor authentication, encryption at rest, and centralized policy management come built into major cloud platforms without additional capital purchases.
Limitations to plan for
If applications remain unoptimized after the move, expected savings may not materialize. Static rehosting without rightsizing can drive roughly 15% higher cloud costs over time due to overprovisioned compute and idle resources. Licensing constraints and compliance requirements may also limit savings without proactive audits. Teams should plan optimization phases immediately after stabilization to capture the full value of cloud economics.
| Benefit |
What It Delivers |
Risk and Mitigation |
| Fast cutover |
Minimal downtime, consistent user experience |
Insufficient testing -- conduct dependency mapping and dry runs |
| Financial flexibility |
Shift to operational spend, elastic pricing |
Cost creep -- set KPIs and monitor consumption continuously |
| Performance uplift |
Modern hardware, autoscaling options |
Overprovisioning -- apply rightsizing within 30 days post-move |
| Security controls |
RBAC, MFA, centralized policies from day one |
Misconfiguration -- enforce guardrails and run security audits |
When to Choose Lift and Shift
Data center exits, disaster recovery, regulated workloads, and M&A transitions are the four scenarios where a direct cloud move delivers the most value with the least risk.
Data center exits and consolidation
When lease expirations or cost pressures force a rapid exit, rehosting compresses timelines dramatically. Dow Jones migrated the majority of its workloads to AWS in two months, saving $40,000 in immediate costs and enabling News Corp to consolidate from 56 data centers down to six. GE Oil & Gas moved 750 TB of data and planned the migration of 500 applications, reporting approximately 52% cost savings after standardization.
Disaster recovery and business continuity
Rehosting creates high-fidelity replicas of production systems in the cloud, providing fast failover capability without application refactoring. This approach leverages cloud provider redundancy across availability zones and regions to protect service levels and meet RPO/RTO targets at a fraction of the cost of maintaining a secondary physical data center.
Vendor-locked and regulated workloads
Off-the-shelf applications often cannot be modified without voiding vendor support agreements. Rehosting preserves these licensing and support relationships while gaining cloud infrastructure benefits. Regulated workloads in healthcare (HIPAA), finance (SOC 2, PCI DSS), and government (FedRAMP) can move to compliant cloud regions with documented shared responsibility models and audit trails.
M&A transitions and temporary relocations
Short-term cloud moves during mergers, acquisitions, or office relocations protect team productivity by maintaining uninterrupted access to systems while organizations plan longer-term modernization strategies.
Lift and Shift vs Replatforming vs Refactoring
Not every workload requires the same migration path; the right approach depends on business value, risk tolerance, timeline, and the application's long-term strategic importance.
Replatforming (lift, tinker, and shift)
Replatforming makes targeted changes to adopt cloud-managed features like autoscaling databases, container orchestration, or automated patching without a full application rewrite. This middle path requires more effort than a direct rehost but delivers faster developer productivity and improved operational resilience. It is the right fit when moderate effort can unlock meaningful cloud-native benefits.
Refactoring and rearchitecting
When long-term agility and unit economics matter most, teams break monolithic applications into microservices or adopt serverless computing. Refactoring demands the highest upfront investment -- often three to twelve months of development -- but can dramatically improve deployment velocity, observability, and per-transaction cost efficiency for high-change applications.
Choosing the right approach per workload
A portfolio strategy delivers the best results across a diverse application estate. Apply rehosting for stable systems that need to move fast, replatform where quick wins exist with moderate effort, refactor high-value applications that will benefit from cloud-native architectures, and replace commodity applications with SaaS equivalents. This balanced approach matches each workload to the strategy that delivers the best return on investment. For a deeper comparison of rehosting economics, see our cloud migration cost analysis.
| Approach |
Primary Benefit |
Best For |
Typical Timeline |
| Rehost (lift and shift) |
Fast execution, minimal code change |
Urgent deadlines, stable applications |
Weeks |
| Replatform (lift, tinker, shift) |
Managed features, autoscaling |
Moderate changes acceptable |
1-3 months |
| Refactor / rearchitect |
High agility, optimal unit economics |
Strategic, high-growth applications |
3-12 months |
| Replace with SaaS |
Rapid adoption, minimal ops burden |
Commodity apps with SaaS equivalents |
Days to weeks |
Step-by-Step Lift and Shift Migration Strategy
A successful rehosting project follows four phases: discovery, planning, execution, and optimization. Breaking large moves into short, verifiable stages reduces risk and lets teams demonstrate measurable value at each milestone.
Phase 1: Discovery and assessment
Build a complete inventory of applications, databases, middleware, and interdependencies. Capture performance baselines including CPU utilization, memory usage, storage IOPS, and network throughput. Use automated discovery tools like AWS Migration Hub, Azure Migrate, or Google Cloud Migrate to accelerate the process and reduce manual errors. Document licensing models for every application to identify potential cloud licensing cost differences early.
Phase 2: Workload prioritization and wave planning
Sequence workloads by complexity, interdependencies, resource patterns, and modernization potential. Start with low-risk, low-dependency applications to prove the operating model before tackling mission-critical systems. Define success criteria including acceptable downtime windows, performance thresholds, and cost targets for each wave. A well-structured risk assessment at this stage prevents surprises during execution.
Phase 3: Migration execution
Run time-boxed pilots for each wave using replication tools to minimize cutover windows. Test security controls, execute disaster recovery simulations, and verify functional parity against on-premises baselines before decommissioning legacy systems. Maintain rollback plans and runbooks to support operations teams throughout the process. For VMware environments, VMware HCX enables network extension and bulk VM migration with minimal IP address changes.
Phase 4: Post-migration optimization
After stabilization, apply rightsizing recommendations, enable autoscaling policies, and implement cloud cost management practices including reserved instances, savings plans, spot instances for non-critical workloads, and storage tiering. Establish observability dashboards to track performance, availability, and spend against pre-migration baselines. This phase is where organizations capture the long-term financial value of cloud migration.
| Phase |
Key Outcome |
Recommended Tools |
| Discovery |
Complete inventory and performance baselines |
AWS Migration Hub, Azure Migrate, Google Migrate |
| Planning |
Prioritized wave plan with success criteria |
Cloud adoption frameworks, risk matrices |
| Execution |
Validated migration with DR testing |
AWS Application Migration Service, VMware HCX |
| Optimization |
Rightsized resources and cost controls |
Cloud cost management platforms, observability tools |
Migration Tools and Platform Considerations
AWS, Azure, and Google Cloud each provide dedicated migration tooling, but platform selection should align with your existing technology stack, team expertise, and long-term architectural direction.
AWS Migration Hub and Application Migration Service
AWS offers the Migration Acceleration Program (MAP) with funding incentives and tools like AWS Application Migration Service for automated server replication. These tools support continuous block-level replication with minimal performance impact, enabling cutover windows measured in minutes rather than hours.
Azure Migrate and Google Cloud Migrate
Azure Migrate provides end-to-end assessment, server migration, database migration, and web app migration in a unified portal. Google Cloud Migrate offers workload discovery, fit assessment, and automated VM migration with Migrate to Virtual Machines. Both platforms support agentless discovery and incremental replication for large-scale moves.
VMware HCX for enterprise VM environments
For organizations running VMware at scale, VMware HCX extends on-premises networks into the cloud, enabling unified management, bulk replication, and recovery for thousands of VMs while preserving IP addressing and routing. Success requires ESXi parity, vSphere API-compatible tools, and experienced operations staff to coordinate replication windows.
Network, storage, and security architecture
Design IP addressing, routing, firewall rules, and network segmentation to preserve application behavior post-migration. Plan storage for throughput and IOPS requirements, choosing replication strategies that meet RPO/RTO targets. Implement federated identity management and enforce least-privilege access controls from the start. All external integrations should use encrypted transport with continuous compliance monitoring.
Compliance and governance guardrails
Map regulatory controls to cloud provider capabilities before migration begins. For industries like healthcare (HIPAA), finance (SOC 2, PCI DSS), and government (FedRAMP), document the shared responsibility model clearly so both your team and the cloud provider understand their obligations. Collect evidence continuously during and after the move, and schedule compliance audits at each major milestone. Limit the scope of each migration wave to a tight minimum viable product and enable additional cloud services in controlled phases after stability is confirmed.
Costs, Risks, and Real-World Results
Rapid cloud moves often deliver clear short-term wins, but sustaining savings requires proactive financial governance and continuous optimization from the first week.
Short-term savings vs long-term cost creep
Rehosting reduces capital outlay immediately and can produce savings from decommissioning hardware and terminating data center leases. However, static cloud deployments without rightsizing often drive roughly 15% higher costs over time due to overprovisioned compute, idle storage, and underutilized reserved capacity. Setting cost baselines during discovery and enforcing optimization within 30 days of each wave prevents this drift.
Common repatriation drivers to avoid
Industry data identifies the most common reasons organizations move workloads back on-premises: technical provisioning issues (36%), performance degradation (29%), wrong provider selection (21%), and unexpected cost overruns (20%). Avoiding these outcomes requires thorough benchmarking, proof-of-concept testing, and architecture validation aligned to workload requirements before committing to large-scale moves.
Real-world case studies
- Dow Jones: Completed a two-month AWS migration, delivering $40,000 in immediate savings and enabling News Corp to consolidate from 56 data centers to six.
- GE Oil & Gas: Migrated 750 TB of data with plans for 500 applications, reporting approximately 52% cost savings after cloud standardization.
- Netflix: An urgent data center failure triggered an initial AWS migration that evolved into iterative cloud-native modernization for long-term resilience and global scale.
Financial governance recommendations
Enforce financial governance from day one. Implement anomaly detection for cost spikes, track unit economics per workload, establish chargeback models for business units, and benchmark cloud providers against actual workload performance requirements. For a detailed breakdown of cost optimization approaches, see our guide to cloud migration cost management.
Team Readiness and Partner Selection
Operational readiness depends as much on team capabilities and cultural alignment as on tooling and architecture decisions.
Assess your team's familiarity with cloud platforms, infrastructure-as-code tools like Terraform and CloudFormation, and monitoring platforms like CloudWatch, Azure Monitor, or Datadog. Plan training sprints before the first migration wave so operations staff can respond to incidents in the new environment without reverting to legacy workflows.
Consider partnering with a cloud migration consulting partner for the first wave to accelerate learning and establish operational patterns that your internal team can replicate for subsequent waves. Knowledge transfer should be an explicit deliverable in any consulting engagement, not an afterthought.
For organizations evaluating managed service providers, look for partners with documented migration methodology, cloud provider certifications across AWS, Azure, and GCP, and transparent pricing that aligns incentives with your optimization goals rather than cloud consumption.
Getting Started with Your Migration
A rehosting migration gives teams immediate operational breathing room while building the cloud competency needed for deeper modernization.
This approach is the fastest, least disruptive entry point to a modern cloud environment. It delivers time to stabilize services, reduce data center exit risk, and establish cloud operations capabilities while proven tools streamline execution across AWS, Azure, and GCP.
To sustain the gains, enforce governance from day one: set KPIs for cost, performance, and availability; apply rightsizing within 30 days; and maintain compliance baselines with continuous monitoring. Then adopt a portfolio strategy that matches each application to the migration approach -- whether rehosting, replatforming, or refactoring -- that delivers measurable business value over time.
Next step: Identify three to five candidate applications, define clear success criteria, and run a pilot migration. This approach shortens time to value, controls cost, and frees teams to innovate on higher-priority initiatives. Explore Opsio's cloud migration services to see how we help organizations execute successful lift and shift projects.
FAQ
What is lift and shift migration?
Lift and shift migration, also called rehosting, means moving applications and their data from on-premises servers into a cloud IaaS environment with minimal code changes. The existing architecture is preserved so operations continue uninterrupted while teams plan further cloud optimization and modernization.
When is lift and shift the right choice?
Rehosting works best when teams need a fast data center exit, face tight timelines that rule out application redesign, or must reduce on-premises infrastructure costs quickly. It is well suited for stable off-the-shelf applications, disaster recovery scenarios, and regulated workloads that cannot be modified without risking compliance or vendor support.
What are the main benefits of rehosting?
Organizations typically gain faster time to value, predictable OpEx pricing instead of CapEx hardware purchases, reduced maintenance burden, and access to cloud provider security and scaling features. These benefits free IT teams to focus on strategic initiatives rather than infrastructure management.
What are the risks of a lift and shift approach?
Rehosting can leave applications underusing cloud-native services like autoscaling and managed databases, which may cause higher long-term operating costs. Without post-migration rightsizing, cloud spend can exceed on-premises costs by roughly 15%. Teams should plan optimization phases immediately after the initial move to capture full cloud value.
How does rehosting compare to replatforming and refactoring?
Rehosting is the fastest and least disruptive option, moving workloads as-is. Replatforming makes moderate changes to adopt managed cloud services. Refactoring redesigns applications for cloud-native architectures with the highest effort but best long-term economics. Most organizations apply a portfolio approach, using different strategies for different workloads based on business value, risk, and timeline.
Which tools are best for lift and shift migrations?
Proven tools include AWS Application Migration Service for automated server replication, VMware HCX for hybrid extension and bulk VM transfers, Azure Migrate for assessment and migration, and Google Cloud Migrate for workload discovery and orchestration. The right choice depends on your existing infrastructure and cloud provider strategy.
How long does a lift and shift migration take?
Simple application moves can complete in weeks, while enterprise-wide data center exits typically require two to six months of planning, discovery, testing, and staged cutovers. Dow Jones demonstrated that even large-scale migrations can complete in approximately two months with proper planning and tooling.
How do you prevent cost overruns after rehosting?
Apply rightsizing within 30 days of each migration wave, enable autoscaling, use reserved capacity and spot instances where appropriate, and implement storage tiering. Set up anomaly detection for cost spikes, track unit economics per workload, and run regular cost reviews to align cloud spend with actual business value.
