Once you have completed your discovery and assessment, it’s time to prepare for the next step: cloud migration.
This is where, after you have landed on your migration goals and gathered all requirements and constraints, you can choose the best method of migration. In previous datasheets, we overviewed the migration evolution model that showed workloads progressing through phases of lift and shift, cloud optimization, and eventually app modernization.
During the migration effort, you’ll determine the approach that best meets your requirements. This is best addressed per application. Essentially, in this phase, you’re physically moving your workloads and applications (including their data) to the cloud and planning to retire the on-premises versions. Every organization will have a different approach and mixture of using rehosting, refactoring, rearchitecting, or rebuilding for their applications.
This datasheet focuses on the rehost approach, moving applications running on traditional servers and virtual machines to Azure IaaS. In many cases, organizations will start with lift and shift to drive rapid migration and early cost savings. Lift and shift makes no changes to your app or workload framework or architecture; it simply involves exchanging hardware and OS management with the cloud environment.