Microsoft Project Online replacement

Moving from Microsoft Project Online to ServiceNow® SPM.

Microsoft Project Online retired on 30 September 2026. For organisations that have selected, or are actively planning, ServiceNow Strategic Portfolio Management as the target platform, we help design and deliver the transition from existing Project Online processes, data, reporting and integrations.

Project Online has retired. The migration work can extend well beyond schedules.

Microsoft retired Project Online on 30 September 2026. Microsoft states that this retirement applies specifically to Project Online and does not retire Project desktop, Project Server Subscription Edition or Planner.

For organisations that used Project Online for enterprise project and portfolio management, the transition can involve much more than individual project plans. A Project Web App (PWA) environment may include enterprise custom fields and lookup tables, resource-pool and capacity structures, portfolio metadata, workflows, reporting feeds and integrations built around the existing service.

Microsoft Project Online lifecycle information →

This is a migration and implementation problem, not a like-for-like product copy.

Where ServiceNow SPM is the target, the objective is not to reproduce every Project Online configuration decision. The useful starting point is to identify the portfolio and delivery capabilities that still matter, understand the data and dependencies behind them, and decide how those requirements should work in ServiceNow.

Some elements should move. Some should be redesigned. Some historical data may be better archived than loaded into the new platform. Making those decisions early reduces unnecessary complexity later.

Do not migrate technical debt by default. A replacement programme is an opportunity to simplify obsolete fields, reports, workflows and data structures rather than recreate them automatically in ServiceNow.

What to inventory before designing the migration.

The current-state review should go beyond counting projects. Depending on how Project Online was used, useful areas to examine include:

  • Active and historical projects, schedules, tasks, milestones and dependencies.
  • Enterprise custom fields, lookup tables and the business meaning attached to them.
  • Project-level metadata, portfolio structures and prioritisation information.
  • Enterprise resources, roles, calendars, rates and capacity-planning structures.
  • Project Detail Pages, workflow-driven processes and approval points.
  • OData-based reporting, Power BI or data-warehouse dependencies.
  • Interfaces to finance, HR, delivery, reporting or other enterprise systems.
  • Data that must remain accessible for audit, reporting or operational reasons even if it does not belong in the target SPM solution.

Importing Microsoft Project files is only one part of the transition.

ServiceNow supports importing Microsoft Project files into its Project Management application, including mapped custom fields where the corresponding ServiceNow fields have been created. That can be useful for bringing project schedules into the platform.

But a Project Online replacement can include information and processes that are not contained in an individual project file — such as enterprise resource structures, PWA metadata, workflow logic, reporting feeds and integrations. Those need to be assessed and mapped separately rather than assuming an MPP import represents the whole migration.

ServiceNow documentation: importing Microsoft Project files →

A practical Project Online to ServiceNow SPM delivery sequence.

  • Inventory the current environment. Understand what is actually used, who depends on it and which data or integrations must survive retirement.
  • Define the target process. Translate portfolio, project, resource, financial and reporting requirements into the target ServiceNow SPM operating model.
  • Set migration scope. Decide what should be migrated, transformed, archived, redesigned or retired.
  • Configure the target solution. Build the required ServiceNow SPM data structures, workflows, roles, reporting and integrations before loading production data.
  • Run trial migrations and reconcile. Validate mappings, record counts, key values, relationships and reporting outcomes rather than treating a successful import as proof of a successful migration.
  • Cut over deliberately. Coordinate final extraction, migration, validation, user readiness and the transition into live operation.

Business process and technical delivery together.

Project Online replacement work normally needs both sides of the problem: discovery, workshops and requirements to define how the future process should operate, and hands-on ServiceNow delivery to configure, integrate and migrate the solution.

SPM Wise supports both. Our practitioner experience includes hands-on enterprise Project Online replacement work into ServiceNow SPM, alongside broader SPM implementation, configuration, reporting, integration and data-migration delivery.

Already moving from Project Online to ServiceNow SPM?

If ServiceNow SPM is already your chosen or likely destination, we can help review the existing Project Online environment, define the migration scope and target design, and support the implementation through migration, testing and cutover.

Discuss your Project Online to SPM migration