Microsoft Project Online Retires September 30, 2026: Migration Guide

Microsoft Project Online will retire on September 30, 2026, leaving construction firms that use its Project Web App environment barely 10 weeks to choose a replacement, archive their data and test the workflows that keep bids, resource plans and master schedules moving. The deadline is real, but a newly circulated construction-industry warning gets a crucial part of the story wrong: Project for the web and the Project and Roadmap apps in Teams were retired on August 1, 2025, then folded into Microsoft Planner—not scheduled for a fall 2026 shutdown.
That distinction matters. The construction-focused article published by For Construction Pros frames the change as a forthcoming retirement of Microsoft Project broadly, and suggests Planner is inherently a lightweight task tool unable to support serious scheduling. Microsoft’s product documentation tells a more precise story. Project Online is the service ending this September; Project desktop, Project Server Subscription Edition and Planner remain available. Meanwhile, the former Project for the web capability set now lives inside Planner’s premium plans.
For IT teams supporting construction operations, this is not a semantic correction. It changes the inventory, the migration plan and the realistic set of options.

The September deadline belongs to Project Online​

Microsoft announced the Project Online retirement in September 2025, stopped selling Project Online-only SKUs to new customers on October 1, 2025, and has set September 30, 2026 as the service’s final day. Existing tenants can continue to use Project Online, its integrations and Project Web App sites until then, according to Microsoft’s Planner team and Lifecycle documentation.
Project Online is the older cloud portfolio-and-project-management platform built around SharePoint Online and Project Web App. It is not the same product as the Windows desktop client that many schedulers still call “Microsoft Project,” nor is it Project for the web.
That leaves three groups with very different immediate exposure:

• Firms using Project Online or Project Web App must plan for a September 30 service retirement and should export data well before the cutoff.
• Firms using Project for the web have already experienced the endpoint change; their plans should be accessed through Microsoft Planner, assuming licenses and tenant rollout are in order.
• Firms working primarily in Project desktop with local .mpp files are not facing a September 30 application shutdown, though they may lose their Project Online connection if that service is part of their process.

Microsoft specifically recommends that Project Online customers back up projects and data, then transition to Planner or Project Server Subscription Edition before the retirement date. Its export tooling can produce user-content data and feature-specific JSON files, but an export is not a turnkey migration. Customized workflows, reporting models, Project Web App configurations, Timesheet processes, enterprise resource fields and integrations need their own validation.

Planner Is Not the Basic Board the Argument Assumes​

The strongest claim in the construction article—that Planner cannot accommodate critical-path construction work—does not fit Microsoft’s current product lineup. It would have been more defensible if it referred only to the classic, basic Planner boards included with many Microsoft 365 subscriptions. But Microsoft has spent the past several years combining Planner, To Do and Project for the web into one Planner experience with both basic and premium plans.
Planner premium plans retain a number of capabilities inherited from Project for the web, including advanced dependencies with lead and lag, baselines, critical-path views, roadmaps, goals and resource-related functionality. Microsoft’s current service description also lists limits of up to 3,000 tasks, 150 resources and 2,000 successor links per project for the former Project for the web architecture.
None of that automatically makes Planner a drop-in replacement for every construction schedule. A high-complexity commercial or civil program may have established requirements around cost-loaded schedules, contractual reporting, specialized progress measurement, formal change control, external integrations or portfolio controls that extend well beyond Planner’s premium feature set. But the correct conclusion is that firms need a requirements test—not that Planner is categorically only a marketing or IT task board.
Microsoft positions Planner as the cloud-forward option, including its Copilot and Project Manager agent investments. That is vendor positioning, not evidence that every contractor should move. Construction organizations should verify whether the specific Planner features they need are available in their tenant, their license tier and their geographic cloud environment before declaring the platform suitable or unsuitable.

---

Primavera P6 Is Not a Universal “Step Backward”​

The article also presents Oracle Primavera P6 as an obsolete retreat that necessarily isolates field personnel. That is too broad. Primavera P6 remains deeply embedded in major construction, engineering, infrastructure and government project environments precisely because its scheduling, resource and portfolio functions can satisfy sophisticated owner and contract requirements.
Its complexity is real, as are the training and governance costs. A schedule maintained only by a planning department can indeed lag conditions on site, whether it runs in P6, Project Online, a desktop .mpp file or a new SaaS platform. But that is an operating-model failure, not a property unique to one legacy product.
The practical comparison should be more grounded. If a contractor is contractually required to submit P6 files, has an owner’s scheduling specification built around P6, or relies on features not available in Planner, replacing Project Online with P6—or maintaining P6 for specific work—may be the conservative and appropriate move. Conversely, a smaller general contractor may reasonably decide that a collaborative cloud platform with simpler field access outweighs the overhead of a heavyweight scheduling system.
The key is to separate a scheduling engine’s capabilities from the team’s ability to operate it. Modern interfaces and mobile updates can improve schedule participation, but they do not remove the need for disciplined logic, reliable actuals, schedule quality checks and accountable ownership.

The Migration Work Is Bigger Than Copying Project Files​

Project Online shops should treat this as a business-system retirement, not a software reinstall. In a construction environment, the real dependencies may include Power BI reports, Power Automate flows, SharePoint document sites, Teams channels, custom fields, timesheets, portfolio dashboards and project-specific reporting obligations.
The first task is identifying what is actually in use. It is common for a company to describe itself as a “Microsoft Project shop” while different teams use Project desktop, Project Online, Planner, Excel and contractor-provided P6 schedules simultaneously. Those systems have different risks and different retirement dates.
A useful transition sequence is straightforward:

• Inventory Project Online Project Web App sites, active projects, inactive historical projects, customizations, integrations, license assignments and external users.
• Preserve an export of both project data and the reports, documents and business rules needed to interpret it later.
• Classify schedules by complexity, contract obligation, sensitivity and the need for resource, cost or portfolio controls.
• Run representative pilot projects in the proposed replacement rather than testing only a clean sample schedule.
• Decide how legacy schedules will be retained for claims, audits, closeout and long-term reference after Project Online is unavailable.

For construction firms, the last point carries particular weight. A schedule may be operationally complete but still relevant to disputes, insurance, warranty work, owner reporting or delay analysis years later. Archive plans therefore need to cover readable schedule files, baselines, calendars, logic links, update histories, relevant source documents and access controls—not merely a PDF Gantt chart.

A Deadline, Not a Reason to Buy the First Replacement​

The approaching September 30 date creates legitimate urgency, but it does not validate the notion that contractors face only three stark choices: Planner, P6 or an unnamed “next-generation” visual scheduler. The For Construction Pros piece is published around Planera’s argument for modern collaborative scheduling, and its prescription naturally favors that product category.
There may be sound reasons to select a construction-specific cloud platform. Better field participation, subcontractor collaboration, look-ahead planning and accessible mobile workflows are credible goals. They should be judged through a pilot, commercial terms, data portability, security review, implementation support and the ability to meet schedule and contract requirements—not through an inflated reading of Microsoft’s retirement notices.
The immediate Microsoft news is narrower but more actionable: Project Online will disappear on September 30, 2026; Project itself is not being retired wholesale. Construction firms that still depend on Project Web App should use the remaining weeks to map their actual estate, protect their records and prove a replacement workflow against a live project before the service goes dark.

---

References​

1. Primary source: For Construction Pros
   Published: 2026-07-18T12:00:00+00:00
   
   

   Construction Firms Face Autumn Microsoft Project Retirement Deadline | For Construction Pros

   With Microsoft Project set to retire in 2026, contractors are weighing new scheduling platforms and collaborative project management tools.

   www.forconstructionpros.com
2. Official source: techcommunity.microsoft.com
   
   https://techcommunity.microsoft.com/blog/plannerblog/transitioning-to-microsoft-planner-and-retiring-microsoft-project-for-the-web/4410149/replies/4508917
3. Official source: learn.microsoft.com
   
   

   Project for the web - Microsoft Lifecycle | Microsoft Learn

   Project for the web follows the Modern Lifecycle Policy.

   learn.microsoft.com
4. Official source: support.microsoft.com
   
   

   Project for the web and Project Online | Microsoft Support

   Learn about how Project for the web works with Project Online.

   support.microsoft.com

 

[ChatGPT]

Project Online portfolios built around independent schedules and basic task tracking can move toward Planner premium, but PMOs that rely on cross-project dependencies, capacity planning, multi-schedule operations, custom workflow, or deeply integrated Project Web App (PWA) environments should treat September 30, 2026 as a platform-decision deadline—not merely a date to export files.
WindowsForum reports on the retirement make a practical point: exporting PWA schedule data alone does not preserve the working project record. PMOs also need a plan for linked SharePoint content, reporting history, permissions, workflow evidence, integrations, and records retention.
Microsoft lists September 30, 2026 as the Project Online retirement date in its Project Online lifecycle entry. Microsoft’s retirement announcement also states that Project Online-only plans stopped being sold to new customers on October 1, 2025, and that new Project Online tenant creation is no longer available after April 1, 2026. The retirement applies to Project Online, not Project desktop, Planner, or Project Server Subscription Edition.
Microsoft identifies Planner premium as the path for premium scheduling capabilities, but it does not present it as a feature-for-feature PWA replacement. Organizations with cross-project dependencies, enterprise capacity planning, or bulk operations across multiple schedules may need redesign and rebuild work using Dataverse, Power Apps, Power Automate, and Power BI.

Make the platform decision before moving data​

Use this routing matrix before selecting a destination:

If your portfolio primarily needs…	Answer	Recommended route
Independent schedules, task assignments, basic tracking, and team-level status visibility	Yes	Assess Planner premium through a representative pilot.
Advanced portfolio controls or extensive schedule coordination	Yes	Scope a Dataverse/Power Platform rebuild or evaluate other PPM options.
Deeply customized PWA configuration, custom workflow, significant reporting, or critical integrations	Yes	Conduct a platform-selection assessment before migration; do not assume Planner premium is the destination.
A portfolio that can retire or simplify advanced controls without affecting decisions, compliance, or delivery	Yes	Document the controls being retired and test Planner premium for the remaining work.
A requirement to reproduce every current PWA behavior	Yes	Treat the effort as a business-system replacement, not a schedule conversion.

The useful question is not “How many projects do we have?” It is “What decisions, controls, and records become unavailable if PWA disappears?”
A portfolio of independent plans can often simplify. A portfolio becomes a higher-risk replacement effort when schedules affect one another, resource managers make decisions from enterprise demand data, or the PMO applies governance controls across many projects.
Warning signs include:

• Resource decisions based on enterprise resource data, capacity, demand, utilization, or timesheet information.
• Cross-project dependencies that affect portfolio dates or executive decisions.
• Custom enterprise project types, fields, lookup tables, calendars, views, or security structures.
• Stage gates, intake approvals, notifications, escalations, or exception processes.
• OData feeds, Power BI datasets, Excel refreshes, scripts, APIs, or downstream integrations.
• SharePoint project sites whose documents, risks, issues, deliverables, lists, permissions, or retention labels form part of the formal project record.
• Reports that combine Project Online information with finance, HR, procurement, service, or other line-of-business data.

Produce a destination-selection decision package​

Before approving a destination, require the PMO to create a scored comparison for every candidate platform and proposed rebuild option. The deliverable should score each candidate against:

• Cross-project dependencies
• Capacity planning
• Bulk operations
• Workflow and approvals
• Reporting and historical reporting
• Integrations and APIs
• Records retention and archive access
• Administration, security, and ownership
• Licensing, implementation, and ongoing operating cost

Each row needs a named business owner and technical owner who can mark the requirement pass, fail, or requires redesign. For example, the PMO director may own portfolio controls, the resource-management lead may own capacity planning, the records manager may own retention, and the platform administrator may own administration and integration support.
Planner premium, a Power Platform rebuild, Project Server Subscription Edition, and third-party PPM products can all be evaluation options. Project Server Subscription Edition is excluded from the Project Online retirement, but neither it nor third-party products should be described as Microsoft-endorsed functional equivalents. Each candidate should prove its fit using the organization’s own scenarios.

Test Planner premium as a focused replacement, not an assumed one​

Planner premium is worth evaluating when the organization can operate with modern scheduling, task management, and team-level plan execution. Test it with realistic work, not a stripped-down demonstration schedule.
Select one representative project that includes named resources, dependencies, required status reporting, governance checkpoints, and normal PMO handoffs. Define pass/fail criteria before configuring the pilot:

• Can project managers maintain the required schedule and task information?
• Can teams provide the information leaders need for status decisions?
• Can the PMO produce required reports without manual reconciliation?
• Can approvals and controls operate through an agreed process?
• Can support staff administer access, ownership changes, and reporting?
• Can the organization retain and find historical project records after cutover?

If the pilot proves only that users can enter tasks, it has not proved that the operating model works.
For requirements beyond Planner premium’s standard operating model, explicitly decide which PWA behaviors will be retired, which will be redesigned, and which require a different platform. Do not select a product merely because it imports schedules. Imported plans do not prove equivalent governance, reporting semantics, retention controls, or operational ownership.

Complete a usable inventory, not a high-level catalog​

WindowsForum retirement discussions specifically point to the gap between preserving schedule data and preserving the broader PWA and SharePoint record. Turn that concern into an inventory workbook with one row per item and these fields: item name, functional area, business owner, technical owner, active or historical status, downstream dependency, retention requirement, target disposition, validation evidence, and cutover wave.
Use the following as a recommended discovery checklist, not as a guarantee that every setting, object, or screen exists in every PWA configuration:

1. Review PWA administration and configuration. Record relevant enterprise configuration, such as custom fields, lookup values, calendars, project types, project detail pages, workflow components, security structures, resource settings, timesheet settings, task settings, operational policies, views, filters, and templates. Capture exports or screenshots where possible, and identify the owner who can explain each item’s business purpose.
2. Review projects and schedules. Create a project register showing project name, owner, status, dates, last update, active or historical classification, linked project site, key dependencies, required reports, and destination decision. Ask each business owner to confirm whether the project remains operational after retirement.
3. Inspect Project sites and SharePoint libraries. For each linked site, record document libraries, lists, risks, issues, deliverables, notebooks, site owners, members, visitors, external sharing, retention labels, legal holds, and unique permissions. Identify content that must remain searchable after the project closes.
4. Build a reporting and connection inventory. Identify OData feeds, Power BI datasets, Excel workbooks, Power Query connections, scheduled refreshes, report subscriptions, APIs, scripts, and integrations that use Project Online data. Record the owner, audience, refresh frequency, source data, and whether the output is required after retirement.
5. Document workflow and report history. For each intake, approval, stage-gate, or escalation process, record the trigger, approver, decision record, notification, exception path, and historical evidence that must be retained. For reports, retain the report definition, source description, report owner, and required historical snapshots.

The inventory needs signed business ownership. A PWA administrator can identify configuration, but may not know whether a report informs a board decision or whether a library is subject to a records schedule.

Preserve active work and historical records separately​

An archive is not simply a spreadsheet export. It must allow authorized users to find and understand the project record later.
First, classify every project as active, closing, or historical. Active projects require a destination and cutover plan. Closing projects may need a final status capture and document handoff. Historical projects need a retained record, a search path, and a retention decision.
For each historical or closing project:

1. Preserve the schedule record, including task structure, milestones, dates, assignments, dependencies, status information, and relevant project metadata.
2. Preserve linked SharePoint project-site content or an approved records copy, including documents, risks, issues, deliverables, lists, and required permissions.
3. Record retention labels, legal-hold requirements, access restrictions, and the group or role permitted to retrieve the archive.
4. Preserve report history, workflow decisions, approval records, and evidence needed to explain significant decisions.
5. Create an archive index linking the project identifier to its schedule export, SharePoint location, report history, retention status, and archive owner.
6. Test restoration and search access with users who did not create the archive. They must be able to locate a project, open its preserved schedule and documents, and confirm that permissions work as intended.

Assign one named accountable archive owner and a deputy. The archive owner is responsible for validation evidence, access requests, retention coordination, and final sign-off that historical records can be found after PWA retirement.

Work backward from September 30, 2026​

The following is a sample reverse schedule, not a set of universally usable deadlines. Organizations reading this after any listed milestone should immediately compress, combine, or replace that phase rather than waiting for the next date.

• Inventory sign-off: Complete the PWA, project, SharePoint, reporting, workflow, and owner inventories. PMO, security, records management, and system owners sign off.
• Pilot completion: Complete Planner premium, Power Platform, Project Server Subscription Edition, or PPM product pilots as appropriate. Demonstrate scheduling, reporting, approvals, access control, and support processes using representative projects.
• Archive validation: Complete active/historical classifications; preserve selected schedule records, SharePoint content, permissions, retention information, workflow history, and report history. Perform restoration and search tests.
• Wave cutover: Move active projects in planned waves, redirect reports and integrations, train users, and resolve pilot-to-production gaps. Keep a cutover log for every project and dependency.
• Shutdown rehearsal: Rehearse the loss of Project Online access. Confirm archive retrieval, report replacements, integration changes, access support, and retirement communications.
• September 30, 2026 — Retirement date: Complete final access, communication, and records-management actions under the approved plan.

Frequently Asked Questions​

Can Project Online customers keep using the service after September 30, 2026?​

Organizations should plan for Project Online retirement on September 30, 2026 and should not rely on continued service availability after that date. Microsoft lists the date in its Project Online lifecycle entry.

Does Project Online retirement affect Project desktop?​

No. Microsoft’s retirement material states that Project desktop, Planner, and Project Server Subscription Edition are excluded from the Project Online retirement.

Can Planner premium replace cross-project dependencies and capacity planning out of the box?​

Not necessarily. Microsoft identifies cross-project dependencies, capacity planning, and multi-schedule bulk operations as scenarios that may require rebuild work using Dataverse, Power Apps, Power Automate, and Power BI.

Is exporting Project Online data enough?​

No. Exports are only one part of preservation. The complete plan must cover active schedules, historical records, PWA configuration, reporting, integrations, SharePoint content, permissions, workflow history, retention, and validated archive access.
The retirement date is fixed, but the destination architecture remains a business decision. Organizations that classify their real portfolio behavior, prove a destination through representative pilots, and validate preservation will be better positioned than those that treat Project Online retirement as a last-minute file export.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Get started with Project Online - ProjectOnline | Microsoft Learn

   This article is the first in a series that will help you get started with Project Online. There are three main steps to getting started: signing up, adding people, and creating projects.

   learn.microsoft.com
2. Independent coverage: techcommunity.microsoft.com
   
   https://techcommunity.microsoft.com/blog/plannerblog/microsoft-project-online-is-retiring-what-you-need-to-know/4450558/replies/4489283
3. Primary source: WindowsForum
   
   

   Microsoft Project Online Retirement 2026: PMO Migration Guide | Windows Forum

   Microsoft Project Online will retire on September 30, 2026, with Microsoft ending sales of Project Online-only plans to new customers on October 1, 2025...

   windowsforum.com