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?
| Date | Change |
|---|---|
| September 2025 | Microsoft announces Project Online’s retirement |
| October 1, 2025 | End of sale of Project Online-only plans to new customers |
| April 1, 2026 | Existing customers can’t create new Project Online tenants or functional PWA instances |
| April 2, 2026 | SharePoint Add-ins, Azure ACS and SharePoint 2013 workflows retired in Microsoft 365 |
| July 14, 2026 | Project Server 2016 and 2019 reach end of extended support |
| September 30, 2026 | Project 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:
- Local .mpp files saved by project managers, which Project desktop can still open.
- Earlier exports: Excel exports, OData extracts in Power BI datasets, reporting databases or backups your IT team took.
- 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.
- 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:
| Group | What they used | What they need next |
|---|---|---|
| PMO and portfolio leads | Portfolio analysis, Enterprise Project Types, resource center | Portfolio views and capacity planning |
| Project managers | Schedules, dependencies, baselines | Gantt or timeline views with dependencies |
| Team members | Tasks and timesheets | Simple task lists, time entry |
| Finance | Actuals, cost reports | Time and cost data that feeds billing or accounting |
| Executives | Power BI reports on OData feeds | Dashboards 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:
| Destination | Fits when you need |
|---|---|
| Microsoft Planner | Collaborative planning, task management, portfolio visibility, Teams integration |
| Project desktop | Standalone schedule authoring, Gantt, baselines, dependencies, resource and cost planning |
| Project Server Subscription Edition | On-premises Project Server, advanced portfolio and capacity management |
| Dynamics 365 Project Operations | Projects 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?
- Inventory what you hold: .mpp files, exports, datasets, SharePoint content and backups, with owners.
- List what each team actually needs: active projects, recent history, or only archives.
- Choose the destination per workload. A PMO and a software team may need different tools.
- 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.
- Rebuild calendars, views and reports in the destination; these are configuration, not data.
- Move documents from SharePoint project sites to the destination or a modern SharePoint site.
- Validate a sample of projects: task counts, dates, dependencies and assignments.
- 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.