Project Overview and Readiness

Project Overview and Readiness

Project Overview is the control center for the workbook. It records the migration identity and key owners, then summarizes task, risk, validation, redirect, and decision signals from the other sheets so the team can identify what needs attention next.

The summary is intentionally operational. It helps you locate open work, but it does not replace validation, sign-off, or a decision to launch.

Set up the project identity

Complete the identity fields before building the detailed plan.

Field	What to record	Why it matters
Project Name	A clear internal project name.	Keeps exports, evidence, and meetings tied to the same migration.
Project ID	Your internal identifier when one exists.	Provides a stable reference across project systems.
Source Platform / Target Platform	The platforms in the purchased migration path.	Establishes the direction the project is planning for.
Migration Path	Calculated from the Source Platform and Target Platform values.	Gives the team a quick directional check.
Supported Data Reference	The verified migration-path or Documentation reference used for scope planning.	Keeps scope decisions connected to the supported-data reference used for the project.
Migration Service	Standard Service, Managed Service, or Custom Service.	Affects execution responsibilities and the purchased scope.
Entity Points Plan / Purchased Entity Points	The purchased capacity.	Helps the team recognize when capacity review is required.
Purchased Add-ons	The Add-ons included in the migration.	Keeps planned configuration and validation aligned with the purchase.
Approved Customization	A short reference to approved Custom Service work.	Connects non-standard requirements to the project baseline without duplicating the full specification.
Service Expiry	The expiration value shown for the migration.	Keeps the plan aligned with the available service period.
Project Owner / Launch Approver	The people accountable for coordination and final launch authority.	Prevents unclear approval responsibility.
Evidence Repository	The secure project location used for detailed evidence.	Keeps the workbook lightweight while preserving traceability.
Next-Cart Contact	The relevant Next-Cart contact when applicable.	Gives the team a clear escalation reference.

Confirm purchased migration details in My Migrations by expanding Migrations in the Dashboard and selecting My Migrations, rather than estimating them from the plan.

Record milestone and control dates

Use the milestone fields to align the workbook to the project’s operating calendar:

• Demo Migration planned date;
• Full Migration planned date;
• Launch window;
• Project Time Zone;
• As of Date;
• Project Status.

The As of Date matters because overdue-task signals use it as the reference point. Update it whenever the team wants the readiness summary to reflect a new review date.

Read the readiness indicators

The Overview calculates several signals from the working sheets.

Indicator	What it means	Where to investigate
Task completion	Percentage of rows with a Task ID whose Status is Completed.	Project Plan
Open task blockers	Signals from tasks marked Blocking? = Yes and incomplete tasks whose due date is earlier than the As of Date.	Project Plan
Residual High / Critical risks	Risks whose residual score remains High or Critical after mitigation.	Risk Register
Validation failures	Validation rows whose Result is Fail.	Validation
Redirect blockers	Redirect rows whose calculated Readiness is Blocked or Decision required.	Redirects
Open launch decisions	Launch-blocking decision rows that are not Approved or Approved with limitations.	Decisions & Sign-off
Validation completion	Percentage of Validation IDs that have a recorded terminal result: Pass, Pass with accepted limitations, Fail, or Not applicable.	Validation
Overall readiness	A summary state derived from the signals above, task completion, and validation completion.	All working sheets

Use blocker totals as investigation signals

Open task blockers combines explicit blocking flags with overdue incomplete work. A task can contribute more than one signal when both conditions apply. Use the total to prompt a review of Project Plan, not as a unique-task count.

Interpret Overall readiness

The workbook uses four high-level states:

State	Meaning
Set up project	No Task IDs have been entered yet.
In progress	Work is recorded and no blocking summary signal forces a Not ready state, but the plan or validation record is not yet complete.
Not ready	At least one blocker signal remains in tasks, residual risk, validation, redirects, or launch decisions.
Ready for review	Tasks are complete, validation rows have terminal results, and the blocker summary is clear. This means the project is ready for a human review, not automatically approved for launch.

Ready for review is not launch approval

A completed task plan and clean summary cannot prove that the migrated result is acceptable or that the target store is operationally ready. Use the applicable validation pages and Define Sign-off Criteria before recording approval.

Use the Overview during project reviews

1. Update the As of Date and Project Status. Make the summary reflect the review you are about to perform.
2. Scan the blocker indicators. Open the corresponding sheet for every non-zero blocker or failure signal.
3. Review readiness trends, not only totals. Confirm whether risks are reducing, failed validation items have corrective owners, and launch decisions are moving toward closure.
4. Confirm the next milestone. Update planned dates only when the team has agreed to the change and the dependencies are understood.
5. Record the actual decision in its working sheet. Do not use a summary cell as the approval record.

Next Steps

Build the accountable work sequence in Project Plan, then connect material uncertainty in Risk Register.