A practical sequence for moving off Project Online without rebuilding your PMO from scratch or discovering the gaps after go-live.
Most Project Online migrations fail the same way: they treat it as a data-export exercise. Move the schedules, close the ticket, deal with the governance layer “later.” Later usually means after someone’s already imported the biggest programme and hit the task cap.
Here’s a sequence that avoids that.
Phase 1: Assess
Before touching a single project, map what you actually have:
- Every custom field in use, and which ones are load-bearing for reporting or governance, this matters most if you’re headed for vanilla Planner, where the field limit is what typically triggers a Power Apps extension
- Every dependency type across your live schedules, some users report Planner Premium supports Finish-to-Start only, so this is worth confirming against your own tenant before you plan around it
- Your current resourcing model, is it project-level or portfolio-level?
- Every approval workflow and stage-gate currently running through SharePoint
Score your exposure against the PPM Gap (see the previous article in this series), this tells you how much governance rebuild you’re actually facing, before you commit to a timeline.
Phase 2: Protect
Export and back up everything, schedules, custom field configurations, historical reporting data well ahead of the retirement date. Don’t wait for the deadline to force this; the recommended export window closes well before September 30, and post-retirement access is short and read-only.
Pilot the migration on one real programme, not a test project. This is where the task cap, field limits, and dependency flattening show up, better to find them on one programme than your whole portfolio.
Phase 3: Extend
This is where the Governance layer gets rebuilt deliberately, not reactively:
- Cross-portfolio resource pool and capacity visibility restored on the same Microsoft 365 tenant
- Portfolio and programme rollups with financials, not just individual plans
- Custom field and dependency logic extended beyond Planner Premium’s native limits
- Enterprise Power BI reporting reconnected
Built on Power Platform, this stays inside your existing Microsoft 365 environment and licensing, no separate platform, no separate data residency conversation.
Phase 4: Govern
Rebuild the process layer, not just the data layer:
- Stage-gate approvals and demand intake, automated through Power Automate
- Portfolio prioritisation and governance reporting restored for leadership
- A support model so the PMO isn’t relying on tribal knowledge to keep it running
Why sequence matters
Organisations that skip straight to Phase 2 export and migrate, end up doing Phase 3 and 4 anyway, just later, under pressure, after the gaps have already caused a visible failure (a dropped task list in front of a steering committee is a bad way to discover the cap). Doing the assessment first means the governance rebuild is planned, not reactive.
Where you are in this process determines what you need next, a straightforward migration, a governed extension, or a full PMO rebuild. If you’re not sure which, the PPM Gap Assessment takes about ten minutes and will tell you.
Sources: the ~3,000-task cap on import is based on our own direct experience with an MSP schedule imported into Project for the Web (Planner Premium Plan 3/5’s underlying engine). The custom field ceiling applies to vanilla Planner. The Finish-to-Start-only dependency limitation is reported by some users and not independently confirmed across all configurations. Retirement dates and Microsoft’s official replacement guidance are per Microsoft’s Project Online retirement announcement.
