The 6R Strategy: Choosing the Right Path for Every Application

Why “lift and shift everything” is one of the most expensive mistakes enterprises make — and how to decide what really belongs where

The Myth of Lift and Shift

The conference room at Company-A was packed. The CTO, Infrastructure Director, CISO, and CFO sat across from the strategy team, surrounded by whiteboards covered in application diagrams and dependency maps.

I presented our analysis: of Company-A’s 287 applications, only 38% could be simply “lifted and shifted” to the cloud. The remaining 62% required more sophisticated strategies — some needed significant refactoring, others should be retired entirely, and a few were so critical they couldn’t be moved at all.

“This isn’t what we expected. We budgeted for a straightforward migration, not a complete application transformation.”

The Solutions Architect had seen this reaction countless times. “The myth of ‘lift and shift everything’ is one of the most expensive mistakes enterprises make,” she explained. “Each application is unique — different business value, technical complexity, and strategic importance. A one-size-fits-all approach leads to overspending, underperformance, and missed opportunities.”

This was Company-A’s introduction to the 6R framework — the strategic approach that would determine the fate of each application and define their cloud transformation success.

Before Strategy: Defining Success

Before assigning a migration path to a single application, the team needed to answer fundamental questions:

• What are your business drivers? Cost reduction or innovation enablement? Speed to market or stability?
• What are your constraints? Budget ceilings, timeline pressures, skills availability, regulatory mandates?
• What are your risk tolerances? Downtime tolerance, vendor lock-in comfort, capacity for change?

This illustrates a fundamental shift in approach: don’t start with solutions — start with purpose. The best technical solution that doesn’t fit your business reality is still the wrong one.

The 6Rs in Enterprise Context

Retire: The Liberation Strategy

Retirement offered the fastest path to cost reduction and complexity elimination. Company-A identified redundant systems, legacy applications with minimal usage, unofficial or business-managed tools that have been replaced by standard enterprise systems, and end-of-life systems that no longer deliver business value.

By systematically retiring such workloads, organizations can eliminate unnecessary licensing, infrastructure overhead, and operational effort, while simplifying the overall technology landscape and reducing risk exposure.

Retain: The Strategic Hold

Some applications couldn’t or shouldn’t be migrated — mainframe applications with massive refactoring costs, recently purchased software with long-term contracts, highly regulated systems requiring extensive re-certification, or applications with hardware dependencies.

Rehost: The Speed Strategy

Lift-and-shift provided the fastest migration path for stable applications with well-understood dependencies, time-sensitive migrations, and systems requiring minimal downtime.

Relocate: The Virtualization Bridge

A hybrid approach for applications tightly integrated with virtualization-specific features, disaster recovery systems, and development environments with existing toolchain dependencies.

Replatform: The Optimization Path

Minor optimization provided cloud benefits without major architectural changes, often involving database and platform modernization.

Refactor: The Transformation Strategy

Complete re-architecting for cloud-native capabilities, reserved for applications with the highest business value: revenue-generating applications requiring scalability, customer-facing systems needing global performance, and applications requiring modern capabilities like AI/ML and real-time analytics.

The Decision Framework

Determining the right strategy for each application required balancing multiple competing factors.

Business Criticality Matrix

Applications were evaluated across two dimensions — revenue impact (direct revenue generation, customer experience, competitive differentiation) and operational importance (business process dependency, compliance requirements, integration complexity). 

Technical Complexity Assessment

Migration strategy was driven by architecture (monolithic vs. modular), technology stack (modern vs. legacy), data complexity (volume, compliance requirements), and integration dependencies (number, type, real-time vs. batch).

Compliance and Regulatory Constraints

Regulatory requirements imposed strict constraints: data residency (GDPR), audit and control needs (SOX), industry regulations (FDA), and vendor certifications tied to specific infrastructure.

Skills and Resource Availability

Feasibility was influenced by internal cloud expertise, project and change management maturity, business stakeholder engagement, and existing vendor partnerships.

The Result: 287 Applications, 6 Strategies

After weeks of analysis, every application had a clear migration path. The breakdown reflected the complexity that the discovery phase had revealed — and validated why a one-size-fits-all approach would have failed.

The 6R strategy presentation marked a pivotal moment. The comprehensive analysis revealed that Company-A’s migration would be far more complex than initially anticipated — but also far more valuable.

However, as the applause died down, the CFO raised her hand:

“The numbers look compelling, but I’m still concerned about the risks. What happens if something goes wrong? How do we justify the investment?”

The strategy was sound. But the business case still needed to be proven.

What’s Next

In our next post — “The Business Case: TCO, Validation, and Stakeholder Alignment” — we’ll explore:

• How to build a comprehensive Total Cost of Ownership model that captures hidden costs
• AWS validation processes that ensure migration strategies are realistic and achievable
• Tailoring the business case for different stakeholders — from CFO to security team
• The financial trajectory from investment to ROI

Remember: You’re Not Alone

Every enterprise leader we meet feels the weight of legacy complexity. The difference between those who transform and those who don’t isn’t resources — it’s partnership, clarity, and courage.