Issue link: https://insights.oneneck.com/i/1443186
5 How should I think about migration and modernization with the cloud? For many organizations, migration—the process of moving workloads to cloud infrastructure as a service (IaaS) quickly and with minimal changes—is a valuable tactic to speed cloud adoption. Migrating apps as-is to the cloud helps flip capital expense (CAPEX) to operational expense (OPEX) and quickly gain agility and scale. However, while this is often the starting point for the cloud journey, it's rarely the end. Modernizing applications, data, and operations requires more in-depth evaluation and retooling of existing workloads. As the future comes into focus, organizations should consider how they can take advantage of platform-as-a-service (PaaS) capabilities like built-in security, patching, high availability, and auto-scaling. Modernizing may also involve breaking an application into modular parts that can be easily replaced or updated. Most organizations start with rapid lift-and-shift migration due to timeline pressures, legacy workloads, and the need to maintain fine-grained control over their workloads, while others start with modernization and work extensively on applications to ready and optimize them for the cloud before putting them into production. When it comes to the sequence of migrate first and modernize later, or doing them in parallel, both are valid strategies. Each migration and modernization journey is unique and depends on your workload complexity and business priorities. Migration and modernization CONTROL PRODUCTIVITY VMs / Virtual desktops Containers Managed databases Low code apps PaaS