Microsoft has confirmed that Microsoft Project Online will be retired in September 2026, meaning organisations currently relying on it must plan their transition.
While some organisations assume this is simply a matter of replacing one project management tool with another, the reality is more complex.
Over the years, Project Online has become a central operational system for many PMOs, supporting scheduling, governance, resource management, financial oversight, collaboration, and integration with other enterprise systems.
Because of this, the right migration strategy depends heavily on how your organisation actually uses Project Online today.
Before selecting a replacement platform, organisations should perform a structured assessment of how Project Online is currently used.
In most environments, usage falls into several functional categories.
|
Some organisations use Project Online primarily as a central repository for schedules where project managers publish their plans for visibility. Typical characteristics include: Possible alternatives include Microsoft Planner Premium (Project for the web), Smartsheet, Monday.com, Jira, and dedicated PPM platforms such as pmo365. |
|
A more advanced use case involves assigning resources to tasks and tracking effort against schedules. |
|
In more mature environments, Project Online is used to manage financial aspects of project delivery.
|
Another major use of Project Online is project governance and approval workflows. Many organisations configure approval processes based on project type or investment category.
Typical examples include:
- Project initiation approvals,
- Business case submission,
- Stage gate approvals,
- Steering committee reviews, and
- Portfolio prioritisation workflows.
Modern solutions typically support configurable workflows, role based approvals, automated notifications, and audit trails.
Project Online is frequently used by PMOs to manage resource demand and organisational capacity.
Typical capabilities include:
- Viewing resource allocation across projects,
- Identifying over allocation,
- Forecasting future demand,
- Balancing workload across teams, and
- Planning hiring or contractor needs.
Many Project Online environments include lists used to manage governance artefacts such as Risks, Issues, Assumptions and Dependencies.
These elements are essential for project governance, status reporting, and escalation management.
Some organisations rely heavily on Project Online timesheets to capture project effort for utilisation reporting, payroll integration, or client billing.
Project Online integrates tightly with SharePoint Online which is used to store project documentation such as document libraries, version control, and collaboration assets.
Most organisations will continue using SharePoint Online after migration.
|
Many organisations integrate Project Online with ERP systems such as SAP, Oracle, TechnologyOne, or Dynamics 365 to support financial reporting, cost tracking, project accounting, and procurement data. |
Project Online often operates alongside operational work management platforms such as Microsoft Planner, Jira, Monday.com, or ServiceNow. |
Many organisations remain within the Microsoft ecosystem by combining Microsoft Project Desktop for scheduling, Microsoft Planner Premium for task management, Power Platform for workflows and automation, SharePoint for document management, and Power BI for reporting.
Another common approach is implementing a dedicated Project Portfolio Management solution designed specifically for PMOs.
One example is pmo365, a Microsoft Power Platform based PPM solution that provides a library of specialised apps designed to support different PMO functions including project governance, portfolio planning, resource management, risk management, and project delivery.
Organisations can deploy the specific apps they need while remaining fully integrated with Microsoft 365, Dataverse, Power BI, and SharePoint.
Some organisations adopt a hybrid architecture combining scheduling tools, workflow platforms, ERP systems, and operational work management tools. This provides flexibility but requires strong integration architecture and governance.
The retirement of Microsoft Project Online represents an opportunity for organisations to rethink how project and portfolio management should operate in a modern digital environment.
By assessing how scheduling, governance, resource planning, financial tracking, and integrations are currently used, organisations can design a migration strategy that not only replaces Project Online but improves how projects are governed and delivered across the organisation.