Project Online to Shut Down September 2026: A Practical Guide to Migrating Your PMO Without Data Loss

Microsoft has confirmed that Project Online will reach end of life on September 30, 2026. The deadline is fixed, and for project management offices (PMOs) that have built their operations around the service’s Project Web App (PWA), the clock is ticking. But as experts and community discussions reveal, simply exporting schedule data won’t be enough—the real work is rethinking how your organization plans, tracks, and governs projects.

The Details: What’s Retiring and When

Microsoft stopped selling new stand-alone Project Online subscriptions on October 1, 2025. After April 1, 2026, you won’t be able to create new Project Online tenants at all. Then, on September 30, 2026, the service itself will shut down. These dates come straight from Microsoft’s official documentation and a Tech Community blog post detailed the roadmap.

What’s affected? Only the cloud-based Project Online service—not Project desktop applications, not Project Server Subscription Edition, and not Microsoft Planner. If your organization uses Project Online Desktop Client (the subscription version of Project Professional) that’s also tied to the service, you’ll need to transition that license to a different Project plan to keep the desktop app.

The recommended replacement is Planner premium, Microsoft’s modern task-and-plan management tool. But the company explicitly states that Planner premium is not a one-to-one feature replacement for PWA. Core gaps include cross-project dependencies, enterprise capacity planning, bulk operations across multiple schedules, custom workflows, and deeply integrated reporting. For those capabilities, Microsoft points to the Power Platform—Dataverse, Power Apps, Power Automate, and Power BI—which means building a custom solution.

Which PMO Are You? Matching Your Needs to a Migration Path

How painful this transition will be depends entirely on what your organization actually does with Project Online. Use this decision matrix to gauge your situation:

The real pain comes from four areas that Planner premium doesn’t handle out of the box: managing resource capacity across multiple projects, understanding how a delay in one project impacts another, applying stage‑gate approvals automatically, and consolidating portfolio‑level reports. If your organization depends on these, you’ll need a developer‑led effort to recreate them on Dataverse or to switch to a third‑party tool.

Don’t overlook the non‑schedule data. As first reported by WindowsForum, exporting PWA schedule data alone does not preserve the full working project record. You also need a plan for linked SharePoint project sites (documents, risks, issues, deliverables, lists, permissions), historical reports, workflow evidence, integration records, and any custom configurations that enforce governance. Without these, you lose the context that explains why projects turned out the way they did.

From Server to Cloud: A Brief History

Project Online launched in the early 2010s as Microsoft’s browser‑based project portfolio management service, essentially a cloud‑hosted version of Project Server. It gave organizations a centralized PWA to manage portfolios, resources, timesheets, and reporting. But while the desktop Project client kept evolving, Project Online remained tied to an older architecture.

Around 2019, Microsoft introduced Project for the web (built on the Power Platform) and rebranded Planner as part of a push toward modern, collaborative work management. The writing has been on the wall since then. In 2023, new Planner premium features started converging task management, goals, and projects into a single experience. The October 2025 sales halt for Project Online made the retirement official, and the Tech Community blog spelled out that Planner premium is the strategic direction—even if it doesn’t cover every enterprise scenario yet.

Your Pre‑Retirement Action Plan

Start now, not six months before the deadline. A hasty migration risks broken processes, missing historical records, and PMO chaos. Here’s a five‑step playbook.

Step 1: Take an Honest Inventory

Before you choose a destination, you must know what’s really living inside your PWA. Create a detailed inventory with these categories:

• PWA configuration: custom fields, lookup tables, calendars, project types, security groups, views, filters, workflows, timesheet settings, operational policies. For each item, record a business owner who can explain its purpose.
• Projects and schedules: a register of every project—name, status, last update, linked SharePoint site, key dependencies, required reports. Classify each as active, closing, or historical.
• Linked SharePoint content: for each project site, inventory document libraries, risk/issue lists, deliverables, permissions, retention labels. Note which content must remain searchable after retirement.
• Reports and data connections: OData feeds, Power BI datasets, Excel workbooks connected to Project Online, scheduled refreshes, API scripts, downstream integrations. Identify what feeds the board deck or compliance filings.
• Workflow and approval history: intake approvals, stage‑gate decisions, escalations. What evidence must be kept for audit?

Get sign‑off from the PMO director, IT admins, records manager, and any integration owners. A PWA admin knows what’s configured, but only a business owner can say whether a Power BI report drives a monthly executive decision or whether a SharePoint library is subject to a legal hold.

Step 2: Choose Your Destination Platform

Use the matrix earlier to narrow options. Then, require a formal scored comparison for every candidate (Planner premium, Power Platform rebuild, Project Server Subscription Edition, third‑party PPM tools). Score each against:

• Cross-project dependency management
• Capacity planning and resource analysis
• Bulk operations (multi‑project updates, mass status changes)
• Workflow and approvals
• Reporting fidelity and historical report preservation
• Integration with your existing systems
• Records retention and archive accessibility
• Administration, security, and total cost of ownership

For each row, assign a named business owner and technical owner who can mark the requirement “pass,” “fail,” or “requires redesign.” If Planner premium fails on cross‑project dependencies, for example, your resource management lead must confirm that gap and either accept the risk or sponsor a Power Platform rebuild. Do not assume that importing schedules into a new tool equals functional equivalency.

Step 3: Pilot with a Real Project

Don’t test with a dummy. Pick one representative active project—preferably one with named resources, dependencies, governance checkpoints, and typical reporting demands. Define pass/fail criteria up front:

• Can project managers maintain the schedule and task detail they need?
• Can teams provide the status information leadership requires?
• Can the PMO produce required reports without manual reconciliation?
• Do approvals and controls operate through an agreed process?
• Can support staff administer access, ownership changes, and reporting?
• Can the organization find and interpret the project’s historical record after cutover?

If the pilot only proves that users can enter tasks, it hasn’t validated your operational model. For capabilities that Planner premium can’t deliver, explicitly decide which PWA behaviors you’ll retire, which you’ll redesign, and which demand a different platform entirely.

Step 4: Archive Everything That Matters

An archive is not a spreadsheet dump. For every closing or historical project, preserve:

• The schedule record (tasks, milestones, dates, assignments, dependencies) with metadata.
• Linked SharePoint project‑site content—or an approved records copy that meets legal and compliance needs.
• Retention labels, hold status, and access restrictions.
• Workflow decisions, approval records, and key report snapshots.

Create an archive index that links each project’s identifier to its schedule export, SharePoint location, report history, and responsible record owner. Test restoration: ask someone who didn’t build the archive to find a specific project, open its preserved schedule and documents, and confirm permissions work. Assign one named archive owner and a deputy; they’ll be the contact for access requests after shutdown.

Step 5: Execute a Phased Cutover

Work backward from September 30, 2026. A sample timeline (compress phases if you’re starting late):

• Inventory sign‑off: complete and have all stakeholders approve the detailed inventory.
• Pilot completion: finish a representative pilot for your chosen platform(s) and document results.
• Archive validation: classify all projects; preserve historical records; test retrieval.
• Wave cutover: move active projects in planned groups, retrain users, redirect integrations. Keep a cutover log for every dependency.
• Shutdown rehearsal: simulate losing Project Online access. Confirm archive retrieval, report replacements, and support readiness.
• September 30, 2026: execute final access removal, wrap up communications, and close the books.

Throughout this process, remember: the retirement is not just a technical event. It’s a chance to streamline burdensome processes and clarify what your PMO truly needs to govern effectively. Some legacy workflows may no longer be worth rebuilding.

Looking Ahead: The Post‑Project Online World

Once Project Online goes dark, Microsoft’s project management story will center on Planner premium, Project for the web, and the Power Platform ecosystem. For many teams, this modern stack will be more intuitive and tightly woven into Microsoft 365. But for enterprise PMOs, the gap between the old and new worlds means the next 18 months will be a period of intense adaptation.

Expect third‑party migration tools to mature, and watch for additional guidance from Microsoft as the deadline nears. Organizations that invest in proper inventories, realistic pilots, and thorough archives will not only survive the transition—they might even find they’ve built a better project management foundation on the other side.