Microsoft Project Online Retired on September 30, 2026

Yes: Microsoft Project Online has retired, on the date Microsoft fixed in advance. September 30, 2026. Microsoft confirmed the retirement and announced no extension, no successor upgrade path, and no exception process. If your PMO ran on Project Online, the deadline is behind you. What matters now is what you exported and where it goes next.

This post is the short orientation: what changed on the day, what survived, who was affected, and the three realistic paths forward. The deeper guides for each step are linked throughout; if you only read one page about the retirement before briefing your team, make it this one.

What changed on September 30, 2026

The retirement was a hard cutover, not a gradual wind-down. These all depended on the service:

Everything on the left depended on the same service, so there was no partial mode where the schedules stayed readable but the timesheets stopped. Anything that read it live stopped with it; anything already exported or imported did not.

The full hour-by-hour breakdown of the shutdown sequence is in what actually happened after Project Online retired, and Microsoft's own statement is worth reading in the original for stakeholder conversations.

What this means in practice

Every PMO on Project Online was affected, but not equally. The heaviest impact landed on organizations using the parts of Project Online that have no equivalent in Microsoft's successor products: multi-project portfolios with governance gates, costed timesheets driving billing, the Enterprise Resource Pool, Enterprise Custom Fields with lookup tables, and Power BI dashboards built against the OData feed.

What you exported is what you have. Files you exported still import, with dependencies, custom fields and costs, and a .mpp or Project XML file imported into a new project brings its baseline as a baseline in Onplana. Project Online Data: Import What You Exported covers bringing them in, the free Migration Preview checks a sample file first, and Onplana Schedule opens an exported .mpp. The data export deadline analysis covers what is still recoverable.

There is no in-place upgrade. Microsoft's positioning points customers toward the new Planner, but that is a different product on a different architecture, not an upgrade. Whatever you choose, this is a migration project with an inventory, a destination decision, a pilot, and a cutover.

Your three realistic paths

Three honest options exist, and the right one depends on how your organization actually used Project Online:

1. Microsoft Planner Premium (the rebranded Project for the Web). A real option for teams that used Project Online as a rollup of simple task lists, and a more capable scheduler than it is often given credit for: all four dependency types with lead and lag, a critical path in the timeline view, and a baseline. Where it stops short for schedule-driven PMOs is scale and the layers above a single plan: a 3,000-task ceiling, 10 custom fields, one baseline against Project Online's 11, no enterprise resource pool, no timesheets, and no stage-gate governance. The honest Project Online vs Planner comparison covers the gap feature by feature.
2. A modern PM platform built for the migration. For PMOs that need scale and the enterprise layers (schedules past 3,000 tasks, multiple baselines, a shared resource pool with capacity planning, timesheets, stage-gate governance), the realistic path is a third-party platform that imports your .mpp files and OData exports. Onplana is purpose-built for this case; the broader alternatives roundup scores the market honestly.
3. A custom build. Defensible only for engineering-heavy organizations with genuinely idiosyncratic needs and the appetite to maintain internal tooling for a decade. For everyone else, the build vs buy math rarely favors building.

Where to start now

A standard Project Online migration runs about 12 weeks for a 50-500 project PMO: inventory, evaluate, pilot, cutover prep, cutover, stabilise. Project Online retired on September 30, 2026, so the inventory now covers what you exported, not a live tenant. Do not compress the pilot: a compressed pilot is the single most common cause of failed cutovers.

If you are starting today, three links do most of the work:

• The plan: the 90-day migration plan with weekly checklists and phase gates.
• The inventory: the 35-item migration checklist covering the projects, fields, workflows, and integrations admins most often miss, with a free interactive version.
• The budget: the six-category cost breakdown with a free calculator that produces a CFO-ready estimate.

For the widest view, the complete Project Online migration guide covers the whole journey, and the migration hub is the entry point to every resource. The retirement itself is one of three related Microsoft retirements in 2026; the consolidated retirement timeline maps all three, and the retirement timeline and what stopped working answers the questions this overview deliberately keeps short.

The one-sentence version for your leadership

If you need to compress this entire page into a briefing line: Project Online retired on September 30, 2026, with no extension and no upgrade path; what we exported is what we have, and a standard migration takes twelve weeks, so the work starts from those files now.

The deadline has passed. The only variable now is how well you use what you exported.

---

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.