Microsoft Retirements 2026: Every Sunset That Affects PMOs
Four Microsoft retirements with primary-source-confirmed dates land in 2026, each one a separate cut to the legacy PMO stack. This page lists each, what it changes, who's affected, and the honest migration path. The headline event is Microsoft Project Online, retiring . The two July events end the on-premises Microsoft PM stack on the same day, and the April event has already removed SharePoint 2013 workflows from production.
until Project Online retirement
2026 retirement timeline
Four PMO-relevant Microsoft retirements with confirmed dates, ordered chronologically. The Project Online retirement is the load-bearing event. The two July 14 events (SharePoint Server 2016 + Project Server 2019) end the on-premises Microsoft PM stack in one operations window. The April event has already removed the SharePoint 2013 workflow runtime that many PWA deployments depended on.
| Date | Product | What it means |
|---|---|---|
| SharePoint 2013 workflows | Jump to details → | |
| SharePoint Server 2016 | Jump to details → | |
| Microsoft Project Server 2019 | Jump to details → | |
| Microsoft Project Online | Jump to details → |
Dates sourced from Microsoft's published lifecycle policies. See the Project Online service description for the canonical statement on the September 30 deadline.
Why these retirements matter
The 2026 retirement set is structurally different from the routine end-of-life announcements Microsoft has shipped over the past decade. Three reasons it deserves dedicated planning rather than a normal-quarter migration response:
First, the headline product has no in-place upgrade path. Project Online customers cannot upgrade their existing tenant to Planner Premium; the underlying data models (SharePoint-based vs Dataverse-based) are different enough that a managed upgrade isn't available. Every Project Online customer picks a target platform whether they want to or not, which makes the migration decision strategic rather than tactical.
Second, the successor's PMO depth is materially lower. Planner Premium is positioned as a PM tool but the design centre is task management with project veneer. PMOs that actually used Project Online's depth — enterprise resource pool, formula-driven custom fields, costed timesheets, multi- project capacity views — will find none of those at full depth in the successor. That forces a genuine evaluation of third-party platforms rather than a default "stay with Microsoft" decision.
Third, the dependent surface is broader than the product itself. Project Online has been a PMO data substrate for over a decade. Power BI dashboards, Power Automate flows, custom .NET integrations, Excel workbooks with OData connections, SharePoint Designer workflows — every one of these breaks at retirement. Inventorying and rebuilding those is usually a larger budget item than the seat-cost migration itself. A PMO that hasn't run that inventory yet is already late.
Per-event details
Each retirement below: what happens technically, who's affected, and the honest migration path. Each card links to the canonical companion blog post and the relevant pillar guide so you can go deeper without leaving the migration story.
Microsoft Project Online
What happens
Project Web App (PWA) sites stop accepting requests. The OData reporting endpoint returns 410 Gone. The Project Server SOAP API is decommissioned. Custom fields, formulas, timesheet history, and Enterprise Resource Pool data become unreachable from the live tenant. SharePoint document libraries inside PWA enter a read-only window before being deleted on December 31, 2026.
Who's affected
Every PMO running Project Online today. Microsoft has confirmed there is no in-place upgrade path, every customer must migrate to a successor platform. Heaviest impact: PMOs with multi-project portfolios, formal governance pipelines, costed timesheets driving billing, or Power BI dashboards built against the OData feed.
Migration path
Three honest options: Microsoft Planner Premium (the rebranded Project for the Web) for light teams, Onplana or another modern PM platform for PMOs that need scheduling + governance depth, custom build for engineering-heavy organisations with idiosyncratic needs. The Complete Migration Guide breaks down each path with cost ranges.
Microsoft Project Server 2019
What happens
On-premises Project Server 2019 reaches end of extended support. Microsoft stops shipping security updates, bug fixes, and compatibility patches. No Project Server 2026 or 2029 successor has been announced, the on-premises Project Server product line ends with the 2019 release. The date lines up with SharePoint Server 2016 EOL because Project Server 2019 runs on top of it, the two products effectively share a lifecycle.
Who's affected
Government, defence, healthcare, financial-services PMOs running Project Server 2019 on-premises for data-residency or sovereignty reasons. Combined with the cloud Project Online retirement two-and-a-half months later, July 14 is when the on-premises Microsoft PM stack runs out of vendor support.
Migration path
Microsoft's recommended upgrade is to Project Server Subscription Edition (SE), the supported subscription-licensed on-prem successor, or to Project 2024 LTSC Professional / Project 2024 Professional for single-user (non-PWA) scenarios. For sovereignty-required workloads that can't move to Microsoft's cloud, a self-hosted third-party PM platform is the alternative, Onplana ships a self-hosted option on Enterprise+ plans.
Consolidated migration paths
Across the four retirements, the migration options collapse to four patterns. Most PMOs end up picking one for their flagship Project Online migration and applying the same target to the smaller adjacent events.
Microsoft's successor (Planner Premium / Project for the Web)
Fits if your PMO uses light task management and you're committed to staying within Microsoft 365 licensing. Gaps to verify before committing: enterprise resource pool, costed timesheets, formal governance, deep custom fields. The Onplana vs Microsoft Planner comparison covers each gap concretely.
Onplana
Fits PMOs that need scheduling depth, enterprise resource pool, costed timesheets, AI risk detection, and formal governance preserved across the migration. Native .mpp / MSPDI import preserves the dependency graph and resource assignments 1:1. Free plan available. See the Microsoft Project alternative page for the full positioning.
Third-party PPM (Smartsheet, Workfront, etc.)
Fits if you already have a relationship with the vendor or a specific feature requirement their tool fits. Watch the all-in TCO — many third-party PPMs price the resource-management module, portfolio analytics, and timesheets as separate SKUs.
Custom build / open-source stack
Fits engineering-heavy organisations with idiosyncratic needs. 12–18 month build, 1–2 FTEs to maintain. Treat as becoming a PM software vendor in your cost model.
For the full vendor-neutral playbook (timeline, the five paths above with cost ranges, pre-migration checklist, validation), see the Project Online Migration Complete Guide. For deadline-bounded data-export tactics specifically, see the data export deadline guide. For the resource-model migration in detail, see resource capacity planning after Project Online.
Start with the free tools
Three free, no-signup tools to ground your 2026 retirement planning in real data rather than vendor talking points.
Schedule Health Check
Upload a .mpp file, get a 7-point audit of critical-path bottlenecks, resource overallocation, and dependency cycles. No signup.
Migration Cost Calculator
3-year migration cost estimate across six categories. Calibrated by org band. Output in a format you can drop into a CFO business case.
Inventory Checklist
35-item pre-migration inventory for Project Online tenants. Captures the downstream surface most teams underestimate.
Frequently asked questions
The questions PMOs ask most often about the 2026 retirement set. Full FAQPage schema is embedded so these surface in Google's "People Also Ask" feature.
What's the biggest Microsoft retirement affecting PMOs in 2026?
Microsoft Project Online, retiring September 30, 2026. Every other 2026 retirement in the PMO space is secondary by impact — Project Online has the largest installed base, the most-coupled downstream systems (Power BI dashboards, Power Automate flows, custom .NET integrations), and the fewest like-for-like replacements. The complete migration guide breaks the Project Online deadline down by milestone.
Will Microsoft extend the Project Online deadline?
No. Microsoft has stated publicly and repeatedly that the September 30, 2026 retirement date will not be extended. Every signal points the same direction: Microsoft has already announced the successor product (Planner Premium), the engineering organisation is allocated to it, and there's no business case for sustaining the legacy stack past the announced date. Plan as though the deadline is firm.
Is Planner Premium a real replacement for Project Online?
For light task management with small teams, yes. For PMO-grade work — multi-project portfolios, enterprise resource pools, costed timesheets, formal governance, deep custom-field engines — Planner Premium is materially weaker than Project Online was. The platform-by-platform comparison covers the specific gaps. PMOs that ran Project Online in earnest typically need a peer-class platform like Onplana, not a step-down.
How early should we start the Project Online migration?
Six to ten weeks of focused effort for a 50–200 project portfolio. Larger portfolios or multi-PWA deployments stretch to three or four months. Backwards-plan from a target cutover of August 15, 2026 (six weeks before the September 30 deadline) so you have parallel-operation runway. Anything later trades risk for schedule. The 90-day plan covers the typical timeline.
What happens to our Power BI dashboards built against Project Online?
They break at retirement. Power BI dashboards that read the Project Online OData feed will return errors the moment the feed goes offline; semantic models built on the Reporting Database stop refreshing. Plan a parallel rebuild against your target platform's API during the migration. A typical complex dashboard takes 3–5 days of senior BI analyst time; multiply by your dashboard count.
Can we keep using Project Server on-premises?
For a few more weeks, yes, but the runway ends July 14, 2026. Project Server 2019 extended support ends that day, the SharePoint Server 2016 underlay it runs on ends the same day, and Microsoft has not announced a Project Server successor after 2019. Two paths from there: upgrade to Project Server Subscription Edition + SharePoint Server SE (Microsoft's supported on-prem path) and continue running Project Server, or migrate off Microsoft's PM line entirely. Regulated PMOs with sovereignty requirements increasingly evaluate self-hosted third-party platforms, Onplana ships a self-hosted Enterprise+ option.
What about Microsoft To Do, OneNote, and the other adjacent productivity tools?
No major sunsets announced for To Do, OneNote, or Loop in 2026. The four primary-source-confirmed 2026 events are PM-stack-specific: SharePoint 2013 workflows (April 2), Project Server 2019 and SharePoint Server 2016 (both July 14), Project Online (September 30). The current evidence is that Microsoft is consolidating PM tooling under the Planner umbrella while leaving general productivity tools on their existing trajectories.
How do we know which Microsoft integrations our PMO depends on?
Run a 30-day audit before the deadline: tap your Project Online audit log and record every external system that hits OData, the Project Server SOAP API, or the SharePoint REST API for the PWA site. Anything in that log is a downstream consumer that needs migration planning. The list is almost always longer than what your team thought existed — SharePoint Designer workflows from years ago, Excel workbooks with live OData feeds owned by finance, third-party connectors set up via Zapier.
Will Microsoft provide a managed export tool?
No managed export service has been announced. The official path is for tenant admins to use existing OData APIs, PowerShell / CSOM, and SharePoint export tools to pull their own data before the cutoff. Treat the responsibility for export as yours, not Microsoft's. The data-export deadline guide covers the format-by-format export procedure.
Where should we start if we're just learning about this?
Start with the complete migration guide (sections on timeline + 5 paths + costs). Then run the schedule health check on a representative project to see how clean your current data is. Then run the migration cost calculator for a 3-year budget number. That's the typical first-meeting sequence — informational depth → data quality → budget — and it surfaces the right next steps without committing to a platform.
The deadline is real. Plan accordingly.
September 30, 2026 is not extending. Onplana ships native .mpp import, full critical path, AI risk detection, formal governance, and self-hosted deployment for PMOs that need to migrate without losing depth. Free plan covers full Gantt; paid plans start at $7/seat/month.