When an organisation retires a project management platform, it is not just the software that needs replacing. Years of project data, reporting structures and established ways of working may also be affected.
On 30 September 2026, Microsoft retired Project Online, a platform that supported enterprise project and portfolio management for more than a decade. Other Microsoft Project products remain available, but organisations relying on Project Online have had to transition away from the service.
What interests me about this development is not which replacement Microsoft recommends, but the implications for organisations that have built their project management processes around a particular technology. Consider a PMO that has spent years using one platform for project schedules, resource allocation, performance reporting and portfolio oversight. Over time, it may have developed customised dashboards, approval workflows, reporting standards and integrations with other business systems. Replacing the software may be easier than preserving everything that depends on it.
Historical project data may be needed for audits, performance comparisons or future planning. Existing integrations may support critical reporting, while workflows may reflect governance requirements that a replacement cannot automatically replicate. Microsoft confirmed that after retirement, organisations would no longer be able to access their projects or associated data through the service. This makes data preservation and transition planning particularly important.
I think there is a broader lesson here about managing enterprise technology throughout its lifecycle. Technology selection often focuses on immediate functionality, implementation costs and expected benefits. But equal consideration should be given to what happens when it becomes obsolete, is discontinued or no longer meets business requirements.
For PMOs and transformation leaders, this means knowing where critical project information resides, maintaining data retention and export arrangements, documenting essential integrations and evaluating replacements against actual organisational requirements. A technology migration is not necessarily complete when users can access the replacement system. Reporting continuity, historical data integrity, process effectiveness and the ability to support existing governance and decision-making are equally important measures of success.
Perhaps organisations should ask not only how well enterprise technology will support operations today, but how effectively they could transition away from it tomorrow. Technology will continue to evolve, but the knowledge, accountability and decisions built around it should not disappear because a platform reaches the end of its life.
Good ideas get better in conversation.
