Migration Go/No-Go Criteria: Six Checks Before Cutover

The go/no-go meeting for a Project Online cutover routinely gets skipped, or held as a status update where nobody actually votes no. That happens because most PMOs never wrote down what a "no" requires, so the room has nothing to test against except gut feel and whatever the sponsor's calendar allows, even with Microsoft's September 30, 2026 retirement date fixed on the calendar behind them.

The direct answer: a real migration go/no-go decision runs against six checks: export verified, schedule math matches, permissions mapped, reporting rebuilt, support staffed, and rollback still possible. Score each one pass, amber, or fail against a written threshold. Two ambers do not block a go if neither touches export integrity or the rollback path; one fail on either of those two checks does, regardless of how green everything else looks.

The Six Checks That Gate a Real Go/No-Go Decision

Each check needs a threshold decided before the meeting starts, not argued about during it. Export verified maps directly onto the data extraction window: treat that check as passed only once every project, resource pool, and custom field has actually cleared it, not once the export job has merely finished running. This is the scorecard we use across cutover reviews:

Check	What it verifies	Pass threshold
Export verified	Every active project, resource pool, and custom field is out of Project Online and validated	100% of active projects re-imported and diffed against the source export, zero unresolved discrepancies
Schedule math matches	The destination recalculates the same critical path and finish dates as the source	Finish dates match within 1 day on every project; critical path sequence unchanged on tier-1 projects
Permissions mapped	Every user and role has working access in the destination	100% of internal users verified by spot-check login; guest access confirmed for anyone who needs it day one
Reporting rebuilt	The dashboards leadership actually checks are live	The 2-3 reports reviewed weekly are functional and validated against last week's Project Online numbers
Support staffed	Someone is on call to fix problems during and after cutover	Help desk trained, runbook published, on-call coverage scheduled through week one
Rollback still possible	You can still undo the cutover if it goes wrong	Source tenant remains read-accessible, export data retained, rollback procedure tested at least once

How Two Ambers Still Add Up to a Go

Take a real scorecard: export verified passes clean, schedule math matches, reporting is rebuilt for the reports that matter, and rollback is tested. Permissions comes back amber, guest access for three external consultants is still pending IT approval, expected within two days. Support staffing also comes back amber, the cutover weekend is fully covered but week-one on-call is tentative pending a hire's start date. Neither amber touches export integrity or the ability to undo the move. Both have a named owner and a date. That scorecard is a go, with the two ambers tracked as open items on the post-cutover punch list, not treated as blockers.

Compare that with a scorecard where schedule math fails on a single tier-1 project, the destination's critical path drops two weeks that Project Online's forward pass accounts for. Every other check is green. That is still a no-go, because a critical path error on a tier-1 project is exactly the kind of silent data problem the post-cutover validation audit exists to catch, and finding it after go-live costs far more than a delayed cutover date.

The diagram below shows how the six checks feed the final call.

Why This Meeting Gets Skipped, and What Skipping Costs

The go/no-go meeting gets replaced by a status update for a specific reason: it forces someone to say no in front of a sponsor who has already told the business a date. Without a written scorecard, that pressure wins almost every time, and the team cuts over on schedule instead of on readiness. The cost shows up later, not at the meeting. A permissions gap that would have taken an amber and a two-day fix instead becomes a locked-out finance director on day one. A schedule math error that would have failed the check instead becomes a wrong delivery date in a board report three weeks after go-live, discovered only because a customer asked why a milestone slipped.

Who Should Own the Call

The migration lead makes the go/no-go call, but the scorecard needs a second reader before the meeting, usually the PMO director or the executive sponsor, who signs off on the thresholds in advance rather than negotiating them in the room. That separation matters because the migration lead is the person under the most pressure to say yes; a scorecard only one person can see is a decision only one person can be held to. If the sponsor and the migration lead disagree on a threshold call, that is exactly the disagreement the meeting exists to surface before cutover weekend, not during it.

What a No-Go Actually Triggers

A no-go is not a failure state, it is the scorecard doing its job. The rollback decision framework covers what happens next in detail, but the short version runs three steps:

1. Reschedule the cutover window to a specific new date, not an open-ended "when ready."
2. Assign a named owner and a fixed re-check date to every amber and fail on the scorecard.
3. Re-run all six checks against the new date rather than assuming they will pass themselves the second time.

Teams that treat a no-go as a scheduling inconvenience instead of a real signal tend to cut over anyway on the rescheduled date with the same open items, which defeats the purpose of having run the checks at all.

Before the scorecard meeting, run the free Migration Preview tool against your Project Online tenant to see what your Project Online migration will actually look like on the other side, project count, resource pool size, and custom fields included, so the export-verified and schedule-math checks have real numbers to test against instead of estimates.

Preview your migration before the go/no-go meeting See what your Project Online migration actually looks like, project by project, before you have to score it. No signup required. → Run the Migration Preview

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.