Microsoft will permanently pull the plug on Project Online on September 30, 2026. The cloud project management platform, which for years served as the backbone for portfolio and project management in industries ranging from construction to IT, is reaching its end of life. Organizations that still depend on its Project Web App environment now have just over two months to rescue their data, choose a successor, and implement a workable alternative.
The September 30 Deadline Is Firm—and It Only Applies to Project Online
The clock is ticking, but not for every product that carries the “Project” label. Microsoft’s retirement notice, first announced in September 2025, targets the legacy Project Online service—not the desktop client that millions still use, not Project Server Subscription Edition, and not the newer Planner-based tools. Project Online is the SharePoint Online–based platform that delivered portfolio and project management through Project Web App sites, integrated resource management, timesheets, and reporting.
Here is what the timeline looks like:
- September 2025 – Microsoft publicly announced the retirement of Project Online.
- October 1, 2025 – Sales of new Project Online–only subscriptions were halted.
- September 30, 2026 – The service will be turned off. After this date, customers will lose access to their Project Web App sites and all data within them, unless they have exported and archived it beforehand.
Crucially, other Microsoft project management offerings live on. Project desktop (the classic .mpp file application) will continue to work, and Project Server Subscription Edition remains available for on-premises or hybrid scenarios. Microsoft Planner—which absorbed the capabilities of the retired Project for the web in August 2025—is now Microsoft’s primary cloud-based project management solution, offering both basic task boards and premium plans with advanced scheduling features.
What Actually Retires: A Clearer Picture
Confusion has arisen because the Project brand covers multiple services. To be precise:
- Project Online (with Project Web App) retires September 30, 2026.
- Project for the web already retired on August 1, 2025, and its functionality was moved into Microsoft Planner’s premium plans.
- Project desktop (the standalone application included in many Microsoft 365 plans) is not being retired.
- Project Server Subscription Edition is not being retired.
So the disruption is concentrated on organizations running the cloud-based Project Online platform. If your firm uses Project desktop and saves .mpp files locally or on network shares, your primary scheduling tool is safe—but any integration that relies on Project Online, such as automatic syncing to a Project Web App site, will break when the service goes dark.
What the End of Project Online Means for You
The impact depends on how your teams work today.
For IT Administrators and Project Management Offices
If your organization has active Project Online subscriptions, you need to act immediately. The deadline is not about simply uninstalling software; it’s about migrating an entire business system. Your Project Web App environment likely includes:
- Active and inactive projects with complex dependencies
- Custom fields, enterprise resource pools, and views
- Timesheet configurations and approvals
- Power BI reports, Power Automate flows, and SharePoint sites tied to projects
- External user access for clients, subcontractors, or partners
All of this must be inventoried, exported, and carefully retargeted to a new platform. Microsoft provides export tools that generate user-content data and feature-specific JSON files, but a flat export does not constitute a turnkey migration. Workflows, reports, and custom configurations need manual validation and rebuilding.
For Project Managers and Schedulers
You will need to learn a new interface. Whether you move to Microsoft Planner premium, Project Server, or a third-party tool, your daily routine will change. The good news: modern cloud tools often offer more intuitive collaborative features, such as real-time co-authoring, mobile access, and visual roadmaps. The bad news: if your current processes rely on deeply customized Office 365 integrations or specialized scheduling logic, you will likely experience friction during the transition.
For Construction and Engineering Firms
The construction sector has a particularly high stake. Many contractors and engineering firms built their project controls around Project Online’s portfolio and resource capabilities. A recent industry warning suggested that Planner is too lightweight to replace it and that alternatives like Oracle Primavera P6 are antiquated. Reality is more nuanced.
Microsoft Planner premium—which inherited the engine of Project for the web—supports critical-path scheduling, baselines, advanced dependencies with lead/lag, resource assignments, and roadmaps. It can handle up to 3,000 tasks, 150 resources, and 2,000 successor links per project, according to Microsoft’s service descriptions. For many general contractors and mid-sized projects, this may suffice.
However, for complex civil or commercial programs that demand cost-loaded schedules, contractual reporting specifications, or integration with estimate and risk tools, Planner premium may fall short. In such cases, teams may need to consider Project Server Subscription Edition, a dedicated construction scheduling solution, or—yes—Oracle Primavera P6 if owner contract requirements demand it. The decision should be based on a real requirements assessment, not on a generic dismissal of any single tool.
How We Got Here: Microsoft’s Project Management Consolidation
The retirement of Project Online is the final act in a multi-year effort to unify Microsoft’s fragmented project management portfolio. The timeline of recent changes tells the story:
- 2016–2019 – Microsoft introduced Project for the web as a lighter, browser-based alternative, alongside the classic Project desktop and Project Online.
- 2023 – Microsoft began merging Planner, To Do, and Project for the web into a single Planner experience with basic (task boards) and premium (advanced project scheduling) tiers.
- August 1, 2025 – Project for the web was retired. Customers were migrated automatically to Planner premium plans, though some manual steps were required for licensing and customizations.
- September 2025 – Microsoft announced that Project Online would follow suit, with an end-of-life date 12 months later.
The motivation is clear: maintain a single, cloud-first project management platform (Planner) while continuing to offer an on-premises option (Project Server) for scenarios that demand it. Project Online, built on the older SharePoint framework, represented a legacy codebase and user experience that no longer fit the roadmap.
What to Do Now: A 6-Week Migration Playbook
The remaining time is tight but sufficient if you act methodically. Here is a practical checklist:
1. Inventory Everything
List every active Project Web App site, its projects, customizations, and integrations. Don’t overlook dormant projects that may still hold data needed for audits or historical reference.
2. Export and Preserve Data
Use Microsoft’s export utilities to download project data, including tasks, assignments, baselines, and custom fields. Also capture related assets: reports, dashboards, document libraries, and any external system links. Store these exports securely; you may need them for contractual or legal purposes years later.
3. Classify Projects by Complexity and Requirements
Group projects into categories:
- Simple task lists that can move to basic Planner boards
- Mid-complexity schedules that fit Planner premium
- High-complexity programs requiring Project Server or a specialized tool
This prevents a one-size-fits-all approach and identifies where extra licensing or training is needed.
4. Choose Your Target Platform(s)
Evaluate options against your classified requirements:
- Microsoft Planner (premium) for collaborative, cloud-based project scheduling with moderate complexity.
- Project Server Subscription Edition for on-premises control, advanced portfolio analysis, and strict compliance needs.
- Third-party construction or engineering tools if contractual specs mandate a specific scheduling engine.
Don’t trust marketing claims—test with real project data. Your chosen platform should be able to open, interpret, and continue the logic of your exported schedules.
5. Pilot with Live Projects
Run a representative pilot, not just a clean demo project. Involve actual project managers and team members. Validate that critical features—dependencies, resource leveling, reporting—work as expected. Surface integration issues early.
6. Migrate in Phases
Roll out the new platform group by group. Start with less critical projects, then progressively move mission-critical work. This reduces risk and gives users time to adapt.
7. Plan for Long-Term Archive Access
Some completed projects may never need to be actively managed again but must remain accessible for claims, warranties, or owner audits. Decide how you will store and retrieve these archives—perhaps as read-only MPP files, PDFs, or JSON exports—and ensure access controls are documented.
Outlook: Beyond the Deadline
September 30, 2026, will mark the end of Project Online, but it also accelerates a larger shift toward collaborative, connected project management. Microsoft is investing heavily in Planner, with Copilot and a new Project Manager agent that promises to automate status updates and resource recommendations. Meanwhile, the construction and engineering sectors are witnessing a wave of modern scheduling tools that emphasize field participation and visual planning.
For organizations that prepare now, this forced migration is a chance to modernize workflows and retire technical debt along with the service. For those that delay, the shutdown could mean scrambling to recover data from a decommissioned environment—with no lifeline from Microsoft to help.