Overview of application migration examples for Azure
This section of the Cloud Adoption Framework provides examples of several common migration scenarios and demonstrates how you can migrate on-premises infrastructure to Microsoft Azure.
Azure provides access to a comprehensive set of cloud services. As developers and IT professionals, you can use these services to build, deploy, and manage applications on a range of tools and frameworks through a global network of datacenters. As your business faces challenges associated with the digital shift, the Azure platform helps you to determine how to:
- Optimize resources and operations.
- Engage with your customers and employees.
- Transform your products.
The cloud provides advantages for speed and flexibility, minimized costs, performance, and reliability. However, many organizations might need to continue to run on-premises datacenters. In response to cloud adoption barriers, Azure provides a hybrid cloud strategy that builds bridges between your on-premises datacenters and the Azure public cloud. An example is using Azure cloud resources like Azure Backup to protect on-premises resources or Azure analytics to gain insights into on-premises workloads.
As part of the hybrid cloud strategy, Azure provides growing solutions for migrating on-premises applications and workloads to the cloud. With simple steps, you can comprehensively assess your on-premises resources to determine how they'll run in the Azure platform. With a deep assessment in hand, you can confidently migrate resources to Azure. When resources are up and running in Azure, you can optimize them to retain and improve access, flexibility, security, and reliability.
Strategies for migration to the cloud fall into four broad patterns: rehost, refactor, rearchitect, or rebuild. The strategy you adopt depends on your business drivers and migration goals. You might adopt multiple patterns. For example, you could choose to rehost noncritical applications while rearchitecting applications that are more complex and business-critical. Let's look at these patterns.
|Pattern||Definition||When to use|
|Rehost||Often referred to as a lift-and-shift migration, this option doesn't require code changes. You can use it to migrate your existing applications to Azure quickly. Each application is migrated as is to reap the benefits of the cloud without the risk and cost associated with code changes.||- When you need to move applications quickly to the cloud
- When you want to move an application without modifying it
- When your applications are designed to take advantage of Azure infrastructure as a service (IaaS) scalability after migration.
- When applications are important to your business, but you don't need to immediately change application capabilities.
|Refactor||Often referred to as a "repackaging," refactoring requires minimal changes to applications so that they can connect to Azure platform as a service (PaaS) and use cloud offerings. For example, you could migrate existing applications to Azure App Service or Azure Kubernetes Service (AKS). Or, you could refactor relational and nonrelational databases into options such as Azure SQL Managed Instance, Azure Database for MySQL, Azure Database for PostgreSQL, and Azure Cosmos DB.||- If your application can easily be repackaged to work in Azure
- If you want to apply innovative DevOps practices provided by Azure, or if you're thinking about DevOps using a container strategy for workloads
- For refactoring, you need to think about the portability of your existing code base and available development skills.
|Rearchitect||Rearchitecting for migration focuses on modifying and extending application functionality and the code base to optimize the application architecture for cloud scalability. For example, you could break down a monolithic application into a group of microservices that work together and scale easily. You could also rearchitect relational and nonrelational databases to a fully managed database solution, such as SQL Managed Instance, Azure Database for MySQL, Azure Database for PostgreSQL, and Azure Cosmos DB.||- When your applications need major revisions to incorporate new capabilities or to work effectively on a cloud platform
- When you want to use existing application investments, meet scalability requirements, apply innovative DevOps practices, and minimize use of virtual machines
|Rebuild||Rebuild takes things a step further by rebuilding an application from scratch using Azure cloud technologies. For example, you could build greenfield applications with cloud-native technologies like Azure Functions, AI, SQL Managed Instance, and Azure Cosmos DB.||- When you want rapid development, and existing applications have limited functionality and lifespan
- When you're ready to expedite business innovation (including DevOps practices provided by Azure), build new applications using cloud-native technologies, and take advantage of advancements in AI, blockchain, and IoT.
Migration example articles
This section provides examples of several common migration scenarios. Each example includes background information and detailed deployment scenarios. These scenarios illustrate how to set up a migration infrastructure and assess the suitability of on-premises resources for migration. More articles will be added to this section over time.
This series focuses on each migration scenario, which is driven by slightly different business goals to determine the migration strategy. For each deployment scenario, we provide information about:
- Business drivers and goals.
- A proposed architecture.
- Steps to perform the migration.
- Recommendations for cleanup and next steps after migration is finished.
|Assess on-premises resources for migration to Azure||This article in the Plan methodology discusses how to run an assessment of an on-premises application running on VMware. In the article, an example organization assesses application VMs by using Azure Migrate and the application SQL Server database by using Data Migration Assistant.|
|Deploy Azure infrastructure||This article shows how an organization can prepare its on-premises infrastructure and its Azure infrastructure for migration. The infrastructure example established in this article is referenced in the other samples provided in this section.|
Windows Server workloads
|Rehost an application on Azure VMs||This article provides an example of migrating on-premises application VMs to Azure VMs using Azure Migrate.|
SQL Server workloads
|Migrate SQL Server databases to Azure||This article demonstrates how the fictional company Contoso assessed, planned, and migrated its various on-premises SQL Server databases to Azure.|
|Rehost an application on an Azure VM and SQL Managed Instance||This article provides an example of a lift-and-shift migration to Azure for an on-premises application. This process involves migrating the application front-end VM by using Azure Migrate and the application database to SQL Managed Instance by using Azure Database Migration Service.|
|Rehost an application on Azure VMs using SQL Server Always On availability groups||This example shows how to migrate an application and data by using Azure-hosted SQL Server VMs. It uses Azure Migrate to migrate the application VMs and Database Migration Service to migrate the application database to a SQL Server cluster that's protected by an Always On availability group.|
Linux and open-source databases
|Migrate open-source databases to Azure||This article demonstrates how the fictional company Contoso assessed, planned, and migrated its various on-premises open-source databases to Azure.|
|Migrate MySQL to Azure||This article demonstrates how the fictional company Contoso planned and migrated its on-premises MySQL open-source database platform to Azure.|
|Migrate PostgreSQL to Azure||This article demonstrates how the fictional company Contoso planned and migrated its on-premises PostgreSQL open-source database platform to Azure.|
|Migrate MariaDB to Azure||This article demonstrates how the fictional company Contoso planned and migrated its on-premises MariaDB open-source database platform to Azure.|
|Rehost a Linux application on Azure VMs and Azure Database for MySQL||This article provides an example of migrating a Linux-hosted application to Azure VMs by using Azure Migrate. The application database is migrated to Azure Database for MySQL by using Database Migration Service.|
|Rehost a Linux application on Azure VMs||This example shows how to complete a lift-and-shift migration of a Linux-based application to Azure VMs by using Azure Migrate.|
|Migrate dev/test environments to Azure IaaS||This article demonstrates how Contoso rehosts its dev/test environment for two applications running on VMware VMs by migrating to Azure VMs.|
|Migrate to Azure DevTest Labs||This article discusses how Contoso moves its dev/test workloads to Azure by using DevTest Labs.|
ASP.NET and PHP web apps
|Refactor a Windows application by using App Service and SQL Database||This example shows how to migrate an on-premises Windows-based application to an Azure web app. It also shows how to migrate the application database to an Azure SQL Database server instance by using Database Migration Service.|
|Refactor a Windows application by using App Service and SQL Managed Instance||This example shows how to migrate an on-premises Windows-based application to an Azure web app. It also shows how to migrate the application database to SQL Managed Instance by using Database Migration Service.|
|Refactor a Linux application to multiple regions by using App Service, Azure Traffic Manager, and Azure Database for MySQL||This example shows how to migrate an on-premises Linux-based application to an Azure web app on multiple Azure regions by using Traffic Manager to integrate with GitHub for continuous delivery. The application database is migrated to an Azure Database for MySQL instance.|
|Rebuild an application in Azure||This article provides an example of rebuilding an on-premises application by using a range of Azure capabilities and managed services. These capabilities and services include App Service, AKS, Azure Functions, Azure Cognitive Services, and Azure Cosmos DB.|
|Refactor Team Foundation Server to Azure DevOps Services||This article shows an example migration of an on-premises Team Foundation Server deployment to Azure DevOps Services in Azure.|
|SAP migration guide||Get practical guidance to move your on-premises SAP workloads to the cloud.|
|Migrate SAP applications to Azure||White paper and roadmap for your SAP journey to the cloud.|
|SAP on Azure migration||Learn how to migrate your SAP estate to Azure.|
|Move on-premises VMware infrastructure to Azure||This article provides an example of moving on-premises VMware VMs to Azure by using Azure VMware Solution.|
|Azure NetApp Files||Enterprise file storage powered by NetApp. Run Linux and Windows file workloads in Azure.|
|Oracle on Azure||Run your Oracle databases and enterprise applications in Azure and Oracle Cloud Infrastructure.|
|Cray in Azure||High-performance computing with Cray in Azure. A dedicated supercomputer on your virtual network.|
|Move on-premises Remote Desktop Services to Azure Virtual Desktop||This article shows how to migrate on-premises Remote Desktop Services to Azure Virtual Desktop.|
|Scale a migration to Azure||This article shows how an example organization prepares to scale to a full migration to Azure.|
The example articles provided in this section use two demo applications: SmartHotel360 and osTicket.
SmartHotel360: This test application was developed by Microsoft to use when you work with Azure. It's provided under an open-source license, and you can download it from GitHub. It's an ASP.NET application connected to a SQL Server database. In the scenarios discussed in these articles, the current version of this application is deployed to two VMware VMs running Windows Server 2008 R2 and SQL Server 2008 R2. These application VMs are hosted on-premises and managed by vCenter Server.
osTicket: This open-source service desk ticketing application runs on Linux. You can download it from GitHub. In the scenarios discussed in these articles, the current version of this application is deployed on-premises to two VMware VMs running Ubuntu 16.04 LTS using Apache 2, PHP 7.0, and MySQL 5.7.