Project Online retires on September 30, 2026, and for construction and infrastructure teams, the exposure is larger than a tool swap. Over a decade, Project Online became the system of record for cost-loaded master schedules, contractual reporting, subcontractor coordination, and portfolio governance, the exact project controls that keep bids accurate and capital programs on budget. Lose those controls without a plan, and the estimating and allocation errors PMOs spent years eliminating come straight back.
The generic migration advice treats this as a like-for-like tool swap. For capital-intensive portfolios, the harder question is which controls survive the move and which quietly break.
What is happening to Microsoft Project Online?
Microsoft Project Online retires on September 30, 2026. After that date, Project Web App (PWA) sites and the data inside them will no longer be accessible.
The timeline has firm markers. According to ​Microsoft’s official lifecycle documentation, Project Online retires on September 30, 2026, after which the service and its data will no longer be accessible. Sales of Project Online-only plans to new customers ended October 1, 2025, and existing customers cannot create new PWA sites as of April 1, 2026. Microsoft is redirecting investment toward Planner and Copilot-based work management, citing the legacy SharePoint architecture that Project Online was built on. For construction teams, the key point is that Planner is not a like-for-like replacement, and the parts of your process that depend on Project Online may extend well beyond scheduling.
Why construction portfolios face a bigger transition than most
Construction and infrastructure portfolios carry requirements that general project management rarely touches. That is why a migration plan written for a marketing PMO does not fit a capital program.
Consider what Project Online typically anchors in a construction organization. The platform holds cost-loaded schedules where budget and timeline are linked at the task level, supports contractual reporting that owners and regulators require, manages complex resource structures spanning employees, contractors, and subcontractors, and often underpins formal change control, progress measurement, and portfolio governance. Rebuilding these on a new platform requires the ​enterprise architecture and data integration discipline that connects scheduling, cost, and reporting into one coherent system.
What actually changes for capital project teams
The retirement touches several areas that construction portfolios depend on, and each one needs deliberate attention.
Master schedules and cost-loaded plans
Project Online could manage massive schedules with thousands of tasks, deep work breakdown structures, and multi-level dependencies. Lightweight replacements are built for task coordination, not this scale. Capital programs that lose cost-loaded scheduling fall back to spreadsheets, and the estimating and allocation errors that PMOs worked years to eliminate come right back.
Contractual and regulatory reporting
Infrastructure portfolios frequently feed funding decisions and regulatory reporting from Project Online data. Any replacement has to preserve the reporting structures that owners, auditors, and regulators expect, or the organization risks compliance gaps during the transition. Connecting project data to ​analytics and reporting that matches contractual formats is essential, not optional.
Subcontractor and resource coordination
Project Online could automatically rebalance schedules when resources were overallocated. Without that capability, resource managers revert to manual coordination across crews and subcontractors, exactly the fragmentation that portfolio-level ​resource capacity planning exists to prevent.
Historical project data and sharepoint content
Construction Project Online environments often connect to SharePoint project sites, document workflows, and approval chains. After retirement, PWA data will not be accessible, so historical schedules, bid records, and project documentation must be exported and preserved before the deadline using disciplined ​data migration practices.
How construction and infrastructure teams should plan the move
Large capital organizations rarely have the luxury of a single big-bang change. A phased approach lowers delivery risk and lets the PMO show incremental wins ahead of the deadline.
Start by stabilizing the critical portfolios first: the regulatory, board-visible, and revenue-critical programs that carry the most exposure. Move those into the new platform before anything else. Next, optimize by redesigning intake, governance, resource, and financial processes rather than simply replicating old workflows. Rationalize the custom reports and workflows that accumulated over a decade. Finally, scale the model across business units and integrate the new platform with ERP, financial, and asset management systems so project data flows consistently. Treating the retirement as a chance to modernize the operating model, not just the tool, is where forward-looking construction PMOs find real value in ​work and operations management.
Turn a forced deadline into a stronger project controls foundation
The Project Online retirement is a hard deadline, but for construction and infrastructure teams it is also a rare opportunity to rebuild project controls on a modern foundation. Handled early and deliberately, this transition protects your master schedules, preserves your historical data, and strengthens the cost and governance controls that keep capital programs on budget. Handled late, it becomes a scramble to save data before access disappears.
If your construction or infrastructure organization is planning its move off Project Online, ​connect with Advaiya’s project services team. With deep experience in construction, EPC, and infrastructure alongside OnePlan and Microsoft expertise, Advaiya helps capital-intensive teams preserve their project data and rebuild the project controls that complex portfolios depend on.
Frequently asked questions
Microsoft Project Online retires on September 30, 2026. After that date, Project Web App sites and the data stored in them become inaccessible. Sales to new customers ended October 1, 2025, and existing customers cannot create new PWA sites as of April 1, 2026.
Construction and infrastructure portfolios rely on cost-loaded schedules, contractual reporting, subcontractor coordination, and formal change control that lightweight replacements cannot support. Project Online often anchors portfolio governance, funding decisions, and regulatory reporting, so its retirement affects far more than scheduling.
Planner is built for lightweight task coordination, not portfolio governance, cost-loaded scheduling, or contractual reporting. Construction teams managing capital programs typically need deeper project controls than Planner provides, which is why many evaluate purpose-built PPM platforms designed for complex portfolios.
After September 30, 2026, Project Web App data and connected SharePoint content become inaccessible. Construction firms must export and preserve historical schedules, bid records, cost data, and project documentation before the deadline, or risk losing years of capital project history permanently.
Use a phased approach: stabilize critical regulatory and board-visible portfolios first, then optimize intake, governance, and financial processes, and finally scale across business units while integrating ERP and asset systems. Starting early avoids the risk and cost of a rushed final-quarter migration.
Yes. Handled as a modernization opportunity rather than a forced swap, the retirement lets construction teams rebuild project controls on a modern platform with better cost integration, resource management, portfolio visibility, and AI-enabled capabilities that the legacy architecture could not support.
