
A cloud migration strategy describes how much an application changes as it moves to the cloud. There are four strategies, rehost, replatform, refactor and rebuild, and they are easiest to remember in order of how much they change the application, from no significant changes at all to a complete reconstruction. For the Cloud Digital Leader exam, choosing a strategy comes down to what an organization is willing to change and what it wants from the move.
A rehosted migration, often called "lift and shift," moves applications into the cloud as they are. There are no significant changes to the code or the architecture. Only the underlying infrastructure moves to the cloud provider, while the application itself stays intact.
Rehosting is the most direct option when the goal is speed and minimal disruption rather than optimization or redesign. It gets workloads running in Google Cloud quickly, without the complexity of reworking code or redesigning systems, and the workloads still benefit from being hosted in Google Cloud.
A replatformed migration makes some modifications to the application or its runtime so that it fits the cloud environment better. It goes a step beyond rehosting, because the application or its runtime is adjusted rather than moved exactly as it is.
A refactored migration alters the application code to take advantage of cloud-native features. The code itself changes, and those changes are what let the application use capabilities that the cloud provides.
A rebuilt migration reconstructs the application from the ground up as fully cloud native. It is the furthest of the four from a simple move, and it is the most resource-intensive option.
Because the strategies are ordered by how much they change, the amount of change an organization is prepared to make narrows the choice. Rehosting is the only one of the four that leaves code and architecture as they are. Every strategy after it involves some change, from adjustments to the application or runtime up to a full rebuild.
The trade-off runs in the other direction as well. Rehosting favors speed and minimal disruption, but it does not optimize or redesign the application. The further a migration moves toward refactoring and rebuilding, the more it takes advantage of cloud-native features and the more effort it takes, with rebuilding at the resource-intensive end. We would read each Cloud Digital Leader scenario for what the organization values more, a fast and low-disruption move or an application reworked to be cloud native, and match the strategy to that.
Our Cloud Digital Leader practice exams cover the four migration strategies alongside cloud deployment models and Google Kubernetes Engine, with detailed explanations that drill these distinctions.