Read a sample: 1. From Approved Assessment to Executable Plan
An approved migration assessment is permission to plan a move, not proof that the move is ready to happen. It may identify the workloads in scope, recommend Azure destinations, and record the business case. It rarely tells the operations team exactly when to stop writes, who confirms that an integration works, or how long the team can investigate a failure before recovery must begin.
Those questions belong to the cutover plan. They turn a proposed migration into a controlled change with an executable sequence, observable results, assigned decision makers, and a credible way to recover.
This chapter establishes the boundary between assessment and execution. You will interpret approved findings without treating every estimate as a guarantee, identify missing information before a date is committed, and start a set of artifacts that will grow into the migration team’s readiness packet.
An assessment generally asks whether a migration is feasible and what approach should be considered. Execution planning asks how an approved approach will be performed under real operating constraints.
The distinction matters because a planning team can encounter uncertainty without having authority to redesign the entire migration. If the assessment approves a workload for migration to a particular Azure landing zone, the planner should use that destination as the starting point. If a required network path is unclear, the planner should investigate the path and obtain confirmation. If that investigation reveals the approved destination cannot support a mandatory requirement, the planner should escalate the conflict through the established approval process rather than quietly choosing a different destination.
Use three categories to keep that boundary visible:
- Approved decisions are authorized inputs to the plan, such as scope, destination, migration approach, and constraints recorded by the assessment.
- Planning details are the operational choices needed to carry out those decisions, such as task order, handoffs, evidence, and proposed decision times.
- Material changes alter an approved decision or introduce a conflict that the planning team cannot resolve within its authority.
Not every unanswered question is a material change. Selecting the person who will verify an application’s sign-in is a planning detail. Discovering that a supposedly noncritical application supports a time-sensitive business process may affect scope, sequencing, or acceptance and therefore requires review by the appropriate owners.
The goal is neither to reopen the assessment at every ambiguity nor to protect the assessment from new evidence. The goal is to preserve a traceable path from approved intent to executable action.
Throughout this book, we will use a fictional order-processing workload called Harbor Orders. Its assessment has been approved for migration from an on-premises environment to Azure. The application supports internal order entry and sends order status information to an external fulfillment service.
The approved assessment records the following:
- The application tier and its database are in scope for the migration.
- The target is an approved Azure landing zone using virtual machines for the application and database tiers.
- Corporate identity, connectivity to the landing zone, and monitoring are expected to be available before cutover.
- The external fulfillment service remains outside the migration scope but must continue to exchange information with Harbor Orders.
- The proposed approach includes preparing the target environment and synchronizing data before a planned cutover.
- The business requires a controlled interruption and confirmation that representative orders can be processed after the move.
These statements provide useful direction, but they do not constitute a weekend plan. “Connectivity available” does not identify every path that must be tested. “Synchronizing data” does not establish how the final synchronization will be checked. A requirement for representative orders does not identify the person authorized to accept the results.
The example deliberately leaves those details open. The team will resolve them as planning progresses. Where a fact has not been approved or verified, it remains an assumption, question, or action—not a hidden promise in the runbook.
Begin by gathering the approved assessment and its supporting records. Depending on the organization, these may include a workload inventory, dependency diagrams, architecture decisions, sizing estimates, risk register, business impact information, and a migration recommendation. Confirm which versions were approved and whether later changes have been authorized.
Then translate the material into planning inputs. For each important statement, ask four questions:
1. What does it authorize or require?
2. What evidence supports it, and how current is that evidence?
3. What must be true for the cutover plan to rely on it?
4. Who can confirm it or decide what happens if it is not true?
For Harbor Orders, consider the statement that corporate identity will be available before cutover. It is a prerequisite, not a task sequence. The planner still needs to identify the sign-in paths used by administrators, application components, and business users; determine how those paths will be tested; and assign owners to provide evidence. The assessment may have identified identity as a dependency without describing every validation step.
Similarly, an assessment may contain an estimated outage. Treat it as an input to be tested against the eventual sequence, not as a duration already reserved for the migration team. A practical schedule must account for stopping activity, final synchronization, traffic changes, technical checks, business checks, decision-making, and recovery time. The estimate becomes useful when the team understands its assumptions and compares them with the planned work.
A simple interpretation record keeps this distinction visible:
The table is not a substitute for the assessment.…