Evaluate and mitigate migration risks
This document describes how to handle migration risks by creating a migrationrisk assessment.
Migration risk assessment
In large transformation programs, organizations confront a number of factorsthat might pose varying degrees of risks during and after the cloud migration.It is therefore essential that you continuously collect data to identifythese risks, and undertake mitigation. This creates the need for a migrationrisk assessment workstream as a part of your program governance for cloudtransformation.
Usually, initial high-level discovery and assessment efforts producedirectional recommendations on migration strategy and planning.As soon as you start your migration wave planning, it is critical that you runthe discovery and assessment effort continuously.Continuous discovery produces additional workload-specificdata points and allows you to refine the scope and priorities of the migrationwaves.
Typical migration risks
The following table presents typically encountered migration risks, and howtheir mitigation helps refine the migration wave planning.
| Risks | Description | Possible mitigation strategies |
|---|---|---|
| Technical blockers | Factors that prevent the migration of specific workloads. Forexample, stored procedures can block database migration to PaaS. | Incorporate a blocker mitigation workstream to eliminate blockersbefore the migration. Alternatively, move the migration plan for these workloads to laterwaves. |
| Regulatory requirements and constraints | Requirements for data protection and privacy, including datalocalization. | Refine the foundational architecture to incorporate improvements,such as restricted landing zones and regional replication strategies. Use separate migration waves for workloads with regulatoryconstraints and non regulated workloads. |
| Performance and availability requirements | Typically, applications with a high degree of mission criticality anda geographically widespread user base have stringent requirements forresponse time and maximum acceptable latency. | Before you start the migration wave, validate right-sizing forperformance and availability. |
| Interconnect between migrated and non-migratedworkloads | Upstream and downstream connectivity between migrated andnon-migrated workloads can impact SLAs and BLAs. | Optimize the sizing of interconnect, and readjust the migrationwaves. |
| Security requirements | Security requirements for specific workloads, such as data,application, and network. | Continuously refine the foundational architecture to address securityneeds. This might also require you to adjust the migrationwaves. |
What's next
- Learn how toplan your migration waves.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.