In Part 1 of this series, we explored how the 6 Rs became the framework that defined the cloud migration era. By providing organizations with structured modernization pathways, the framework helped simplify decision-making and accelerate cloud adoption at scale.

While the 6 Rs remain relevant, the modernization landscape surrounding them has changed significantly. Organizations are now facing a new set of challenges driven by operational complexity, growing technical debt, and the need to support AI-enabled environments. As modernization priorities evolve, it is worth examining whether a framework designed for cloud migration is enough to address the demands of the AI era.

Early Cloud Migration and Modernization

Early cloud transformation efforts were largely focused on infrastructure efficiency and scalability. Organizations wanted to reduce capital expenditures (CapEx), improve uptime, and accelerate deployment capabilities. Today, modernization priorities are becoming far more operational. Organizations are under increasing pressure to improve interoperability, reduce workflow friction, support real-time decision-making, and prepare environments for AI-enabled operations. 

At the same time, many are discovering that modern infrastructure alone does not automatically resolve deeply embedded complexity across the enterprise. Applications may now run in the cloud, but disconnected workflows, siloed data, and fragmented user experiences often remain unchanged underneath. As modernization priorities evolve, organizations are beginning to ask broader questions: How adaptable are our systems? Where does operational friction still exist? Which architectures are limiting scalability? Can our current environments support AI-driven workflows? Are we modernizing technology or modernizing operations? 

These are different questions than the ones organizations were asking when the 6 Rs first emerged and they may require modernization strategies to evolve alongside them.

The Problem With the Original 6 Rs

The original framework was built around migration strategy. It helped organizations decide what should happen to an application during modernization. Should it be lifted and shifted? Should it be refactored? Should it be retired entirely? Those are still important decisions but they focus primarily on the application itself rather than the operational environment surrounding it. 

The rehost strategy may move an application into the cloud faster; the replatform strategy may improve scalability while the refactor strategy may modernize portions of the codebase. However, none of those inherently solve fragmented workflows, disconnected user experiences, inaccessible data or operational bottlenecks that continue to slow the organization down.

In many cases, organizations modernize infrastructure while preserving the exact operational complexity that created the problem in the first place. In other words, the technology changes while the operational model does not. This becomes a much bigger problem in the AI era since AI depends on accessible data, interoperable systems, and workflows that can support automation and continuous adaptation. Legacy architectures were not designed for that environment. In fact, many were built around siloed applications and disconnected workflows optimized for a different operational era entirely. As a result, organizations often discover that simply modernizing infrastructure does not automatically make them AI-ready. It just gives them newer infrastructure supporting the same underlying complexity.

Continue the Conversation

The modernization strategies that helped organizations move to the cloud are now evolving alongside new operational demands, AI adoption, and increasing architectural complexity.

In Part 3 of this series, we explore why modernization may require more than the traditional 6 Rs and why organizations are beginning to think about a 7th R: Reimagine. Stay tuned for the next blog!