Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Lift And Shift
Cyber Security

Lift And Shift

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Lift and shift is a migration approach that moves an application into the cloud with minimal redesign. It can accelerate migration, but it often preserves the original architecture’s inefficiencies. In cloud environments, that can lead to oversizing, redundant services, and higher recurring costs than a cloud-native redesign would create.

What Lift And Shift Means in Cloud Migration

Lift and shift is the fastest path to move an existing workload into cloud infrastructure without redesigning its core architecture. That makes it useful when speed matters, but it also means the application usually keeps the assumptions, scaling pattern, and operational shape it had on-premises.

The practical trade-off is that the cloud becomes a new hosting layer rather than a redesign opportunity. Teams can gain faster relocation and simpler project sequencing, but they may also inherit tightly coupled components, fixed capacity assumptions, and deployment patterns that were never designed for elastic consumption.

Why Lift And Shift Often Preserves Inefficiency

Because little is changed during migration, lift and shift often carries forward the same resource profile that existed before the move. In cloud environments, that can mean oversized instances, idle capacity, duplicated supporting services, and a bill structure that reflects legacy design choices instead of cloud-native optimisation.

This is why the method is sometimes described as a relocation strategy rather than a modernisation strategy. If the original application was built for static infrastructure, its inefficiencies do not disappear when it is moved, they are simply running in a different environment with a different cost model.

Where Lift And Shift Fits in Migration Strategy

Lift and shift is best understood as one point on a migration spectrum. It is often chosen when organisations need to exit a data centre, reduce migration risk, or move a workload quickly before deciding whether deeper refactoring is justified later.

That makes it a legitimate transitional approach, especially for large portfolios with mixed technical debt. The important distinction is that successful relocation does not automatically equal long-term optimisation, and a migrated workload may still need later redesign, rightsizing, or decommissioning of unnecessary dependencies.

For teams planning cloud transitions, a migration-first mindset is often the reason the approach is adopted, while a cost- and architecture-aware mindset determines whether it remains a temporary step or becomes a long-term operating model.

Operational Signals That Lift And Shift Needs Review

After migration, the strongest clues that a workload was simply lifted and shifted are unchanged utilisation patterns, consistently low resource efficiency, and recurring spend that does not align with user demand. Those signals usually indicate that the application is still sized and structured for its old environment.

At that point, the real question is not whether the move succeeded, but whether the workload is now paying cloud prices for a legacy architecture. That is where inventory, usage telemetry, and application dependency analysis become important for deciding whether to modernise, retire, or keep the workload as-is.

Risk and Threat Considerations

Lift and shift is not inherently insecure, but it can extend the life of brittle architectures, expose unnecessary services to the cloud perimeter, and preserve weak assumptions about segmentation, monitoring, and recovery. The main risk is that speed hides architectural debt instead of removing it.

Failure mechanism: A workload is migrated with the same privilege boundaries, network paths, and operational dependencies it had before, so old inefficiencies and trust assumptions remain in place while the environment around them changes.

Impact: The organisation can end up with higher recurring cost, larger attack surface, and slower remediation of structural weaknesses because the migration is treated as complete when the underlying design still needs work.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0ID.AM-01 — Physical devices and systems within the organization are inventoriedLift and shift depends on knowing what workloads and dependencies are being moved.
GV.RM-01 — Risk management strategy is established, agreed to, and continuously reviewed and updatedLift and shift is a risk tradeoff between speed, cost, and later remediation.
PR.DS-10 — Confidentiality, integrity, and availability of data-at-rest are protectedCloud migration can preserve data handling patterns that need validation after relocation.
Recommendation — Inventory the migrated application and its dependencies before and after relocation. Define when lift and shift is acceptable and when redesign is required. Verify that migrated data protection controls still match the new hosting environment.
CIS Controls v8CIS-12 — Network Infrastructure ManagementLegacy network assumptions often persist during lift and shift and need revalidation in cloud.
Recommendation — Review network segmentation and exposure after the migration.
NIST SP 800-53 Rev 5CM-2 — Baseline ConfigurationLift and shift keeps the existing configuration baseline, including inefficiencies and drift.
Recommendation — Re-baseline the application after migration instead of assuming the old configuration remains suitable.

Practitioner Guidance

Why practitioners should care: Lift and shift should be treated as a migration decision, not a final optimisation decision. If the workload remains business-critical, owners should know whether the move was intended to buy time, reduce risk, or serve as the first phase of a broader cloud transformation.

Common misunderstanding: A successful relocation can create the false impression that the application is cloud-ready. In practice, the cloud may only be hosting the same inefficiencies more expensively, so the post-migration review should focus on rightsizing, dependency pruning, and whether a later redesign is warranted.

Practitioner takeaway: Use lift and shift when speed is the goal, but do not confuse speed with optimisation; the migrated workload still needs a deliberate decision about modernisation.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org