Before selecting a replacement for Microsoft Project Online, organisations need to understand how the platform is actually being used today and which capabilities cannot be lost during the transition.

Many migrations appear technically successful, with data moved and new tools deployed, but months later teams discover that key portfolio capabilities have been lost. Reporting becomes fragmented, governance processes need to be rebuilt manually, and leadership confidence in portfolio data begins to erode.

Our readiness checklist helps organisations avoid that outcome by providing a structured way to assess the risks before any migration decisions are made.

It guides teams through critical questions such as:

• Which reports are relied on by senior leadership?
• Which datasets underpin portfolio reporting?
• Which governance or assurance processes depend on Project Online?

By working through these questions early, organisations can identify the capabilities that must be preserved and avoid the common pitfalls seen in many migrations — such as losing historic baselines, fragmenting portfolio data, or rebuilding governance processes manually.

Use the checklist to ensure your transition is treated as a portfolio change programme, not simply a technical platform replacement.