Microsoft Project Online is no longer available. The shutdown leaves former users with a practical question: where do project schedules, resource data, and connected workflows go now?
According to projectmanager.com, the service was discontinued on September 30, 2026, after Microsoft stopped selling it to new customers on October 1, 2025. Its websites, project data, and connections no longer work, so users must transfer their schedules to another tool.
What changed in Microsoft Project Online?
Microsoft Project Online was a cloud-based project portfolio management service built on SharePoint Online and sold as part of Microsoft 365. Project managers used it to build schedules, manage resources, and publish plans. Portfolio managers analyzed and prioritized projects, while team members updated tasks and submitted timesheets through the Project Web App.
The service was particularly suited to large organizations already using Microsoft 365, SharePoint, and Power BI. It combined shared resource pools, timesheet approvals, demand management, and portfolio analysis in one environment. The Windows desktop client, Project desktop, supported more detailed scheduling and synchronized with the web service.
Microsoft offered three principal plans during the final sales period: Essentials for team members, Professional for project managers, and Premium for portfolio managers and administrators. Professional and Premium were later renamed Project Plan 3 and Project Plan 5. Their listed prices were $30 and $55 per user per month, respectively.
None of those plans can now be purchased or used.
Why the former plan structure matters
The practical replacement challenge depends on which former plan an organization used. Essentials was primarily for team members, Professional centered on scheduling and resource management, and Premium added portfolio-level planning and administration. Replacing a schedule is therefore only one part of the transition.
The former plan structure sets the evaluation criteria:
| Former plan | Primary users | Capabilities that need checking | What should drive the replacement choice |
|---|---|---|---|
| Project Online Essentials | Team members | Task, issue, and risk updates, timesheets, document sharing, and Microsoft Teams collaboration | A solution for routine participation and reporting, without assuming it can reproduce the former Professional or Premium environment |
| Project Online Professional | Project managers | Detailed scheduling, dependencies, critical path, baselines, resource costs, roadmaps, timesheets, and reports | A planning environment that preserves both schedule logic and the way teams and stakeholders consumed it |
| Project Online Premium | Portfolio managers and administrators | Everything in Professional, plus portfolio analysis, demand management, resource capacity planning, and resource-request approvals | A tool that supports governance across projects rather than only the delivery work inside one schedule |
This distinction is important because Essentials was an add-on for organizations using Professional or Premium; it was not a standalone Project for the web plan. Organizations wanting both Project for the web and Essentials used Project Plan 1.
A team that only needs task updates may have a different requirement from a portfolio group responsible for demand, capacity, and resource approvals. The most relevant comparison is therefore the workflow being replaced—not simply the number of users or the price of a new subscription.
What to check before moving schedules
Start with an inventory. Identify which schedules are active, which baselines still matter, and what resource, cost, approval, and reporting information stakeholders expect to retain. The reference says former users must transfer their schedules, but it does not provide one universal migration method for every alternative.
Next, test the workflow rather than only opening a file. A team that relied on timesheet approvals needs a replacement for that process, not merely a task list. A portfolio group may need demand and capacity views. Project managers should verify support for critical path, baselines, dependencies, and lag relationships.
ProjectManager, for example, is described as accepting MPP files and offering browser-based Gantt planning, critical-path analysis, and baseline plans. Those capabilities make it relevant to schedule-heavy teams, but opening an MPP file alone does not establish that every former Project Online workflow has been covered.
Before committing, run a representative project through the candidate system. Include a schedule with dependencies, an approval process, a baseline, and a stakeholder report. This exposes gaps while there is still time to adjust.
How to assess the Microsoft and third-party routes
Microsoft Planner, Project desktop, Project Server Subscription Edition, Dynamics 365 Project Operations, and third-party tools are among the alternatives identified by projectmanager.com. Each route should be evaluated against the former service’s role in the organization.
Project desktop is directly relevant where detailed scheduling is the priority. Project Online Professional previously combined it with the cloud service, allowing desktop schedules to be published for teams and managers. That distinction matters: adopting desktop planning does not automatically reproduce every web-based participation, portfolio, or approval workflow that an organization may have used.
Other options need the same feature-level scrutiny. The available facts do not establish a universal feature match among all alternatives, so buyers should avoid assuming that a similarly named project-management tool can support every Project Online workflow.
The strongest decision rule is straightforward: preserve the capabilities the organization actually relied on, then confirm that the two systems can remain aligned during transition. Teams managing both backlog work and cross-project dependencies may deliberately use separate layers—one for day-to-day delivery and another for planning, capacity, and executive reporting—provided ownership and update routines are clear.
What the shutdown says about tool selection
Microsoft Project Online’s end demonstrates how much organizational workflow can become attached to a single service. Standardizing on a connected Microsoft 365 environment may have reduced fragmentation, but it also concentrated risk when that service reached end of life.
For project leaders, the lesson is not that one Microsoft option should always replace another. It is that tool selection should include an exit plan. Know where schedules live, whether they can be exported, which integrations and approvals must be rebuilt, and who owns continuity if a service changes.
Agile teams still benefit from disciplined scheduling: visible dependencies, realistic capacity, frequent updates, and honest forecasts. The challenge is to support those needs without making the planning layer so cumbersome that teams stop using it.
What to watch next
The first priority is migration quality. Watch whether former users preserve baselines, dependencies, resource assignments, approvals, and reporting—not merely whether their files open in another tool.
The second issue is product structure. Some organizations may consolidate planning and delivery in one environment. Others may separate daily team work from portfolio oversight. Either approach can work, provided responsibilities and information flows remain clear.
Microsoft Project Online has shut down, and the answer is not simply to pick another app. Inventory what the service supported, test those specific workflows, and choose a durable home for both schedules and decision-making.
Key takeaways
- Inventory schedules, dependencies, baselines, resource data, approvals, and reports before migrating.
- Match each replacement to the capabilities the organization actually used.
- Test a representative project and its associated workflows before committing.
- Include exports, integrations, ownership, and continuity in every future project-tool selection.
Frequently asked questions
When did Microsoft Project Online shut down?
The service was discontinued on September 30, 2026. Microsoft had stopped selling it to new customers on October 1, 2025.
What happens to schedules in Microsoft Project Online?
Its websites, project data, and connections no longer work. Former users need to transfer their schedules to another tool, such as Microsoft Planner, Project desktop, Project Server Subscription Edition, Dynamics 365 Project Operations, or a third-party platform.
What alternatives are available?
Projectmanager.com identifies Microsoft Planner, Project desktop, Project Server Subscription Edition, and Dynamics 365 Project Operations. Third-party tools are also possible.
Should an agile team keep its scheduling details in the same tool as its backlog?
That depends on how the team operates. One system may manage the backlog while another supports cross-team dependencies, capacity, and executive reporting, provided both remain current.
What should be tested before a migration?
Test the capabilities your organization actually uses, such as dependencies, critical path, baselines, resource assignments, timesheet approvals, and stakeholder reporting.