Microsoft Retirements 2026: Every Sunset That Affects PMOs
Three Microsoft retirements with primary-source-confirmed dates landed in 2026, each one a separate cut to the legacy PMO stack. This page lists each, what it changed, who it affected, and the honest migration path now. The two July events ended support for the on-premises Microsoft PM stack on the same day, and the April event removed SharePoint 2013 workflows from production.
2026 retirement timeline
Three PMO-relevant Microsoft retirements with confirmed dates, ordered chronologically. The two July 14 events (SharePoint Server 2016 + Project Server 2019) ended support for the on-premises Microsoft PM stack in one operations window, and the April event removed the SharePoint 2013 workflow runtime that many Project Server deployments depended on.
| Date | Product | What it means |
|---|---|---|
| SharePoint 2013 workflows | Jump to details → | |
| Microsoft Project Server 2019 | Jump to details → | |
| SharePoint Server 2016 | Jump to details → |
Dates sourced from Microsoft's published lifecycle policies.
Why these retirements matter
Three reasons the 2026 set still shapes what a PMO does next:
First, the on-premises line stops at Project Server 2019. Microsoft has not announced a successor after it. Staying on premises means moving to Project Server Subscription Edition; leaving means picking a new platform. Either way the decision is strategic rather than tactical.
Second, Microsoft's cloud direction is lighter. Microsoft is consolidating PM tooling under the Planner umbrella, and Planner Premium's design centre is task management with project veneer. Enterprise resource pool, formula-driven custom fields, costed timesheets and multi-project capacity views are not there at full depth. That forces a genuine evaluation of third-party platforms rather than a default "stay with Microsoft" decision.
Those gaps are worked through in full: the task ceiling, timesheets, stage gates, resource capacity, portfolio management, custom fields, reporting, and earned value, each with the Microsoft position checked and dated rather than asserted.
Third, the dependent surface is broader than the product itself. Power BI dashboards, Power Automate flows, custom .NET integrations, Excel workbooks with live data connections, SharePoint Designer workflows: every one built on the old stack needs a rebuild on the new one. Rebuilding those is usually a larger budget item than the seat-cost migration itself.
“Enterprise-Grade Project Management with a Modern AI-Powered Collaborative Edge”
It combines enterprise-grade project management features like Gantt charts, dependencies, and portfolio management with a modern AI-powered and collaborative experience. It feels like a strong modern alternative for organizations moving away from Microsoft Project.
Waheed H.
Manager · Small Business (50 or fewer employees)
Per-event details
Each retirement below: what happens technically, who's affected, and the honest migration path. Each card links to the relevant guide so you can go deeper without leaving the migration story.
Microsoft Project Server 2019
What happens
On-premises Project Server 2019 reached end of extended support on July 14, 2026. Microsoft stopped 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 lined up with SharePoint Server 2016 EOL because Project Server 2019 runs on top of it; the two products shared a lifecycle.
Who's affected
Government, defence, healthcare, financial-services PMOs running Project Server 2019 on-premises for data-residency or sovereignty reasons. July 14 was when the on-premises Microsoft PM stack ran 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 scenarios. For workloads whose data must stay in an environment you control, Onplana Enterprise+ is a dedicated deployment that Onplana runs in your own Azure subscription.
Consolidated migration paths
Across the three retirements, the migration options collapse to four patterns. Most PMOs pick one target for their Project Server migration and apply it to the smaller adjacent events.
Microsoft's cloud line (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. For the full Microsoft Project SKU map (Plans 1/3/5, Planner Premium, Desktop, Server SE, LTSC 2024) with decision tree + renaming history, see Microsoft Project licensing 2026.
Onplana
Fits PMOs that need scheduling depth, capacity across projects, costed timesheets, AI risk detection, and formal governance after the migration. Native .mpp / MSPDI import keeps the dependency graph, and assigns each task to the member whose email matches its resource; a resource with no matching member arrives unassigned and is listed for you to invite. Free plan available. See our case for Onplana for the full positioning, or the round-up of alternatives to Microsoft Project if you are still comparing the field rather than one product.
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 step-by-step move from Microsoft Project and Project Server files, see the migration guide. For the resource-model migration in detail, see resource capacity planning.
Start with the free tools
Four free, no-signup tools to plan the move in real data rather than vendor talking points.
Schedule Health Check
Upload a .mpp file, get an 8-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.
MS Project Migration Tool
Upload a .mpp or XML file and see what carries over to each destination, scored, before you move it. No signup.
PMO Maturity Assessment
15 questions across process, tooling, governance, risk and reporting. Worth doing before you choose a replacement, so you know which gaps it has to close.
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?
For on-premises PMOs, Project Server 2019 and the SharePoint Server 2016 it runs on, which both reached end of extended support on July 14, 2026. Microsoft has not announced a Project Server successor after 2019, so the supported on-premises path is Project Server Subscription Edition.
Is Microsoft Project discontinued?
No. Microsoft Project desktop is still shipping, still supported, and still opens .mpp files. Project Server 2019 reached end of extended support on July 14, 2026, and Project Server Subscription Edition remains the supported on-premises edition. If you need to open or edit .mpp files without a Project licence, Onplana Schedule is a free desktop app for Windows and Mac.
Is Planner Premium a real replacement for Project Server?
For light task management with small teams, yes. For PMO-grade work (multi-project portfolios, capacity across projects, costed timesheets, formal governance, deep custom-field engines) Planner Premium is materially weaker. The platform-by-platform comparison covers the specific gaps. PMOs that ran Project Server in earnest typically need a peer-class platform like Onplana, not a step-down.
Can we keep using Project Server on-premises?
Only on Project Server Subscription Edition. Project Server 2019 extended support ended on July 14, 2026, along with the SharePoint Server 2016 it runs on, 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 that need their data in their own environment can also use Onplana Enterprise+, a dedicated deployment that Onplana runs in their own Azure subscription.
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 three primary-source-confirmed 2026 events are PM-stack-specific: SharePoint 2013 workflows (April 2), Project Server 2019 and SharePoint Server 2016 (both July 14). The current evidence is that Microsoft is consolidating PM tooling under the Planner umbrella while leaving general productivity tools on their existing trajectories.
Where should we start if we're just learning about this?
Save a representative project from Project Server or Microsoft Project as a .mpp or Project XML file and run the Schedule Health Check on it to see how clean your data is. Then run the migration cost calculator for a 3-year budget number. That sequence (data quality, then budget) surfaces the right next steps without committing to a platform.
Which PMO are you?
The tool is the easy part. The practice is what moves.
Moving off Microsoft Project, what actually moves is a practice: demand intake, stage gates, resource capacity, baselines, earned value, and the audit trail behind them. The Onplana for PMOs page walks that practice end to end, by industry, with the plan tier for each step.
- Aerospace & defense
- Government & public sector
- Banking, financial services & insurance
- Energy & utilities
- Pharma & med-tech
- Healthcare & telecom IT
The support dates have passed. The move is yours to time.
Onplana imports .mpp and Project XML files from Microsoft Project and Project Server, with full critical path, AI risk detection, formal governance, and a dedicated deployment in your own Azure subscription for PMOs that need to move without losing depth. Free plan covers full Gantt; paid plans start at $12/seat/mo.
Would rather talk it through? Book a 30 minute migration consult with the founder. Bring a real schedule.
No Microsoft account needed, choose "Continue as guest".