Microsoft Project Online reaches end of service on September 30, 2026.

After that date the service stops. Existing projects, schedules, timesheets, resource data, custom fields, reports, and associated SharePoint content become inaccessible. There is no extended read-only window promised beyond the retirement date and no automatic migration path.

As of early September 2026 the remaining window is measured in weeks, not months. The operational friction that still surprises teams is the gap between “we will export the data” and the actual effort required to preserve years of project history, governance constructs, reporting, and integrations without breaking daily work. Organizations that treated the timeline as distant are now compressing what should have been a structured multi-month program into a short sprint.

What Exactly Is Retiring

Only the cloud Project Online service (Project Web App / PWA built on SharePoint Online) is retiring.

Unaffected products and services include:

• Project desktop (Project Standard 2024 and Project Professional 2024)
• Project Server Subscription Edition (on-premises)
• Microsoft Planner (basic and premium capabilities)
• Dynamics 365 Project Operations

Sales of new Project Online-only SKUs ended October 1, 2025. Existing customers have continued full use and support up to the September 30, 2026 cutoff. Project Online Essentials licenses also reach end of life around the same period and require transition to supported Planner and Project plans or Project Server CALs to retain rights.

Microsoft’s stated reason is the legacy architecture’s limits on delivering modern AI-powered experiences. Investment has shifted to Planner, Microsoft 365 Copilot, and the Project Manager agent.

Immediate Risks If You Wait

After September 30, 2026:

• Users lose access to Project Web App.
• OData endpoints and related integrations stop responding.
• Historical project data, baselines, timesheets, and resource engagements are no longer reachable inside the service.
• Backup tools that rely on the Project Online APIs lose the ability to restore from that point forward.

Third-party backup providers have already published cutover dates aligned with or immediately after the Microsoft retirement. Any data you still need must be exported or migrated before the service is switched off.

The Decision Framework That Still Works

Most organizations fall into one of three practical paths.

1. Move to Planner (Premium where needed)
Suitable when the primary use of Project Online was task and simple project tracking, team collaboration, and light scheduling. Planner Plan 1, Plan 3, or Plan 5 (often labeled Planner and Project) already include premium capabilities for many licensed users. The interface is familiar inside Teams and Microsoft 365. Complex enterprise resource pools, heavy custom fields, portfolio prioritization models, and sophisticated reporting usually do not transfer cleanly. Treat this path as a deliberate simplification rather than a feature-for-feature replacement.

2. Move to Project Server Subscription Edition
The on-premises (or self-hosted) continuation of the Project Server line. It preserves the classic Project desktop + PWA experience, enterprise custom fields, resource management, and many of the governance features Project Online users relied on. This path requires infrastructure capacity, ongoing patching, and either internal expertise or a partner to run the farm. It is the closest functional bridge for organizations that still need traditional PPM depth and are not ready to redesign processes around Planner or a third-party platform.

3. Move to a modern PPM or hybrid platform
Many teams evaluate Power Platform-based solutions, Dynamics 365 Project Operations, or specialized PPM tools that sit on Microsoft 365. These can deliver stronger portfolio views, better AI assistance, and tighter integration with modern work management, but they require process redesign and data mapping. The effort is higher; the long-term alignment with Microsoft’s direction is often better.

Project desktop remains available regardless of the path chosen. Many hybrid models keep the desktop client for detailed scheduling while shifting collaboration and portfolio views elsewhere.

Concrete Steps to Take This Month

Inventory before you migrate.
List every active and closed PWA site, the number of projects, custom fields, lookup tables, enterprise resources, timesheet periods, reports (including any Power BI or Excel connections that pull from the OData feed), and third-party integrations. Identify which projects still have active work and which are purely historical. This inventory drives the export scope and the target platform choice.

Export what you cannot afford to lose.
Use Project desktop to open and save critical schedules as .mpp files. Export custom field definitions, resource data, and timephased information where possible. Capture SharePoint lists and document libraries that sit alongside the projects. Do not assume a single “export all” button will produce a usable archive; plan for iterative, project-by-project or site-by-site work.

Decide the target and run a pilot.
Pick one representative set of projects and move them to the candidate platform. Validate that resource assignments, baselines, custom fields, and reporting still meet the PMO’s minimum requirements. User acceptance at this stage prevents late surprises when the full cutover arrives.

Address licensing in parallel.
Users currently on Project Online Essentials or older Project Online plans need new assignments (Planner and Project Plan 3 or Plan 5, or Project Server CALs) before the related end-of-life dates. Confirm that the chosen target platform’s licensing covers both the people who edit schedules and the people who only view or update status.

Communicate the cutoff.
Project managers, resource managers, and sponsors need a clear date after which Project Online will no longer be available. Provide the interim process for opening new work and the location of the migrated or archived data.

Common Friction Points Appearing Now

Custom reports and OData-dependent dashboards frequently take longer to rebuild than the project schedules themselves. Governance workflows built on SharePoint or Power Automate that reference Project Online lists break unless re-pointed. Organizations that kept large numbers of closed projects “just in case” discover the export volume is larger than expected. Teams that assumed Planner would absorb everything without process change run into missing resource leveling, limited portfolio views, or different security models.

The compressed timeline amplifies every one of these issues. Work that could have been staged across two quarters now has to finish before the service disappears.

What Success Looks Like by September 30

Active projects live in the new platform or in Project desktop with a clear collaboration method. Historical data required for audits, lessons learned, or compliance is exported and stored in a durable location. Users know where to go on October 1. Licensing is clean. Integrations that previously pointed at Project Online have been updated or retired.

DirectDeals works with organizations that need practical help mapping current Project Online usage to the right successor platform, structuring the data export, and avoiding last-minute loss of access. With the retirement date now only weeks away, the highest-leverage action is an honest inventory of what still matters and a firm decision on the destination.