Lift and Shift: IaaS App Migration in Record Time<\/h2>\nMigrate as-is:<\/strong><\/h3>\nApps are migrated unchanged to virtual machines (VMs) in Azure. The VMs effectively emulate on-prem hardware, providing a like-for-like migration.<\/p>\n
Fast migration:<\/strong><\/h3>\nSince apps don’t need refactoring or re-platforming, migration can happen much faster compared to modernizing apps.<\/p>\n
This is useful for organizations with tight timelines, such as if you need to get apps moved to the cloud in weeks or months.<\/p>\n
Leverage existing skills:<\/strong><\/h3>\nWith lift-and-shift, your developers can use the same tools and processes they are familiar with already.<\/p>\n
There is no need to learn new cloud development skills and practices to migrate apps.<\/p>\n
Avoid app downtime:<\/strong><\/h3>\nWith proper planning and the use of techniques like replication, apps can stay online and accessible to users during the migration process. This prevents business disruption.<\/p>\n
Flexible scale:<\/strong><\/h3>\nIn Azure, VMs can be scaled up or down to provide more or less resources to meet changing demand. You only pay for the VM capacity you need.<\/p>\n
Enhanced DR:<\/strong><\/h3>\nNative Azure features like Availability Zones and Region Pairs provide additional options for disaster recovery that are harder to achieve on-prem.<\/p>\n
Lift and shift is a good option when:<\/strong><\/p>\n\n- You have legacy apps that are too complex or risky to modernize. Lift and shift lets you migrate them as-is.<\/li>\n
- Your apps have many complex dependencies that would require significant unraveling and re-architecting to modernize.<\/li>\n
- You need to complete migrations quickly to meet pressing business timelines.<\/li>\n
- You want to migrate apps without disrupting them and causing downtime. Keeping apps online throughout migration is vital.<\/li>\n
- You want to get apps moved to the cloud rapidly to start realizing benefits, even if modernization comes later. Quick wins build confidence and momentum for further cloud adoption.<\/li>\n<\/ul>\n
However, there are some downsides to keep in mind with lift and shift:<\/p>\n
Increased cost:<\/strong><\/h3>\nIn most cases, running workloads on IaaS like VMs costs more over the long term compared to using managed platform services. You miss out on cost optimizations.<\/p>\n
Technical debt accrues:<\/h3>\n
Apps aren’t optimized for the cloud when migrated as-is. You incur more technical debt, making modernization harder later.<\/p>\n
Extra management overhead:<\/h3>\n
Apps running on IaaS still require the same management, monitoring, and maintenance as running them on-prem.<\/p>\n
The cloud doesn’t inherently reduce this hands-on workload.<\/p>\n
Scalability limits remain:<\/h3>\n
Apps are still constrained by their original architectures meant for on-prem hardware. They can’t take advantage of cloud scaling.<\/p>\n
Security gaps:<\/h3>\n
Traditional security models persist. Apps lack cloud-native controls and practices. There is an increased risk of breaches.<\/p>\n
Deployment delays continue:<\/h3>\n
Taking VMs offline to deploy app updates causes the same disruptions as on-prem. No automation gains.<\/p>\n
Finally, lift and shift gets apps to the cloud quickly, buying time to properly modernize later.<\/p>\n
However, most organizations shouldn’t view it as the end state for their migrated apps due to the drawbacks.<\/p>\n
Modernizing: Re-Architecting Apps for the Cloud<\/h2>\n
![\"Modernizing\"](\"https:\/\/www.aegissofttech.com\/insights\/wp-content\/uploads\/2024\/01\/Modernizing.jpg\" "\\"\\"")
<\/p>\n
For organizations able to invest more upfront, modernizing apps unlocks the full benefits of the cloud. Here are some key aspects of modernization:<\/p>\n
Cloud-native architecture:<\/h3>\n
![\"Cloud-native\"](\"https:\/\/www.aegissofttech.com\/insights\/wp-content\/uploads\/2024\/01\/Cloud-native.jpg\" "\\"\\"")
<\/p>\n
Apps are refactored and re-architected using cloud design patterns to maximize scalability, availability, performance, and other qualities. Apps are built for the cloud.<\/p>\n
Managed platform services:<\/h3>\n
Where possible, VMs are traded for managed platform services like App Service, Azure SQL, and PaaS options that remove overhead.<\/p>\n
DevOps automation:<\/h3>\n
Automated CI\/CD pipelines, infrastructure as code, and centralized logging among other practices are implemented for greater agility.<\/p>\n
Microservices:<\/h3>\n
Monolithic apps are broken down into independently deployable Microservices that scale better.<\/p>\n
Containerization:
\n![\"Containerization\"](\"https:\/\/www.aegissofttech.com\/insights\/wp-content\/uploads\/2024\/01\/Containerization.jpg\" "\\"\\"")
<\/h3>\n
Apps are packaged into containers using options like Docker to increase portability. Kubernetes is leveraged for container orchestration.<\/p>\n
Serverless:<\/h3>\n
Serverless computing like Azure Functions replaces VM-bound apps to optimize costs and scale.<\/p>\n
Data cloud migration:<\/h3>\n
On-prem databases are moved to fully managed, cloud-native storage services like Cosmos DB.<\/p>\n
New app features:<\/h3>\n
Parts of apps like UIs or reports can be completely rebuilt to add new capabilities. AI services are integrated to add intelligence.<\/p>\n
The benefits of lift-and-shift often include<\/p>\n
Lower long-term costs:<\/h3>\n
Apps avoid bloated, overprovisioned VMs and instead leverage autoscaling platform services that drive efficiency.<\/p>\n
Reduced overhead:<\/h3>\n
Managed platform services lower administrative and operations overhead compared to IaaS.<\/p>\n
Increased innovation:<\/h3>\n
New cloud-native features boost app functionality in ways not possible with on-prem apps. Competitive advantage grows.<\/p>\n
Improved scalability:<\/h3>\n
Cloud-native, Microservices-based apps scale out easily via autoscaling to meet spikes in demand.<\/p>\n
Faster updates:<\/h3>\n
With CI\/CD pipelines, updates can be deployed multiple times per day without downtime. Business agility increases.<\/p>\n
Enhanced security:<\/h3>\n
Modern apps are designed for cloud-native security practices like zero trust. Risk exposure is lowered.<\/p>\n
However, modernizing apps also requires<\/p>\n
Cloud architecture skills:<\/h3>\n
Your team will need training or hiring to build out expertise in cloud-based application design. This takes time.<\/p>\n
App rewrites:<\/h3>\n
In many cases, large parts of app code will need complete rewrites to become cloud-native. This demands significant developer effort.<\/p>\n
Longer timelines:<\/h3>\n
End-to-end modernization efforts typically take many months or even years to complete. Quick migrations are not realistic.
\nCosts of re-platforming:<\/p>\n
There are costs for data migration<\/a>, Cloud testing services<\/strong><\/a> versions of apps, and addressing integration gaps that lift-and-shift avoids.<\/p>\nFor these reasons, many organizations take an iterative, phased approach to modernizing apps over time rather than trying to transform them all at once. Quick wins help build momentum.<\/p>\n
Key Factors in Choosing a Migration Strategy<\/h2>\n
Organizations don’t have to pick just one migration strategy. Often a mix of lift-and-shift and modernizing works best.<\/p>\n
Consider these key factors when deciding on Azure Cloud Migration Solutions:<\/p>\n
Timeline Requirements<\/h3>\n
Need to migrate quickly?<\/p>\n
Lift-and-shift gets apps to Azure faster, minimizing changes. But modernizing may still be feasible for some newer apps built on cloud-friendly stacks.<\/p>\n
Have time for a longer modernization project?<\/p>\n
Modernizing unlocks the most cloud benefits but requires more upfront effort. With flexible timelines, you can realize the full benefits.<\/p>\n
Application Characteristics<\/h3>\n
Is the app monolithic or tightly coupled?<\/p>\n
These apps are harder to decompose into Microservices. Lift-and-shift minimizes risk for them.<\/p>\n
Is the app already cloud-architected or using Microservices?
\nIt’s a prime candidate for full modernization since cloud optimization is already part of its DNA.<\/p>\n
Does the app use legacy languages like COBOL?<\/p>\n
Lift-and-shift avoids risky, expensive rewrites. But newer Java or C# apps are modernization candidates.<\/p>\n
Is the app built on cloud-native stacks?<\/p>\n
Apps using containers, NoSQL databases, etc. can modernize faster for bigger gains.<\/p>\n
Business Goals<\/h3>\n
Is agility and innovation the priority?<\/p>\n
Modernizing apps unlocks new capabilities that support responding quickly to opportunities.<\/p>\n
Is reducing data center costs the main driver?<\/p>\n
Lift-and-shift cuts expenses much quicker, at least initially.<\/p>\n
Do you want a future-proof architecture?<\/p>\n
Modernizing results in apps aligned with long-term cloud principles.<\/p>\n
Are you migrating a legacy system of record?<\/p>\n
Lift-and-shift is the lowest risk for these foundational apps.<\/p>\n
Cost Considerations<\/h3>\n
Do you have the budget for a major migration effort?<\/p>\n
More budget allows more modernization upfront for long-term gains.<\/p>\n
Is minimizing migration costs critical?<\/p>\n
Lift-and-shift requires less upfront investment compared to modernizing.<\/p>\n
Can you invest in iterative re-platforming over time?<\/p>\n
Spreading modernization over the year smooths costs while increasing benefits.<\/p>\n
Internal Skills<\/h3>\n
Do you have strong cloud architecture skills already?<\/p>\n
Take advantage of this experience to modernize apps using best practices.<\/p>\n
Is your team new to the cloud?<\/p>\n
Lift-and-shift lets you migrate apps without deep cloud expertise.<\/p>\n
Are you willing to train and hire cloud talent?<\/p>\n
Funding skilling and staffing unlocks more modernization capabilities internally.<\/p>\n
Migration Tools<\/h3>\n
Microsoft provides various tools to assess on-prem environments and make recommendations on migrating apps to Azure:<\/p>\n
Azure Migrate:<\/h3>\n
Gives guidance on sizing Azure VMs and PaaS services as part of migration planning based on data collected from on-prem VMs and apps.<\/p>\n
Cloud Adoption Framework:<\/h3>\n
Provides proven methodologies, best practices, and tools for developing an effective cloud migration and modernization strategy.<\/p>\n
Azure App Assessment:<\/h3>\n
Analyzes and generates reports on web apps to determine readiness for migrating to Azure App Service or containers. Makes modernization recommendations.<\/p>\n
The key is to use the right tools for your environment to determine the best path – lift, shift, modernize, or blend.<\/p>\n
With a data-driven analysis of your apps and infrastructure, you can craft a migration approach that sets you up for the most cloud success.<\/p>\n
Hybrid Migration Strategies<\/h2>\n
![\"Hybrid\"](\"https:\/\/www.aegissofttech.com\/insights\/wp-content\/uploads\/2024\/01\/Hybrid.jpg\" "\\"\\"")
<\/p>\n
Many organizations find the best approach is a hybrid migration strategy combining lift-and-shift elements and modernizing based on app characteristics. Some key aspects of hybrid migration:<\/p>\n
Leverage both IaaS and PaaS<\/strong>: Lift-and-shift IaaS hosts legacy apps while new apps use PaaS for cloud-native build.<\/p>\n
Apps are migrated unchanged to virtual machines (VMs) in Azure. The VMs effectively emulate on-prem hardware, providing a like-for-like migration.<\/p>\n
Fast migration:<\/strong><\/h3>\nSince apps don’t need refactoring or re-platforming, migration can happen much faster compared to modernizing apps.<\/p>\n
This is useful for organizations with tight timelines, such as if you need to get apps moved to the cloud in weeks or months.<\/p>\n
Leverage existing skills:<\/strong><\/h3>\nWith lift-and-shift, your developers can use the same tools and processes they are familiar with already.<\/p>\n
There is no need to learn new cloud development skills and practices to migrate apps.<\/p>\n
Avoid app downtime:<\/strong><\/h3>\nWith proper planning and the use of techniques like replication, apps can stay online and accessible to users during the migration process. This prevents business disruption.<\/p>\n
Flexible scale:<\/strong><\/h3>\nIn Azure, VMs can be scaled up or down to provide more or less resources to meet changing demand. You only pay for the VM capacity you need.<\/p>\n
Enhanced DR:<\/strong><\/h3>\nNative Azure features like Availability Zones and Region Pairs provide additional options for disaster recovery that are harder to achieve on-prem.<\/p>\n
Lift and shift is a good option when:<\/strong><\/p>\n\n- You have legacy apps that are too complex or risky to modernize. Lift and shift lets you migrate them as-is.<\/li>\n
- Your apps have many complex dependencies that would require significant unraveling and re-architecting to modernize.<\/li>\n
- You need to complete migrations quickly to meet pressing business timelines.<\/li>\n
- You want to migrate apps without disrupting them and causing downtime. Keeping apps online throughout migration is vital.<\/li>\n
- You want to get apps moved to the cloud rapidly to start realizing benefits, even if modernization comes later. Quick wins build confidence and momentum for further cloud adoption.<\/li>\n<\/ul>\n
However, there are some downsides to keep in mind with lift and shift:<\/p>\n
Increased cost:<\/strong><\/h3>\nIn most cases, running workloads on IaaS like VMs costs more over the long term compared to using managed platform services. You miss out on cost optimizations.<\/p>\n
Technical debt accrues:<\/h3>\n
Apps aren’t optimized for the cloud when migrated as-is. You incur more technical debt, making modernization harder later.<\/p>\n
Extra management overhead:<\/h3>\n
Apps running on IaaS still require the same management, monitoring, and maintenance as running them on-prem.<\/p>\n
The cloud doesn’t inherently reduce this hands-on workload.<\/p>\n
Scalability limits remain:<\/h3>\n
Apps are still constrained by their original architectures meant for on-prem hardware. They can’t take advantage of cloud scaling.<\/p>\n
Security gaps:<\/h3>\n
Traditional security models persist. Apps lack cloud-native controls and practices. There is an increased risk of breaches.<\/p>\n
Deployment delays continue:<\/h3>\n
Taking VMs offline to deploy app updates causes the same disruptions as on-prem. No automation gains.<\/p>\n
Finally, lift and shift gets apps to the cloud quickly, buying time to properly modernize later.<\/p>\n
However, most organizations shouldn’t view it as the end state for their migrated apps due to the drawbacks.<\/p>\n
Modernizing: Re-Architecting Apps for the Cloud<\/h2>\n
<\/p>\n
For organizations able to invest more upfront, modernizing apps unlocks the full benefits of the cloud. Here are some key aspects of modernization:<\/p>\n
Cloud-native architecture:<\/h3>\n
<\/p>\n
Apps are refactored and re-architected using cloud design patterns to maximize scalability, availability, performance, and other qualities. Apps are built for the cloud.<\/p>\n
Managed platform services:<\/h3>\n
Where possible, VMs are traded for managed platform services like App Service, Azure SQL, and PaaS options that remove overhead.<\/p>\n
DevOps automation:<\/h3>\n
Automated CI\/CD pipelines, infrastructure as code, and centralized logging among other practices are implemented for greater agility.<\/p>\n
Microservices:<\/h3>\n
Monolithic apps are broken down into independently deployable Microservices that scale better.<\/p>\n
Containerization:
\n<\/h3>\n
Apps are packaged into containers using options like Docker to increase portability. Kubernetes is leveraged for container orchestration.<\/p>\n
Serverless:<\/h3>\n
Serverless computing like Azure Functions replaces VM-bound apps to optimize costs and scale.<\/p>\n
Data cloud migration:<\/h3>\n
On-prem databases are moved to fully managed, cloud-native storage services like Cosmos DB.<\/p>\n
New app features:<\/h3>\n
Parts of apps like UIs or reports can be completely rebuilt to add new capabilities. AI services are integrated to add intelligence.<\/p>\n
The benefits of lift-and-shift often include<\/p>\n
Lower long-term costs:<\/h3>\n
Apps avoid bloated, overprovisioned VMs and instead leverage autoscaling platform services that drive efficiency.<\/p>\n
Reduced overhead:<\/h3>\n
Managed platform services lower administrative and operations overhead compared to IaaS.<\/p>\n
Increased innovation:<\/h3>\n
New cloud-native features boost app functionality in ways not possible with on-prem apps. Competitive advantage grows.<\/p>\n
Improved scalability:<\/h3>\n
Cloud-native, Microservices-based apps scale out easily via autoscaling to meet spikes in demand.<\/p>\n
Faster updates:<\/h3>\n
With CI\/CD pipelines, updates can be deployed multiple times per day without downtime. Business agility increases.<\/p>\n
Enhanced security:<\/h3>\n
Modern apps are designed for cloud-native security practices like zero trust. Risk exposure is lowered.<\/p>\n
However, modernizing apps also requires<\/p>\n
Cloud architecture skills:<\/h3>\n
Your team will need training or hiring to build out expertise in cloud-based application design. This takes time.<\/p>\n
App rewrites:<\/h3>\n
In many cases, large parts of app code will need complete rewrites to become cloud-native. This demands significant developer effort.<\/p>\n
Longer timelines:<\/h3>\n
End-to-end modernization efforts typically take many months or even years to complete. Quick migrations are not realistic.
\nCosts of re-platforming:<\/p>\n
There are costs for data migration<\/a>, Cloud testing services<\/strong><\/a> versions of apps, and addressing integration gaps that lift-and-shift avoids.<\/p>\nFor these reasons, many organizations take an iterative, phased approach to modernizing apps over time rather than trying to transform them all at once. Quick wins help build momentum.<\/p>\n
Key Factors in Choosing a Migration Strategy<\/h2>\n
Organizations don’t have to pick just one migration strategy. Often a mix of lift-and-shift and modernizing works best.<\/p>\n
Consider these key factors when deciding on Azure Cloud Migration Solutions:<\/p>\n
Timeline Requirements<\/h3>\n
Need to migrate quickly?<\/p>\n
Lift-and-shift gets apps to Azure faster, minimizing changes. But modernizing may still be feasible for some newer apps built on cloud-friendly stacks.<\/p>\n
Have time for a longer modernization project?<\/p>\n
Modernizing unlocks the most cloud benefits but requires more upfront effort. With flexible timelines, you can realize the full benefits.<\/p>\n
Application Characteristics<\/h3>\n
Is the app monolithic or tightly coupled?<\/p>\n
These apps are harder to decompose into Microservices. Lift-and-shift minimizes risk for them.<\/p>\n
Is the app already cloud-architected or using Microservices?
\nIt’s a prime candidate for full modernization since cloud optimization is already part of its DNA.<\/p>\n
Does the app use legacy languages like COBOL?<\/p>\n
Lift-and-shift avoids risky, expensive rewrites. But newer Java or C# apps are modernization candidates.<\/p>\n
Is the app built on cloud-native stacks?<\/p>\n
Apps using containers, NoSQL databases, etc. can modernize faster for bigger gains.<\/p>\n
Business Goals<\/h3>\n
Is agility and innovation the priority?<\/p>\n
Modernizing apps unlocks new capabilities that support responding quickly to opportunities.<\/p>\n
Is reducing data center costs the main driver?<\/p>\n
Lift-and-shift cuts expenses much quicker, at least initially.<\/p>\n
Do you want a future-proof architecture?<\/p>\n
Modernizing results in apps aligned with long-term cloud principles.<\/p>\n
Are you migrating a legacy system of record?<\/p>\n
Lift-and-shift is the lowest risk for these foundational apps.<\/p>\n
Cost Considerations<\/h3>\n
Do you have the budget for a major migration effort?<\/p>\n
More budget allows more modernization upfront for long-term gains.<\/p>\n
Is minimizing migration costs critical?<\/p>\n
Lift-and-shift requires less upfront investment compared to modernizing.<\/p>\n
Can you invest in iterative re-platforming over time?<\/p>\n
Spreading modernization over the year smooths costs while increasing benefits.<\/p>\n
Internal Skills<\/h3>\n
Do you have strong cloud architecture skills already?<\/p>\n
Take advantage of this experience to modernize apps using best practices.<\/p>\n
Is your team new to the cloud?<\/p>\n
Lift-and-shift lets you migrate apps without deep cloud expertise.<\/p>\n
Are you willing to train and hire cloud talent?<\/p>\n
Funding skilling and staffing unlocks more modernization capabilities internally.<\/p>\n
Migration Tools<\/h3>\n
Microsoft provides various tools to assess on-prem environments and make recommendations on migrating apps to Azure:<\/p>\n
Azure Migrate:<\/h3>\n
Gives guidance on sizing Azure VMs and PaaS services as part of migration planning based on data collected from on-prem VMs and apps.<\/p>\n
Cloud Adoption Framework:<\/h3>\n
Provides proven methodologies, best practices, and tools for developing an effective cloud migration and modernization strategy.<\/p>\n
Azure App Assessment:<\/h3>\n
Analyzes and generates reports on web apps to determine readiness for migrating to Azure App Service or containers. Makes modernization recommendations.<\/p>\n
The key is to use the right tools for your environment to determine the best path – lift, shift, modernize, or blend.<\/p>\n
With a data-driven analysis of your apps and infrastructure, you can craft a migration approach that sets you up for the most cloud success.<\/p>\n
Hybrid Migration Strategies<\/h2>\n
<\/p>\n
Many organizations find the best approach is a hybrid migration strategy combining lift-and-shift elements and modernizing based on app characteristics. Some key aspects of hybrid migration:<\/p>\n
Leverage both IaaS and PaaS<\/strong>: Lift-and-shift IaaS hosts legacy apps while new apps use PaaS for cloud-native build.<\/p>\n
With lift-and-shift, your developers can use the same tools and processes they are familiar with already.<\/p>\n
There is no need to learn new cloud development skills and practices to migrate apps.<\/p>\n
Avoid app downtime:<\/strong><\/h3>\nWith proper planning and the use of techniques like replication, apps can stay online and accessible to users during the migration process. This prevents business disruption.<\/p>\n
Flexible scale:<\/strong><\/h3>\nIn Azure, VMs can be scaled up or down to provide more or less resources to meet changing demand. You only pay for the VM capacity you need.<\/p>\n
Enhanced DR:<\/strong><\/h3>\nNative Azure features like Availability Zones and Region Pairs provide additional options for disaster recovery that are harder to achieve on-prem.<\/p>\n
Lift and shift is a good option when:<\/strong><\/p>\n\n- You have legacy apps that are too complex or risky to modernize. Lift and shift lets you migrate them as-is.<\/li>\n
- Your apps have many complex dependencies that would require significant unraveling and re-architecting to modernize.<\/li>\n
- You need to complete migrations quickly to meet pressing business timelines.<\/li>\n
- You want to migrate apps without disrupting them and causing downtime. Keeping apps online throughout migration is vital.<\/li>\n
- You want to get apps moved to the cloud rapidly to start realizing benefits, even if modernization comes later. Quick wins build confidence and momentum for further cloud adoption.<\/li>\n<\/ul>\n
However, there are some downsides to keep in mind with lift and shift:<\/p>\n
Increased cost:<\/strong><\/h3>\nIn most cases, running workloads on IaaS like VMs costs more over the long term compared to using managed platform services. You miss out on cost optimizations.<\/p>\n
Technical debt accrues:<\/h3>\n
Apps aren’t optimized for the cloud when migrated as-is. You incur more technical debt, making modernization harder later.<\/p>\n
Extra management overhead:<\/h3>\n
Apps running on IaaS still require the same management, monitoring, and maintenance as running them on-prem.<\/p>\n
The cloud doesn’t inherently reduce this hands-on workload.<\/p>\n
Scalability limits remain:<\/h3>\n
Apps are still constrained by their original architectures meant for on-prem hardware. They can’t take advantage of cloud scaling.<\/p>\n
Security gaps:<\/h3>\n
Traditional security models persist. Apps lack cloud-native controls and practices. There is an increased risk of breaches.<\/p>\n
Deployment delays continue:<\/h3>\n
Taking VMs offline to deploy app updates causes the same disruptions as on-prem. No automation gains.<\/p>\n
Finally, lift and shift gets apps to the cloud quickly, buying time to properly modernize later.<\/p>\n
However, most organizations shouldn’t view it as the end state for their migrated apps due to the drawbacks.<\/p>\n
Modernizing: Re-Architecting Apps for the Cloud<\/h2>\n
<\/p>\n
For organizations able to invest more upfront, modernizing apps unlocks the full benefits of the cloud. Here are some key aspects of modernization:<\/p>\n
Cloud-native architecture:<\/h3>\n
<\/p>\n
Apps are refactored and re-architected using cloud design patterns to maximize scalability, availability, performance, and other qualities. Apps are built for the cloud.<\/p>\n
Managed platform services:<\/h3>\n
Where possible, VMs are traded for managed platform services like App Service, Azure SQL, and PaaS options that remove overhead.<\/p>\n
DevOps automation:<\/h3>\n
Automated CI\/CD pipelines, infrastructure as code, and centralized logging among other practices are implemented for greater agility.<\/p>\n
Microservices:<\/h3>\n
Monolithic apps are broken down into independently deployable Microservices that scale better.<\/p>\n
Containerization:
\n<\/h3>\n
Apps are packaged into containers using options like Docker to increase portability. Kubernetes is leveraged for container orchestration.<\/p>\n
Serverless:<\/h3>\n
Serverless computing like Azure Functions replaces VM-bound apps to optimize costs and scale.<\/p>\n
Data cloud migration:<\/h3>\n
On-prem databases are moved to fully managed, cloud-native storage services like Cosmos DB.<\/p>\n
New app features:<\/h3>\n
Parts of apps like UIs or reports can be completely rebuilt to add new capabilities. AI services are integrated to add intelligence.<\/p>\n
The benefits of lift-and-shift often include<\/p>\n
Lower long-term costs:<\/h3>\n
Apps avoid bloated, overprovisioned VMs and instead leverage autoscaling platform services that drive efficiency.<\/p>\n
Reduced overhead:<\/h3>\n
Managed platform services lower administrative and operations overhead compared to IaaS.<\/p>\n
Increased innovation:<\/h3>\n
New cloud-native features boost app functionality in ways not possible with on-prem apps. Competitive advantage grows.<\/p>\n
Improved scalability:<\/h3>\n
Cloud-native, Microservices-based apps scale out easily via autoscaling to meet spikes in demand.<\/p>\n
Faster updates:<\/h3>\n
With CI\/CD pipelines, updates can be deployed multiple times per day without downtime. Business agility increases.<\/p>\n
Enhanced security:<\/h3>\n
Modern apps are designed for cloud-native security practices like zero trust. Risk exposure is lowered.<\/p>\n
However, modernizing apps also requires<\/p>\n
Cloud architecture skills:<\/h3>\n
Your team will need training or hiring to build out expertise in cloud-based application design. This takes time.<\/p>\n
App rewrites:<\/h3>\n
In many cases, large parts of app code will need complete rewrites to become cloud-native. This demands significant developer effort.<\/p>\n
Longer timelines:<\/h3>\n
End-to-end modernization efforts typically take many months or even years to complete. Quick migrations are not realistic.
\nCosts of re-platforming:<\/p>\n
There are costs for data migration<\/a>, Cloud testing services<\/strong><\/a> versions of apps, and addressing integration gaps that lift-and-shift avoids.<\/p>\nFor these reasons, many organizations take an iterative, phased approach to modernizing apps over time rather than trying to transform them all at once. Quick wins help build momentum.<\/p>\n
Key Factors in Choosing a Migration Strategy<\/h2>\n
Organizations don’t have to pick just one migration strategy. Often a mix of lift-and-shift and modernizing works best.<\/p>\n
Consider these key factors when deciding on Azure Cloud Migration Solutions:<\/p>\n
Timeline Requirements<\/h3>\n
Need to migrate quickly?<\/p>\n
Lift-and-shift gets apps to Azure faster, minimizing changes. But modernizing may still be feasible for some newer apps built on cloud-friendly stacks.<\/p>\n
Have time for a longer modernization project?<\/p>\n
Modernizing unlocks the most cloud benefits but requires more upfront effort. With flexible timelines, you can realize the full benefits.<\/p>\n
Application Characteristics<\/h3>\n
Is the app monolithic or tightly coupled?<\/p>\n
These apps are harder to decompose into Microservices. Lift-and-shift minimizes risk for them.<\/p>\n
Is the app already cloud-architected or using Microservices?
\nIt’s a prime candidate for full modernization since cloud optimization is already part of its DNA.<\/p>\n
Does the app use legacy languages like COBOL?<\/p>\n
Lift-and-shift avoids risky, expensive rewrites. But newer Java or C# apps are modernization candidates.<\/p>\n
Is the app built on cloud-native stacks?<\/p>\n
Apps using containers, NoSQL databases, etc. can modernize faster for bigger gains.<\/p>\n
Business Goals<\/h3>\n
Is agility and innovation the priority?<\/p>\n
Modernizing apps unlocks new capabilities that support responding quickly to opportunities.<\/p>\n
Is reducing data center costs the main driver?<\/p>\n
Lift-and-shift cuts expenses much quicker, at least initially.<\/p>\n
Do you want a future-proof architecture?<\/p>\n
Modernizing results in apps aligned with long-term cloud principles.<\/p>\n
Are you migrating a legacy system of record?<\/p>\n
Lift-and-shift is the lowest risk for these foundational apps.<\/p>\n
Cost Considerations<\/h3>\n
Do you have the budget for a major migration effort?<\/p>\n
More budget allows more modernization upfront for long-term gains.<\/p>\n
Is minimizing migration costs critical?<\/p>\n
Lift-and-shift requires less upfront investment compared to modernizing.<\/p>\n
Can you invest in iterative re-platforming over time?<\/p>\n
Spreading modernization over the year smooths costs while increasing benefits.<\/p>\n
Internal Skills<\/h3>\n
Do you have strong cloud architecture skills already?<\/p>\n
Take advantage of this experience to modernize apps using best practices.<\/p>\n
Is your team new to the cloud?<\/p>\n
Lift-and-shift lets you migrate apps without deep cloud expertise.<\/p>\n
Are you willing to train and hire cloud talent?<\/p>\n
Funding skilling and staffing unlocks more modernization capabilities internally.<\/p>\n
Migration Tools<\/h3>\n
Microsoft provides various tools to assess on-prem environments and make recommendations on migrating apps to Azure:<\/p>\n
Azure Migrate:<\/h3>\n
Gives guidance on sizing Azure VMs and PaaS services as part of migration planning based on data collected from on-prem VMs and apps.<\/p>\n
Cloud Adoption Framework:<\/h3>\n
Provides proven methodologies, best practices, and tools for developing an effective cloud migration and modernization strategy.<\/p>\n
Azure App Assessment:<\/h3>\n
Analyzes and generates reports on web apps to determine readiness for migrating to Azure App Service or containers. Makes modernization recommendations.<\/p>\n
The key is to use the right tools for your environment to determine the best path – lift, shift, modernize, or blend.<\/p>\n
With a data-driven analysis of your apps and infrastructure, you can craft a migration approach that sets you up for the most cloud success.<\/p>\n
Hybrid Migration Strategies<\/h2>\n
<\/p>\n
Many organizations find the best approach is a hybrid migration strategy combining lift-and-shift elements and modernizing based on app characteristics. Some key aspects of hybrid migration:<\/p>\n
Leverage both IaaS and PaaS<\/strong>: Lift-and-shift IaaS hosts legacy apps while new apps use PaaS for cloud-native build.<\/p>\n
In Azure, VMs can be scaled up or down to provide more or less resources to meet changing demand. You only pay for the VM capacity you need.<\/p>\n
Enhanced DR:<\/strong><\/h3>\nNative Azure features like Availability Zones and Region Pairs provide additional options for disaster recovery that are harder to achieve on-prem.<\/p>\n
Lift and shift is a good option when:<\/strong><\/p>\n\n- You have legacy apps that are too complex or risky to modernize. Lift and shift lets you migrate them as-is.<\/li>\n
- Your apps have many complex dependencies that would require significant unraveling and re-architecting to modernize.<\/li>\n
- You need to complete migrations quickly to meet pressing business timelines.<\/li>\n
- You want to migrate apps without disrupting them and causing downtime. Keeping apps online throughout migration is vital.<\/li>\n
- You want to get apps moved to the cloud rapidly to start realizing benefits, even if modernization comes later. Quick wins build confidence and momentum for further cloud adoption.<\/li>\n<\/ul>\n
However, there are some downsides to keep in mind with lift and shift:<\/p>\n
Increased cost:<\/strong><\/h3>\nIn most cases, running workloads on IaaS like VMs costs more over the long term compared to using managed platform services. You miss out on cost optimizations.<\/p>\n
Technical debt accrues:<\/h3>\n
Apps aren’t optimized for the cloud when migrated as-is. You incur more technical debt, making modernization harder later.<\/p>\n
Extra management overhead:<\/h3>\n
Apps running on IaaS still require the same management, monitoring, and maintenance as running them on-prem.<\/p>\n
The cloud doesn’t inherently reduce this hands-on workload.<\/p>\n
Scalability limits remain:<\/h3>\n
Apps are still constrained by their original architectures meant for on-prem hardware. They can’t take advantage of cloud scaling.<\/p>\n
Security gaps:<\/h3>\n
Traditional security models persist. Apps lack cloud-native controls and practices. There is an increased risk of breaches.<\/p>\n
Deployment delays continue:<\/h3>\n
Taking VMs offline to deploy app updates causes the same disruptions as on-prem. No automation gains.<\/p>\n
Finally, lift and shift gets apps to the cloud quickly, buying time to properly modernize later.<\/p>\n
However, most organizations shouldn’t view it as the end state for their migrated apps due to the drawbacks.<\/p>\n
Modernizing: Re-Architecting Apps for the Cloud<\/h2>\n
<\/p>\n
For organizations able to invest more upfront, modernizing apps unlocks the full benefits of the cloud. Here are some key aspects of modernization:<\/p>\n
Cloud-native architecture:<\/h3>\n
<\/p>\n
Apps are refactored and re-architected using cloud design patterns to maximize scalability, availability, performance, and other qualities. Apps are built for the cloud.<\/p>\n
Managed platform services:<\/h3>\n
Where possible, VMs are traded for managed platform services like App Service, Azure SQL, and PaaS options that remove overhead.<\/p>\n
DevOps automation:<\/h3>\n
Automated CI\/CD pipelines, infrastructure as code, and centralized logging among other practices are implemented for greater agility.<\/p>\n
Microservices:<\/h3>\n
Monolithic apps are broken down into independently deployable Microservices that scale better.<\/p>\n
Containerization:
\n<\/h3>\n
Apps are packaged into containers using options like Docker to increase portability. Kubernetes is leveraged for container orchestration.<\/p>\n
Serverless:<\/h3>\n
Serverless computing like Azure Functions replaces VM-bound apps to optimize costs and scale.<\/p>\n
Data cloud migration:<\/h3>\n
On-prem databases are moved to fully managed, cloud-native storage services like Cosmos DB.<\/p>\n
New app features:<\/h3>\n
Parts of apps like UIs or reports can be completely rebuilt to add new capabilities. AI services are integrated to add intelligence.<\/p>\n
The benefits of lift-and-shift often include<\/p>\n
Lower long-term costs:<\/h3>\n
Apps avoid bloated, overprovisioned VMs and instead leverage autoscaling platform services that drive efficiency.<\/p>\n
Reduced overhead:<\/h3>\n
Managed platform services lower administrative and operations overhead compared to IaaS.<\/p>\n
Increased innovation:<\/h3>\n
New cloud-native features boost app functionality in ways not possible with on-prem apps. Competitive advantage grows.<\/p>\n
Improved scalability:<\/h3>\n
Cloud-native, Microservices-based apps scale out easily via autoscaling to meet spikes in demand.<\/p>\n
Faster updates:<\/h3>\n
With CI\/CD pipelines, updates can be deployed multiple times per day without downtime. Business agility increases.<\/p>\n
Enhanced security:<\/h3>\n
Modern apps are designed for cloud-native security practices like zero trust. Risk exposure is lowered.<\/p>\n
However, modernizing apps also requires<\/p>\n
Cloud architecture skills:<\/h3>\n
Your team will need training or hiring to build out expertise in cloud-based application design. This takes time.<\/p>\n
App rewrites:<\/h3>\n
In many cases, large parts of app code will need complete rewrites to become cloud-native. This demands significant developer effort.<\/p>\n
Longer timelines:<\/h3>\n
End-to-end modernization efforts typically take many months or even years to complete. Quick migrations are not realistic.
\nCosts of re-platforming:<\/p>\n
There are costs for data migration<\/a>, Cloud testing services<\/strong><\/a> versions of apps, and addressing integration gaps that lift-and-shift avoids.<\/p>\nFor these reasons, many organizations take an iterative, phased approach to modernizing apps over time rather than trying to transform them all at once. Quick wins help build momentum.<\/p>\n
Key Factors in Choosing a Migration Strategy<\/h2>\n
Organizations don’t have to pick just one migration strategy. Often a mix of lift-and-shift and modernizing works best.<\/p>\n
Consider these key factors when deciding on Azure Cloud Migration Solutions:<\/p>\n
Timeline Requirements<\/h3>\n
Need to migrate quickly?<\/p>\n
Lift-and-shift gets apps to Azure faster, minimizing changes. But modernizing may still be feasible for some newer apps built on cloud-friendly stacks.<\/p>\n
Have time for a longer modernization project?<\/p>\n
Modernizing unlocks the most cloud benefits but requires more upfront effort. With flexible timelines, you can realize the full benefits.<\/p>\n
Application Characteristics<\/h3>\n
Is the app monolithic or tightly coupled?<\/p>\n
These apps are harder to decompose into Microservices. Lift-and-shift minimizes risk for them.<\/p>\n
Is the app already cloud-architected or using Microservices?
\nIt’s a prime candidate for full modernization since cloud optimization is already part of its DNA.<\/p>\n
Does the app use legacy languages like COBOL?<\/p>\n
Lift-and-shift avoids risky, expensive rewrites. But newer Java or C# apps are modernization candidates.<\/p>\n
Is the app built on cloud-native stacks?<\/p>\n
Apps using containers, NoSQL databases, etc. can modernize faster for bigger gains.<\/p>\n
Business Goals<\/h3>\n
Is agility and innovation the priority?<\/p>\n
Modernizing apps unlocks new capabilities that support responding quickly to opportunities.<\/p>\n
Is reducing data center costs the main driver?<\/p>\n
Lift-and-shift cuts expenses much quicker, at least initially.<\/p>\n
Do you want a future-proof architecture?<\/p>\n
Modernizing results in apps aligned with long-term cloud principles.<\/p>\n
Are you migrating a legacy system of record?<\/p>\n
Lift-and-shift is the lowest risk for these foundational apps.<\/p>\n
Cost Considerations<\/h3>\n
Do you have the budget for a major migration effort?<\/p>\n
More budget allows more modernization upfront for long-term gains.<\/p>\n
Is minimizing migration costs critical?<\/p>\n
Lift-and-shift requires less upfront investment compared to modernizing.<\/p>\n
Can you invest in iterative re-platforming over time?<\/p>\n
Spreading modernization over the year smooths costs while increasing benefits.<\/p>\n
Internal Skills<\/h3>\n
Do you have strong cloud architecture skills already?<\/p>\n
Take advantage of this experience to modernize apps using best practices.<\/p>\n
Is your team new to the cloud?<\/p>\n
Lift-and-shift lets you migrate apps without deep cloud expertise.<\/p>\n
Are you willing to train and hire cloud talent?<\/p>\n
Funding skilling and staffing unlocks more modernization capabilities internally.<\/p>\n
Migration Tools<\/h3>\n
Microsoft provides various tools to assess on-prem environments and make recommendations on migrating apps to Azure:<\/p>\n
Azure Migrate:<\/h3>\n
Gives guidance on sizing Azure VMs and PaaS services as part of migration planning based on data collected from on-prem VMs and apps.<\/p>\n
Cloud Adoption Framework:<\/h3>\n
Provides proven methodologies, best practices, and tools for developing an effective cloud migration and modernization strategy.<\/p>\n
Azure App Assessment:<\/h3>\n
Analyzes and generates reports on web apps to determine readiness for migrating to Azure App Service or containers. Makes modernization recommendations.<\/p>\n
The key is to use the right tools for your environment to determine the best path – lift, shift, modernize, or blend.<\/p>\n
With a data-driven analysis of your apps and infrastructure, you can craft a migration approach that sets you up for the most cloud success.<\/p>\n
Hybrid Migration Strategies<\/h2>\n
<\/p>\n
Many organizations find the best approach is a hybrid migration strategy combining lift-and-shift elements and modernizing based on app characteristics. Some key aspects of hybrid migration:<\/p>\n
Leverage both IaaS and PaaS<\/strong>: Lift-and-shift IaaS hosts legacy apps while new apps use PaaS for cloud-native build.<\/p>\n
- \n
- You have legacy apps that are too complex or risky to modernize. Lift and shift lets you migrate them as-is.<\/li>\n
- Your apps have many complex dependencies that would require significant unraveling and re-architecting to modernize.<\/li>\n
- You need to complete migrations quickly to meet pressing business timelines.<\/li>\n
- You want to migrate apps without disrupting them and causing downtime. Keeping apps online throughout migration is vital.<\/li>\n
- You want to get apps moved to the cloud rapidly to start realizing benefits, even if modernization comes later. Quick wins build confidence and momentum for further cloud adoption.<\/li>\n<\/ul>\n
However, there are some downsides to keep in mind with lift and shift:<\/p>\n
Increased cost:<\/strong><\/h3>\n
In most cases, running workloads on IaaS like VMs costs more over the long term compared to using managed platform services. You miss out on cost optimizations.<\/p>\n
Technical debt accrues:<\/h3>\n
Apps aren’t optimized for the cloud when migrated as-is. You incur more technical debt, making modernization harder later.<\/p>\n
Extra management overhead:<\/h3>\n
Apps running on IaaS still require the same management, monitoring, and maintenance as running them on-prem.<\/p>\n
The cloud doesn’t inherently reduce this hands-on workload.<\/p>\n
Scalability limits remain:<\/h3>\n
Apps are still constrained by their original architectures meant for on-prem hardware. They can’t take advantage of cloud scaling.<\/p>\n
Security gaps:<\/h3>\n
Traditional security models persist. Apps lack cloud-native controls and practices. There is an increased risk of breaches.<\/p>\n
Deployment delays continue:<\/h3>\n
Taking VMs offline to deploy app updates causes the same disruptions as on-prem. No automation gains.<\/p>\n
Finally, lift and shift gets apps to the cloud quickly, buying time to properly modernize later.<\/p>\n
However, most organizations shouldn’t view it as the end state for their migrated apps due to the drawbacks.<\/p>\n
Modernizing: Re-Architecting Apps for the Cloud<\/h2>\n
<\/p>\nFor organizations able to invest more upfront, modernizing apps unlocks the full benefits of the cloud. Here are some key aspects of modernization:<\/p>\n
Cloud-native architecture:<\/h3>\n
<\/p>\nApps are refactored and re-architected using cloud design patterns to maximize scalability, availability, performance, and other qualities. Apps are built for the cloud.<\/p>\n
Managed platform services:<\/h3>\n
Where possible, VMs are traded for managed platform services like App Service, Azure SQL, and PaaS options that remove overhead.<\/p>\n
DevOps automation:<\/h3>\n
Automated CI\/CD pipelines, infrastructure as code, and centralized logging among other practices are implemented for greater agility.<\/p>\n
Microservices:<\/h3>\n
Monolithic apps are broken down into independently deployable Microservices that scale better.<\/p>\n
Containerization:
\n<\/h3>\nApps are packaged into containers using options like Docker to increase portability. Kubernetes is leveraged for container orchestration.<\/p>\n
Serverless:<\/h3>\n
Serverless computing like Azure Functions replaces VM-bound apps to optimize costs and scale.<\/p>\n
Data cloud migration:<\/h3>\n
On-prem databases are moved to fully managed, cloud-native storage services like Cosmos DB.<\/p>\n
New app features:<\/h3>\n
Parts of apps like UIs or reports can be completely rebuilt to add new capabilities. AI services are integrated to add intelligence.<\/p>\n
The benefits of lift-and-shift often include<\/p>\n
Lower long-term costs:<\/h3>\n
Apps avoid bloated, overprovisioned VMs and instead leverage autoscaling platform services that drive efficiency.<\/p>\n
Reduced overhead:<\/h3>\n
Managed platform services lower administrative and operations overhead compared to IaaS.<\/p>\n
Increased innovation:<\/h3>\n
New cloud-native features boost app functionality in ways not possible with on-prem apps. Competitive advantage grows.<\/p>\n
Improved scalability:<\/h3>\n
Cloud-native, Microservices-based apps scale out easily via autoscaling to meet spikes in demand.<\/p>\n
Faster updates:<\/h3>\n
With CI\/CD pipelines, updates can be deployed multiple times per day without downtime. Business agility increases.<\/p>\n
Enhanced security:<\/h3>\n
Modern apps are designed for cloud-native security practices like zero trust. Risk exposure is lowered.<\/p>\n
However, modernizing apps also requires<\/p>\n
Cloud architecture skills:<\/h3>\n
Your team will need training or hiring to build out expertise in cloud-based application design. This takes time.<\/p>\n
App rewrites:<\/h3>\n
In many cases, large parts of app code will need complete rewrites to become cloud-native. This demands significant developer effort.<\/p>\n
Longer timelines:<\/h3>\n
End-to-end modernization efforts typically take many months or even years to complete. Quick migrations are not realistic.
\nCosts of re-platforming:<\/p>\nThere are costs for data migration<\/a>, Cloud testing services<\/strong><\/a> versions of apps, and addressing integration gaps that lift-and-shift avoids.<\/p>\n
For these reasons, many organizations take an iterative, phased approach to modernizing apps over time rather than trying to transform them all at once. Quick wins help build momentum.<\/p>\n
Key Factors in Choosing a Migration Strategy<\/h2>\n
Organizations don’t have to pick just one migration strategy. Often a mix of lift-and-shift and modernizing works best.<\/p>\n
Consider these key factors when deciding on Azure Cloud Migration Solutions:<\/p>\n
Timeline Requirements<\/h3>\n
Need to migrate quickly?<\/p>\n
Lift-and-shift gets apps to Azure faster, minimizing changes. But modernizing may still be feasible for some newer apps built on cloud-friendly stacks.<\/p>\n
Have time for a longer modernization project?<\/p>\n
Modernizing unlocks the most cloud benefits but requires more upfront effort. With flexible timelines, you can realize the full benefits.<\/p>\n
Application Characteristics<\/h3>\n
Is the app monolithic or tightly coupled?<\/p>\n
These apps are harder to decompose into Microservices. Lift-and-shift minimizes risk for them.<\/p>\n
Is the app already cloud-architected or using Microservices?
\nIt’s a prime candidate for full modernization since cloud optimization is already part of its DNA.<\/p>\nDoes the app use legacy languages like COBOL?<\/p>\n
Lift-and-shift avoids risky, expensive rewrites. But newer Java or C# apps are modernization candidates.<\/p>\n
Is the app built on cloud-native stacks?<\/p>\n
Apps using containers, NoSQL databases, etc. can modernize faster for bigger gains.<\/p>\n
Business Goals<\/h3>\n
Is agility and innovation the priority?<\/p>\n
Modernizing apps unlocks new capabilities that support responding quickly to opportunities.<\/p>\n
Is reducing data center costs the main driver?<\/p>\n
Lift-and-shift cuts expenses much quicker, at least initially.<\/p>\n
Do you want a future-proof architecture?<\/p>\n
Modernizing results in apps aligned with long-term cloud principles.<\/p>\n
Are you migrating a legacy system of record?<\/p>\n
Lift-and-shift is the lowest risk for these foundational apps.<\/p>\n
Cost Considerations<\/h3>\n
Do you have the budget for a major migration effort?<\/p>\n
More budget allows more modernization upfront for long-term gains.<\/p>\n
Is minimizing migration costs critical?<\/p>\n
Lift-and-shift requires less upfront investment compared to modernizing.<\/p>\n
Can you invest in iterative re-platforming over time?<\/p>\n
Spreading modernization over the year smooths costs while increasing benefits.<\/p>\n
Internal Skills<\/h3>\n
Do you have strong cloud architecture skills already?<\/p>\n
Take advantage of this experience to modernize apps using best practices.<\/p>\n
Is your team new to the cloud?<\/p>\n
Lift-and-shift lets you migrate apps without deep cloud expertise.<\/p>\n
Are you willing to train and hire cloud talent?<\/p>\n
Funding skilling and staffing unlocks more modernization capabilities internally.<\/p>\n
Migration Tools<\/h3>\n
Microsoft provides various tools to assess on-prem environments and make recommendations on migrating apps to Azure:<\/p>\n
Azure Migrate:<\/h3>\n
Gives guidance on sizing Azure VMs and PaaS services as part of migration planning based on data collected from on-prem VMs and apps.<\/p>\n
Cloud Adoption Framework:<\/h3>\n
Provides proven methodologies, best practices, and tools for developing an effective cloud migration and modernization strategy.<\/p>\n
Azure App Assessment:<\/h3>\n
Analyzes and generates reports on web apps to determine readiness for migrating to Azure App Service or containers. Makes modernization recommendations.<\/p>\n
The key is to use the right tools for your environment to determine the best path – lift, shift, modernize, or blend.<\/p>\n
With a data-driven analysis of your apps and infrastructure, you can craft a migration approach that sets you up for the most cloud success.<\/p>\n
Hybrid Migration Strategies<\/h2>\n
<\/p>\nMany organizations find the best approach is a hybrid migration strategy combining lift-and-shift elements and modernizing based on app characteristics. Some key aspects of hybrid migration:<\/p>\n
Leverage both IaaS and PaaS<\/strong>: Lift-and-shift IaaS hosts legacy apps while new apps use PaaS for cloud-native build.<\/p>\n