Issue link: https://insights.oneneck.com/i/1171394
Not all workloads are suitable for running in the cloud. Key factors include application attributes, business requirements, and compliance needs. Based on assessment results, on-premises workloads can be categorized into different levels of cloud migration suitability, such as: Ready for migration Can be lifted and shifted to Azure with no changes. Optimized for cloud Possible to rearchitect and then recode for cloud computing. Redesign for cloud-ready Must be modernized with cloud-native technologies. Here, a compilation of customized line-of- business and enterprise applications make up 65 percent of the migration portfolio. Most of these have been identified as "first to move" and are basic web apps or solutions that can be directly migrated to Azure without any code changes. Some of the remainder are identified as candidates that are "next to move," with some code changes. A small portion are identified as "hard or costly to move," and less than 5 percent of applications will remain on- premises (Figure 1). Figure 1: Assessing organizational infrastructure to prepare for cloud migration Retire it, right-size, or eliminate environments From... ...To Use or convert to a SaaS (1st- or 3rd-party solution) Expose functionality in existing SaaS/PaaS solution Convert to Azure PaaS solution Optimize for and move to Azure IaaS No change, lift & shift to IaaS Remain on-premises <5% ~20% ~10% Office servers Portals and SPS Any relationship management Active source control & WIT Data warehouses Industry standard verticals Office 365 SharePoint Online CRM Online VSO ADL + Power BI Best 3rd-party SaaS First to move <45% Basic web apps Advanced portals Any new solutions Any re-architected solutions Next to move <15% High I/O OLTP Regulatory and high business impact Hard or costly to move <5% HVA systems PKI systems Legacy source control Azure IT roadmap Developing a cloud migration strategy Chapter 03 9