5.1.3. Design a Migration Solution
💡 First Principle: A successful cloud migration is a strategic process of discovery, planning, execution, and optimization that enables organizations to transition workloads to the cloud with minimal disruption, risk, and cost.
The migration lifecycle, and what belongs in each phase:
Two assessment outputs are examined far more than the rest. Dependency analysis is what turns a server list into correctly grouped migration waves — move one half of a chatty pair and its traffic crosses back to the datacenter. Performance-based sizing is what makes the cost projection honest, because sizing as-on-premises carries the estate's existing over-provisioning straight into Azure.
⚠️ Exam Trap: any option that starts replicating or cutting over during the assessment phase is wrong. It commits target sizing before the data that should inform it exists.
Scenario: You are designing a migration plan for a legacy enterprise application that includes several Virtual Machines, a large SQL Server database, and shared file servers on-premises. The business requires minimal downtime for the database and a phased migration approach for the VMs.
Think of cloud migration like moving offices. You wouldn't move everything in one truck on one day — you'd assess what you have, decide what to keep/upgrade/discard, move in waves starting with the least critical items, and validate each wave before the next. The 5 R's framework maps directly to this analogy:
| Strategy | Office Analogy | Azure Approach | Effort | Benefit |
|---|---|---|---|---|
| Rehost | Move desk as-is | Lift-and-shift to VMs | Low | Fast migration |
| Replatform | Same desk, new building utilities | Move to PaaS (App Service, managed DB) | Medium | Reduced ops |
| Refactor | Redesign workspace | Cloud-native rebuild (microservices, serverless) | High | Maximum cloud benefit |
| Retire | Throw away old furniture | Decommission unused apps | None | Cost savings |
| Retain | Keep in old office | Keep on-premises (for now) | None | Avoid unnecessary risk |
A migration solution facilitates the secure and efficient transfer of on-premises workloads, applications, and data to the Azure cloud, enabling organizations to leverage cloud benefits while minimizing disruption.
Key Design Considerations:
- Assessment and Planning: Evaluate existing infrastructure and dependencies. Define migration goals and create a detailed plan. Use Azure Migrate for discovery.
- Migration Strategy: Choose between rehost (lift-and-shift), refactor, re-architect, rebuild, or replace.
- Data Migration: Select appropriate tools for transferring data, considering volume and downtime tolerance. Use Azure Data Box for large offline transfers, or Azure Database Migration Service (DMS).
- Application Migration: Migrate applications, ensuring compatibility and performance.
- Network Connectivity: Establish secure connectivity between on-premises and Azure (Azure VPN Gateway, Azure ExpressRoute).
- Security and Compliance: Integrate security controls and ensure compliance throughout the migration.
- Azure Migration Services: Leverage Azure Migrate for discovery, assessment, and migration. Utilize Azure Database Migration Service (DMS) for specialized database migrations.
⚠️ Common Pitfall: A "lift-and-shift" migration with no plan for future modernization. While rehosting is a valid first step, stopping there means leaving most of the cloud's benefits—like elasticity and managed services—on the table.
Key Trade-Offs:
- Speed of Migration vs. Cloud Optimization: The fastest migration strategies (like rehosting) provide the fewest cloud-native benefits. The most beneficial strategies (like refactoring) take the most time and effort.
Reflection Question: How does designing a migration solution (including assessment, strategy choice, data migration, and application migration tools like Azure Migrate and DMS) fundamentally facilitate the secure and efficient transfer of on-premises workloads to Azure, enabling cloud benefits while minimizing disruption and risk?
