The Move Before the MakeoverAt the start of the migration, three teams faced a daunting inventory: more than 200 services, all running on Company X’s on-premise infrastructure, all needing to reach the cloud.The goal was clear—reduce the cost of running those systems—but the path was not. Moving hundreds of services was already a major undertaking. Trying to redesign and optimize each one during the migration would make the project even slower and more complicated.So Company X made a deliberate choice: **lift and shift first, optimize later**.It was like moving to a new house. Instead of unpacking every box, reorganizing every drawer, and replacing every piece of furniture before leaving the old place, you move everything first. Once you are safely inside the new house, you decide what to rearrange, improve, or discard.Over eight months, the three teams migrated more than 200 services from on-premise infrastructure to the cloud. The strategy separated two difficult problems that could easily have become one overwhelming problem: changing where the services ran and improving how they ran.That was the turning point. The migration did not need to produce a perfectly optimized cloud environment on day one. Its first job was simply to complete the move.After the migration, Company X’s server costs were 40% lower.The larger lesson was not merely that cloud infrastructure could reduce costs. It was that sequencing mattered: by prioritizing movement before optimization, Company X turned a complex transformation into a manageable series of decisions.**When a change feels too large to execute perfectly, make the essential move first—and improve the destination once you arrive.**