Migration Wave Planner
Sequence applications and workloads while preserving economic accountability.
Waves organize migration work into manageable periods with owners, planned dates and a portfolio of applications/workloads. A wave is a planning object; it is not an AWS automation trigger.
Security
Plan a wave
Create the wave, assign an owner and a proposed window, select workloads, review readiness blockers and compare cost exposure. Identify whether the planned sequence creates avoidable overlapping source/target charges or strands shared services.
Change control
When a workload moves between waves, retain the action history and review downstream economics. Current wave membership is mutable planning state; historical financial rollups are not rewritten retroactively by the reassignment.
Operating review
A weekly migration review should check upcoming waves, blocked workloads, target environment readiness, expected overlap duration and decommission prerequisites. Escalate high-impact exceptions to the authorized approval workflow.
Financial discipline
Wave-level savings are modeled until the underlying source cost has actually been removed and the target costs observed. Avoid summing overlapping application assumptions into a guaranteed program total.