



Migrating from Microsoft Project Online, answered.
PPM Express has a built-in connector to Microsoft Project Online, so migration is a product capability rather than a consulting engagement. Project schedules are copied into PPM Express task management with the structure preserved — WBS and outline, Baseline 0, dependencies, lead and lag time, and custom fields. Because the connector does the work, there is no separate implementation fee.
No. Project Sites are not migrated. We recommend keeping enterprise documents where they already live — SharePoint, OneDrive or Microsoft 365 — and linking each project in PPM Express to its SharePoint site after migration. That leaves document governance with the platform built for it instead of duplicating a document store inside the portfolio tool.
Project schedules with their WBS and outline structure, Baseline 0, task dependencies, lead and lag time, and custom fields. What does not come across is Project Sites and anything that lived only in SharePoint alongside the project. Establishing that boundary at the start is usually the difference between a migration that finishes and one that stalls.
Usually one of three reasons. The administration overhead has outgrown the value it returns; the interface is too heavy for the people who need to read a portfolio rather than build a schedule; or delivery has spread into Azure DevOps, Jira, Planner, Smartsheet and monday.com, and Project Online can no longer see most of it. The third is the one that normally forces the decision.
No. Project Online stays a supported connection, so you can run both in parallel — read Project Online into PPM Express, prove the portfolio layer with real data, and move schedules when the organization is ready. Treating cutover as a transition rather than an event is how most enterprises do it.
Yes. One of the largest law firms in the United States — over 2,000 attorneys across 14 offices worldwide — runs 7 IT portfolios and more than 200 projects in PPM Express. Read-only portfolio access means the executives, finance partners and sponsors who only need to look at the portfolio do not have to be set up as full users.
Yes, and it is a common way in. A single PMO, IT function or business unit can run its own portfolio without a company-wide program, then extend once the model has proven itself. Nothing about the setup assumes you control the whole estate on day one.
A help centre, video guides, an in-product AI assistant and direct access to the support team, with a ticket for anything that needs a person. Enterprise migrations also run through the same discovery, demo and supervised trial sequence as every other engagement, so the first migration is not the first time anyone has looked at your data.
US and EU data residency, GDPR compliance, and custom DPAs where regulation requires them. Identity runs through Microsoft 365 or Okta SSO, with centralized user management, advanced permissions, detailed audit logs and strict data isolation.
Yes, and for a migration that matters more than a sandbox. The sequence is a discovery call, a demo against your scenario, then a supervised trial with your real schedules — because what you actually need to see is your own data arriving intact. No credit card is required to start.
A full refund within 30 days.
What leadership sees when every delivery tool reports into a single portfolio view.
Strategy
Capacity from real work weeks, so over-allocation surfaces before you commit.
Product
Portfolio dashboards and Power BI datasets built from live delivery data.
Product
Last updated 20 August 2026