The One Migration approach to migrating the IT portfolio

Azure and Azure Migrate are both well known for hosting Microsoft technologies. But you might not be aware of Azure's ability to support migrations beyond Windows and SQL Server. The One Migration scenarios captured in the Migrate methodology demonstrate the same set of consistent guidelines and processes for migrating both Microsoft and third-party technologies.

Migration scenarios

The following diagram and table outline a number of scenarios that follow the same iterative Migrate methodology for migration and modernization.

Diagram of the Cloud Adoption Framework migration model showing the V M, Apps, Data, and Hybrid resources you will need.

Virtual machines Virtual machines Linux servers Virtual desktops
Applications ASP.NET Java PHP
Data SQL Server Open-source databases Analytics
Hybrid Azure Stack VMware
Technology platforms SAP (Classic & HANA) Kubernetes Mainframes
Additional scenarios Secure workloads Multitenant environments NetApp

Migrate methodology

In each of the preceding migration scenarios, the same basic process will guide your efforts as you move your existing workloads to the cloud, as shown here:

Diagram of the Cloud Adoption Framework migration model showing the Migration waves and the Migration effort.

In each scenario, you'll structure migration waves to guide the releases of multiple workloads. Establishing a cloud adoption plan and Azure landing zones through the plan and Ready methodologies helps to add structure to your migration waves.

During each iteration, follow the Migrate methodology to assess, deploy, and release workloads. To modify those processes to fit your organization's specific scenario, select any of the migration scenarios listed in the table.

Next steps

If you aren't migrating a specific scenario, start by following the four-step Cloud Adoption Framework migration process.