Project Online Retirement: 7 Steps to Recover, Migrate, and Move Forward

The Project Online retirement took effect on September 30, 2026, and many organizations are now evaluating replacement platforms, rebuilding reporting, and determining how to manage historical project data. Project Web App (PWA) is no longer available, Power BI dashboards connected to Project Online have stopped refreshing, and project managers are asking where their project data went. Whether your team planned ahead or is scrambling now, this migration guide walks you through seven practical steps to protect your data, choose the right replacement, and get your project portfolio management (PPM) back on track.

Microsoft stopped selling Project Online-only plans in October 2025 and has now fully shut the service down. For organizations that ran their PPM on Project Online, that means losing access to PWA, the OData reporting feed, custom fields, workflows, and the enterprise resource pool that tied everything together. Some of that loss came early. Microsoft retired the SharePoint 2013 workflow engine in Microsoft 365 on April 2, 2026, so many Project Online workflows, such as approval flows, stage-gate automation, and status updates, stopped running months before the final retirement date.

The good news is that the Project Online end of life doesn’t have to derail your projects. With a clear plan, most organizations can recover, migrate, and even come out with a more modern setup. Here’s where to start.

Not everything with “Project” in the name is gone. The retirement applies only to Project Online. Microsoft Project desktop, Project Server, and Microsoft Planner are not affected. Teams using Microsoft Project desktop with local MPP files can keep working as usual.

It also helps to clear up another common mix-up. Project for the web was retired separately in 2025, and its features were folded into Microsoft Planner.

Share a short, clear message with your users early. It will save your help desk from a flood of tickets and prevent unnecessary panic.

Next, take inventory of what was exported before the shutdown. Check with each PMO lead and project manager whether they saved:

Exports are often handled by individual teams rather than centrally, so gaps are common. Gather everything in one secure location with clear ownership.

Before choosing a new platform, step back and look at how your organization actually used Project Online. Many teams paid for enterprise features they rarely touched, while others relied heavily on capabilities that not every replacement offers.

Ask questions like these:

Your answers will point you toward the right platform and help you avoid choosing one you’ll outgrow.

There’s no single successor to Project Online. Most former Project Online customers evaluate one of three Microsoft-focused options.

Project Server Subscription Edition is the closest Microsoft platform to the traditional Project Online/PWA experience. It keeps the familiar PWA interface, advanced scheduling, demand management, and project requests, all running on your own infrastructure. It’s a strong fit for organizations with strict enterprise security, compliance, or data residency requirements. Your project data stays in an enterprise database you control.

Microsoft Planner with premium capabilities (Planner Premium) is the cloud-first option. It offers timelines, dependencies, portfolios, goals, and Copilot-driven capabilities (depending on licensing), with strong Microsoft 365 integration and Microsoft Teams access. It works well for teams that want simpler, real-time project management and collaboration, though organizations used to advanced resource capacity planning or portfolio dashboards may need Power Platform extensions to fill the gaps.

Dynamics 365 Project Operations suits organizations that need financial management, resource management, and billing in one system, such as professional services firms.

For software development teams, Azure DevOps may also be worth considering alongside your main PPM platform.

There are three common ways to approach a Project Online migration:

If you’re moving to Project Server Subscription Edition, plan how you’ll structure the Content DB (content database) for your project sites and data from the start, since it’s much harder to change later.

Whichever approach you choose, set realistic expectations for migration tools. They can move content quickly, but custom fields, workflows, enterprise calendars, and reporting usually need to be rebuilt or reconfigured by hand. Power Automate can replace many legacy PWA workflows, but they need to be redesigned, not copied.

Power BI reports built on the Project Online OData feed stop working once the data source is gone. Executives usually notice this first, since portfolio reporting and dashboards are often how leadership tracks progress.

Identify the reports that matter most, such as portfolio status, resource capacity, and financial tracking, and rebuild those against your new platform first. This is also a good time to retire reports nobody uses and simplify the ones that remain.

Check what Power BI reporting integration your new platform supports before rebuilding, since data sources and connectors differ between options.

Many Project Online deployments included connected SharePoint project sites holding documents, risk management logs, issues lists, and deliverables. That content doesn’t disappear on its own, but it may no longer be linked to the projects it supported.

Audit these SharePoint sites, decide what to keep, and archive what’s no longer needed. Good governance here also matters for AI tools. Microsoft Copilot can surface old content that users can still access, so leftover project sites with loose permissions can become a risk. For more on this, see our guide to Microsoft 365 security issues we find before every Copilot deployment.

The Project Online retirement is disruptive, but it’s also a chance to rethink how your organization manages projects, resources, and portfolios. Confirm what still works, secure your project data, assess what you really need, and choose a platform that fits how your teams actually work.

Windows Management Experts helps organizations plan, migrate, and support Microsoft Project and SharePoint environments. If you’re not sure where your data stands or which platform is right for you, schedule a consultation with our team and we’ll help you map out your next steps.