Microsoft already retired the Project tool most construction firms think is dying this fall. It happened quietly in August 2025, folded into Planner with barely a ripple outside IT departments. The deadline actually closing in on general contractors this September belongs to a different, older, far more deeply wired system called Project Online, and Microsoft has built no migration tool to catch what falls out of it.
Trade coverage warning contractors about a looming Microsoft Project shutdown often points at the wrong product, or blends the two together. That confusion matters, because the real cutover on September 30, 2026 does not just retire an app. It shuts down the SharePoint-based enterprise backbone that many general contractors use to run resource-loaded, multi-year schedules across an entire project portfolio, with no read-only grace period and no built-in way to move the data out.
Microsoft Already Killed the Retirement Everyone Is Bracing For
Two different Microsoft products carry the “Project” name, and they retire on two different dates. Project for the web, the lightweight, Power Platform-based tool, along with the Project and Roadmap apps inside Teams, went first. Microsoft’s own transition notice confirmed that users would be redirected automatically to Planner starting in August 2025, with existing plans carried over and no admin action required. That happened more than a year before this fall’s headline deadline, and it is largely done.
What is actually ending on September 30, 2026 is Project Online, the older SharePoint-based enterprise platform built around Project Web App sites, resource pools, and portfolio reporting. It served as the backbone for general contractors running several job sites off one shared portfolio. Microsoft stopped shipping new features to it back in 2023 and made the retirement official afterward.
- April 2023: Microsoft stops adding new features to Project Online, shifting development into Project for the web and Planner instead.
- August 2025: Project for the web and the Project and Roadmap apps in Teams retire, with users redirected into Planner.
- October 1, 2025: Microsoft stops selling new Project Online-only subscriptions.
- April 1, 2026: Creation of new Project Web App sites is blocked for existing customers.
- April 2, 2026: SharePoint 2013 workflows running Project Online’s stage-gate approvals and status reporting stop working, six months ahead of the main shutdown.
- September 30, 2026: Project Online shuts down completely, with access to the service and its data ending and no grace period.
Desktop Project, the classic .mpp file application many schedulers still open every morning, is not part of either retirement. Neither is Project Server Subscription Edition, the on-premises alternative. A contractor who schedules entirely in the desktop app and emails .mpp files to the field has nothing to migrate. The disruption is concentrated on the portfolio layer, the part large general contractors actually rely on to see several projects at once.
Ten Weeks Left, Twenty Weeks of Work
Count from today and the math is not friendly. September 30 is roughly ten weeks away. Velosio, a Microsoft solutions provider that runs these migrations for enterprise clients, estimates a careful transition can take up to 20 weeks from inventory to cutover. A firm starting from a blank sheet this month is already behind its own runway.
Microsoft gives contractors two ways out the door: a PowerShell export script and a direct pull from the Project Online OData feed. Neither rebuilds a working schedule somewhere else. They just get the raw material out before the door locks. Project controls teams still need to decide, before that date, exactly what to preserve.
- Schedules and baselines, exported project by project through the desktop client or the OData feed, including every stored baseline used to measure delay, not just the current view.
- Resource pools and cost loading, since Project Online’s enterprise resource model rarely maps cleanly onto lighter successor tools.
- Timesheets and custom enterprise fields, the data most successor platforms drop by default during a straight file export.
- Linked SharePoint content, including documents, risk logs, and approval records tied to each project site, which sit outside the Project Online export entirely and need their own separate audit.
Miss that last item and a firm can technically finish its export, tick every box, and still end up with folders of files nobody can reassemble into a defensible project history.
The SharePoint Machinery Behind the Schedule
The two retirements are not the same size problem, and treating them the same way is the first mistake firms make. Project for the web was closer to a modern task board bolted onto a canvas. Project Online carries the deeper machinery construction scheduling actually depends on, including Critical Path Method (CPM) logic, the discipline of tracking which delayed task pushes the whole project’s finish date, layered with resource pools, cost accounts, and multi-year portfolio reporting.
| Attribute | Project for the Web + Roadmap | Project Online |
|---|---|---|
| Retirement date | August 2025 (already complete) | September 30, 2026 |
| Built on | Microsoft Power Platform, a lighter cloud service | SharePoint Online plus a Microsoft-hosted database behind Project Web App |
| Typical construction use | Single-project task tracking for smaller teams | Multi-project portfolios, resource pools, timesheets, stage-gate approvals |
| Migration path Microsoft offers | Automatic redirect into Planner, no admin action needed | A PowerShell export script and an OData feed only, no migration tool |
| What survives untouched | Not applicable; the product itself is gone | Desktop Project and Project Server Subscription Edition, both unaffected |
That resource pool row is where most general contractors (GCs) will feel it first. Planner Premium, Microsoft’s recommended landing spot, was not built to hold an enterprise resource model with named crews, equipment calendars, and cost accounts shared across a dozen active jobs. Firms that try to force that structure into Planner often end up rebuilding pieces of it themselves in Power Apps or Power BI, a cost that shows up as custom development time rather than a licensing line.
Federal Contracts Still Mandate Primavera P6
The choice between Planner, Primavera P6, and a newer visual scheduling platform sounds like a matter of preference. For a large slice of the industry, it is not a choice at all.
The Army Corps of Engineers requires schedule submissions in Primavera P6 format for schedule submissions on most of its capital construction work, spelled out in its own master specification for network analysis schedules. That document sets exact rules for activity coding, calendars, and the data exchange format used to feed schedule updates into the government’s own project system. The Naval Facilities Engineering Systems Command and several state departments of transportation write similar requirements directly into their contracts, and missing them can mean a rejected schedule and a delayed payment application.
A general contractor that wins a federal courthouse job and a private hospital renovation in the same year may end up running Primavera P6 on one and something entirely different on the other, by contract rather than by choice. That reality complicates any tidy, pick-one-platform advice, including advice aimed at firms fleeing Microsoft Project.
Does a Missing Schedule Become a Legal Problem?
Yes. Construction delay claims lean heavily on contemporaneous schedule updates, and courts and arbitrators routinely expect a documented, regularly updated critical path record before they will credit a claim for extra time or money. A gap in that record, created by a botched software migration, can weaken a case years after the work is finished.
Forensic schedule analysis, the practice of reconstructing a project’s timeline from its CPM updates and supporting records, has become routine in construction litigation. Legal analysis on the subject notes that the use of retrospective CPM techniques in contract disputes has grown common over roughly the past four decades, showing up everywhere from federal contract appeals boards to private arbitration. Attorneys who litigate scheduling disputes make the same point from the other direction, noting that well-maintained schedules often provide strong evidence in delay litigation, while thin or inconsistent ones invite challenge.
A live schedule sitting in a system about to go dark, with no clean export of its baseline history, is exactly the kind of gap a defense attorney would go looking for on the other side of a claim.
A Software Market Racing to Absorb the Fallout
Every vendor in construction technology can see the same calendar Microsoft published, and it doubles as a sales opportunity. The construction management software market is valued at an estimated 11.58 billion dollars in 2026 and is projected to reach $17.81 billion by 2031, and already counts Microsoft itself among its major vendors, alongside Oracle, Bentley Systems, Procore Technologies, and Trimble. Project management and scheduling make up the single largest slice of that spending.
A separate forecast puts the broader construction software market at 11.78 billion dollars in 2026, set to climb toward $24.72 billion by 2034, with cloud-based tools growing fastest as firms move off installed, on-premises systems. Oracle, Procore, Trimble, Autodesk, and Bentley show up on both vendor lists, and all five have spent the past year courting exactly the customers Microsoft is displacing.
That broader shakeout will not change the arithmetic facing a scheduler at a mid-size general contractor this September. The market will keep evolving for years. The export deadline will not wait for it.
Frequently Asked Questions
What Should Construction Firms Do With Ten Weeks Left?
Project controls teams should export active and recently closed job baselines first, especially on any project with an open or possible delay claim, before tackling routine portfolio cleanup. A detailed migration playbook built by consulting teams that run these projects breaks the work into roughly three weeks of inventory, five weeks choosing where each data type lands, six weeks of export and staging, and four weeks of parallel testing before cutover, a timeline that leaves almost no room for firms only starting now.
What Happens to My Data When Project Online Shuts Down?
Access to Project Web App sites, resource pools, and reporting data ends on the retirement date with no grace period. Firms must export schedules through the desktop client or Microsoft’s OData feed, and separately audit linked SharePoint content such as documents and risk logs, before September 30, 2026.
Do Construction Firms Have to Use Primavera P6 Instead?
Only when a contract requires it. The Army Corps of Engineers, the Naval Facilities Engineering Systems Command, and several state transportation departments write Primavera P6 formatting directly into their specifications for public work. Private commercial and residential projects carry no such requirement.
How Long Does a Project Online Migration Actually Take?
Guidance from firms that run these migrations puts a careful, fully validated transition at up to 20 weeks, covering inventory, platform selection, export, and a parallel run before cutover. Starting later than early summer 2026 leaves little room for that full process before the deadline.
Will Microsoft Planner Handle Enterprise Construction Scheduling?
Planner now includes the premium scheduling features that used to live in Project for the web, but Microsoft has said portfolio-level tools are still arriving over time rather than fully built. Firms running resource-loaded schedules across many active jobs may find real gaps until those features land.
