Project Online Retirement. Capability Gaps Organisations Must Address

Microsoft is retiring Project Online. For many organisations, this is not simply a technical migration. It is a strategic decision about the future of their project delivery capability.

PPM vendors are actively positioning their platforms as “the best alternative”. For those making the transformation decision, the real challenge is knowing which aspects to evaluate and which questions to ask to uncover capability gaps across the alternatives before committing to a new system.

This post will help you identify the questions to ask to make a strategic decision and choose the most suitable alternative.

To support the Project Online transition assessment, several aspects must be assessed:

• What capabilities do we really need for our style of delivery (especially in Hybrid era)?
• What capabilities are we losing?
• What capabilities are we gaining?
• Which gaps are critical for delivery performance, and which are merely cosmetic?
• Are we replacing a legacy system… or locking ourselves into another one?

Before committing to a new platform, organisations must assess the following dimensions:

1. Which Project Online capabilities must be replaced?
2. Which new PPM capabilities could be gained by moving?
3. Which Microsoft Project scheduling gaps have been historically overlooked or silently accepted?
4. Where are strategic opportunities? 

Uncovering these layers can help leaders make an informed decision.

For decades, Microsoft Project has been considered the gold standard of scheduling. Generations of project managers built their careers using it. But how capable is it really?

To understand what is being lost with Project Online, we need to step back to the early 2000s, before Project Server and later Project Online were introduced.

When desktop Microsoft Project is used in isolation:

1. Each project manager customises calendars, views, formulas, and fields independently.
2. There is no single enterprise resource pool. Resulting in duplication and no cumulative analysis.
3. Security and access can’t be configured. No structured field-level or project-level permissions.
4. Custom fields created for analytics are not automatically connected to enterprise reporting.
5. Centralised portfolio reporting is effectively impossible.
6. Reporting often means screenshots in Word or PowerPoint.
7. There is no integrated connection between schedules and project registers (risks, issues, deliverables, financials).
8. No opportunity to access data via the web.

Project Online addressed these enterprise-level governance gaps. It created structure, centralisation, and visibility.

With its retirement, organisations risk returning to fragmentation, unless they deliberately replace these capabilities. However, Project Online was far from an ideal environment for enterprise project portfolio delivery. 

Despite its benefits, Project Online had significant limitations that were never fully addressed.

Schedule Environment Gaps

• • No version control
  • No backups (!)
  • Limited schedule-to-schedule integration
  • Limited backend connectivity
  • No vertical (WBS-level) access control
  • No horizontal (field-level) access control (except Baseline fields)

It improved governance but did not fundamentally improve scheduling intelligence.

This distinction is critical.

Microsoft Project was actively developed from 1984 to 2016, after which Microsoft effectively stopped meaningful investment in the scheduling engine. Since version 2000, it was no fundamental scheduling improvements. Roadmap capability has arguably been the biggest innovation in the last 25 years.

Additionally, Microsoft Partners used built-in VBA capabilities to create their own add-ins, and users created macro-based features to enhance specific functionality. Some are very powerful. 

However, most Microsoft Project users still apply it in its basic form, often without add-ons or macros. Ironically, Project Online itself limited extensibility by not supporting add-ins capabilities.

Meanwhile, advanced scheduling systems have evolved significantly, particularly in resource-driven modelling, analytics, and simulation, and these gaps can’t be addressed without additional investments in a NEW scheduling engine. Let’s review Microsoft Project limitations:

Structural & Modelling Gaps

• No Work Breakdown Structures (WBS)
• No Resource Breakdown Structure (RBS), Cost Breakdown Structure (CBS), or Risk Breakdown Structure (RiskBS)
• No progress archives
• No configurable unique activity ID
• No backward scheduling
• No multi-resource crews
• No skills management
• No productivity modelling
• No material production modelling
• No idle time or idle cost calculation
• No lag calendars

Resource & Optimisation Gaps

• Ineffective resource levelling
• No resource critical path
• No resource-driven optimisation metrics
• No income simulation
• No multi-currency management

Risk & Analytics Gaps

• No built-in risk simulation
• No PERT (Removed in 2013)
• No advanced scheduling metrics
• No benefits modelling
• Limited schedule analytics
• Limited schedule comparison
• Limited baseline management
• Limited EVMS functionality

Governance & Quality Gaps

• No built-in schedule quality control
• No integrated scope management
• No cost centre management
• No hammock functionality
• No double dependencies
• Limited undo history

This is a long and probably incomplete list. Some of these may appear “advanced”, but many are not luxuries – they are essential to support project dynamics and commitments.

The deeper issue is methodological. Microsoft Project is built on classic CPM logic, assuming resource availability. It is not enough anymore. Modern delivery environments require methods to optimise and control delivery while accounting for available resources and rapidly changing priorities.

The retirement of Project Online is not only a disruption. It is an opportunity.

Organisations now face a strategic choice:

Do they:

• Preserve legacy thinking in a new wrapper?
• Or move toward modern, resource-driven, data-integrated scheduling environments that support Predictive, Adaptive and PredAptive delivery?

There are several paths for corporate users now. I will review the pros and cons of each option.

Invest in Project Server (On-Premise)

Microsot’s On-Premise alternative to project Online. 

Keep Desktop Microsoft Project + Add Alternative PPM System

Power Platform or non-Microsoft PPM systems.

Move to Alternative PPM + Scheduling Platform
Microsot’s Planner Premium or Non-Microsoft scheduling platform.

Hybrid Transition: New PPM Platform + Gradual Scheduling Migration

This option is similar to the previous one but enables a gradual transition, keeping Microsoft Project operational while migrating programmes to a more (or less?) capable scheduling engine. It reduces risk while enabling evolution.

The real risk is not losing Project Online. The real risk is replacing it without understanding what truly drives project delivery performance.

Technology choices are not IT decisions — they are strategic delivery decisions. Organisations that treat this transition as a procurement exercise will maintain the status quo. Those who treat it as a capability transformation will gain a structural advantage.
I haven’t touched on AI-enabling capabilities yet — that’s a separate, extensive, and fascinating topic. Stay tuned.