Skip to content
Get a quote

Project Online retired on September 30, 2026

Deadline: September 30, 2026

Short answer

Microsoft retired Project Online on September 30, 2026. Projects and their data are no longer accessible through the service, PWA pages and reporting APIs stop working, and Project desktop can no longer connect to it. Microsoft's paths are Planner, Project desktop, Project Server Subscription Edition or Project Operations. FlitStack AI migrates preserved project data to Jira, Asana or monday.com.

By

What we handle5
  • Keep schedules for standalone use
  • Move to Microsoft Planner
  • Keep advanced PPM on-premises
  • Tasks, dependencies and assignments
  • Reports and integrations

What the native tool does, and where it stops

TaskNative toolWith FlitStack AI
Keep schedules for standalone useProject desktop stays available as a standalone product and works with local .mpp files, but can't connect to Project Online.Moves preserved plans into a team tool so schedules aren't stuck on one laptop.
Move to Microsoft PlannerMicrosoft's recommended destination for collaborative planning and task management; no one-to-one replacement for every PWA feature.Migrates to Jira, Asana, monday.com or Trello when Planner isn't the right fit.
Keep advanced PPM on-premisesProject Server Subscription Edition.Not applicable to an on-premises Project Server deployment.
Tasks, dependencies and assignmentsNo Microsoft migration tool from Project Online data to Planner or third-party tools is named in the retirement guidance.Maps tasks, subtasks, predecessor and successor links, assignees (matched by email) and custom fields to the destination's model.
Reports and integrationsREST, CSOM, JSOM, ProjectData and OData feeds are unavailable after retirement; reports and flows must be replaced.Data only. Dashboards, views and automations are rebuilt in the destination.
SharePoint project sitesNon-PWA SharePoint content follows normal SharePoint lifecycle; PWA site collections can't be converted to standard sites.Moves documents and comments attached to tasks where the destination supports them.

Deadline passed: September 30, 2026. Microsoft has retired Project Online. Its retirement guidance says Project Online data, pages, reporting endpoints, APIs and synchronization stop working on that date, and that projects and their service data are no longer accessible through Project Online. Microsoft’s final reminder said the retirement would happen automatically, with no admin action required, and didn’t describe a grace or read-only period.

If you are reading this after the date, the question is what you still hold and where it should go. This guide covers what stopped, what may still be reachable, and the destinations.

What were the Project Online retirement dates?

DateChange
September 2025Microsoft announces Project Online’s retirement
October 1, 2025End of sale of Project Online-only plans to new customers
April 1, 2026Existing customers can’t create new Project Online tenants or functional PWA instances
April 2, 2026SharePoint Add-ins, Azure ACS and SharePoint 2013 workflows retired in Microsoft 365
July 14, 2026Project Server 2016 and 2019 reach end of extended support
September 30, 2026Project Online retires

What stopped working when Project Online retired?

From Microsoft’s “Prepare for Project Online retirement” page:

  • PWA experiences: PWA Home, Project Center, Resource Center, Timesheets, Project Detail Pages, scheduling and publishing, time and task management, resource management, portfolio analysis and PWA settings.
  • Service data: projects and schedules, tasks and assignments, timesheets, enterprise resources and engagements, enterprise calendars, custom fields and lookup tables, portfolio analyses, Enterprise Project Types, and workflow and security configuration.
  • Cloud APIs: Project Online REST, CSOM, JSOM, ProjectData and OData reporting feeds, so reports, scripts and Power Automate flows built on them fail.
  • Project desktop connectivity: the desktop app still works standalone, but can’t retrieve or publish Project Online data.

What might I still have?

Not everything lived in the Project Online service layer. Check:

  1. Local .mpp files saved by project managers, which Project desktop can still open.
  2. Earlier exports: Excel exports, OData extracts in Power BI datasets, reporting databases or backups your IT team took.
  3. SharePoint content without a Project Online dependency. Microsoft says documents, lists, issues, risks and deliverables on SharePoint sites can follow the normal SharePoint lifecycle, but a reachable site doesn’t mean its PWA behaviour still works.
  4. Third-party backups of the Project Online environment.

Microsoft also notes there is no supported process to convert a PWA site collection into an independent standard SharePoint site, so move the content you need to keep.

If your tenant still responds, don’t rely on it. Export everything you can straight away.

What about Project Server 2016 and 2019?

Some organizations ran Project Online alongside on-premises Project Server, or considered moving back to it. Microsoft’s lifecycle list shows Project Server 2016 and Project Server 2019 reached end of extended support on July 14, 2026. The supported on-premises option is Project Server Subscription Edition. Microsoft’s retirement guidance also notes that PSI, WCF and ASMX are on-premises Project Server technologies, not Project Online cloud APIs, so inventory them only if your environment includes Project Server.

Which teams need what after Project Online?

Project Online often served several groups at once. Splitting them makes the destination choice easier:

GroupWhat they usedWhat they need next
PMO and portfolio leadsPortfolio analysis, Enterprise Project Types, resource centerPortfolio views and capacity planning
Project managersSchedules, dependencies, baselinesGantt or timeline views with dependencies
Team membersTasks and timesheetsSimple task lists, time entry
FinanceActuals, cost reportsTime and cost data that feeds billing or accounting
ExecutivesPower BI reports on OData feedsDashboards on a supported data source

Where should Project Online users go?

Microsoft’s guidance lists four destinations, and says none is necessarily a one-to-one replacement:

DestinationFits when you need
Microsoft PlannerCollaborative planning, task management, portfolio visibility, Teams integration
Project desktopStandalone schedule authoring, Gantt, baselines, dependencies, resource and cost planning
Project Server Subscription EditionOn-premises Project Server, advanced portfolio and capacity management
Dynamics 365 Project OperationsProjects tied to sales, resourcing, finance, project accounting and billing

Many teams also look outside Microsoft: Jira for engineering and IT delivery, Asana or monday.com for cross-team work management, Smartsheet for spreadsheet-style planning.

How do I move Project Online data to a new tool?

  1. Inventory what you hold: .mpp files, exports, datasets, SharePoint content and backups, with owners.
  2. List what each team actually needs: active projects, recent history, or only archives.
  3. Choose the destination per workload. A PMO and a software team may need different tools.
  4. Map the model: tasks and summary tasks to the destination’s hierarchy, dependencies (with lead and lag), milestones, resources to users by email, and enterprise custom fields to custom fields.
  5. Rebuild calendars, views and reports in the destination; these are configuration, not data.
  6. Move documents from SharePoint project sites to the destination or a modern SharePoint site.
  7. Validate a sample of projects: task counts, dates, dependencies and assignments.
  8. Replace integrations that used Project Online APIs.

What gets lost when moving from Project to other tools?

  • Critical path and resource levelling have no native equivalent in most work-management tools.
  • Lead and lag times on dependencies often need a custom field.
  • Deep WBS hierarchies may exceed the destination’s nesting.
  • Timesheets and actuals need a destination that tracks time, or an archive.

What should I tell users?

Tell them which tool replaces each thing they did in PWA, where their old schedules and documents now live, and who to ask when something is missing. Microsoft’s guidance ends with the same step: prepare users, administrators and support teams before the switch, not after.

When to bring in FlitStack AI

FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It migrates projects, tasks, subtasks, custom fields, comments, attachments, dependencies and time entries into PM tools, matching users by email and flagging any it can’t match, with validation and one-click rollback. Views, dashboards and automations are rebuilt in the destination. The site lists 2 to 5 days as typical for a PM migration. On the scoping call, the team confirms what can be recovered from the files and exports you still hold.

See Microsoft Project to Jira, the Microsoft Project migration hub, or destinations Asana and monday.com. To start, book a free scoping call.

Questions, answered

A few useful answers.

When did Project Online retire?

September 30, 2026. Microsoft ended sales of Project Online-only plans to new customers on October 1, 2025, and from April 1, 2026 existing customers could no longer create new Project Online tenants or PWA instances.

What happened to my Project Online data?

Microsoft says that after retirement, projects and associated Project Online service data are no longer accessible through Project Online. That includes schedules, tasks, assignments, timesheets, enterprise resources, calendars, custom fields and lookup tables, portfolio analyses and Enterprise Project Types.

Does Project desktop still work?

Yes, as a standalone product. Project desktop did not retire with Project Online, but it can no longer connect to Project Online to retrieve or publish service data. Local .mpp files still open.

What is Microsoft's recommended replacement for Project Online?

Microsoft lists four options: Planner for Microsoft 365 work management, Project desktop for standalone scheduling, Project Server Subscription Edition for on-premises portfolio management, and Dynamics 365 Project Operations where projects connect to sales, resourcing and finance.

Get a quote

Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

Get a quote