Evaluate and mitigate migration risks

Stay organized with collections Save and categorize content based on your preferences.

This document describes how to handle migration risks by creating a migration risk assessment.

Migration risk assessment

In large transformation programs, organizations confront a number of factors that might pose varying degrees of risks during and after the cloud migration. It is therefore essential that you continuously collect data to identify these risks, and undertake mitigation. This creates the need for a migration risk assessment workstream as a part of your program governance for cloud transformation.

Usually, initial high-level discovery and assessment efforts produce directional recommendations on migration strategy and planning. As soon as you start your migration wave planning, it is critical that you run the discovery and assessment effort continuously. Continuous discovery produces additional workload-specific data points and allows you to refine the scope and priorities of the migration waves.

Typical migration risks

The following table presents typically encountered migration risks, and how their mitigation helps refine the migration wave planning.

Risks Description Possible mitigation strategies
Technical blockers Factors that prevent the migration of specific workloads. For example, stored procedures can block database migration to PaaS. Incorporate a blocker mitigation workstream to eliminate blockers before the migration.

Alternatively, move the migration plan for these workloads to later waves.
Regulatory requirements and constraints Requirements for data protection and privacy, including data localization. Refine the foundational architecture to incorporate improvements, such as restricted landing zones and regional replication strategies.

Use separate migration waves for workloads with regulatory constraints and non regulated workloads.
Performance and availability requirements Typically, applications with a high degree of mission criticality and a geographically widespread user base have stringent requirements for response time and maximum acceptable latency. Before you start the migration wave, validate right-sizing for performance and availability.
Interconnect between migrated and non-migrated workloads Upstream and downstream connectivity between migrated and non-migrated workloads can impact SLAs and BLAs. Optimize the sizing of interconnect, and readjust the migration waves.
Security requirements Security requirements for specific workloads, such as data, application, and network. Continuously refine the foundational architecture to address security needs. This might also require you to adjust the migration waves.

What's next