Tick tock.
You have less than 3 months to plan how you're going to migrate the platform you use to plan. If that doesn't give you at least an uncomfortable smile, you probably haven't fully grasped what's coming.
On September 30, 2026, Microsoft Project Online shuts down. It doesn't degrade, it doesn't enter legacy mode, it doesn't give you a friendly warning banner. It shuts down. Your projects, timelines, assigned resources, and historical reports become inaccessible the next day. And the decision about where you go next, if you haven't made it yet, should have already been made.
What shuts down (and what doesn't, because this confuses everyone)
Pay attention here because there's a common misunderstanding: Microsoft Project as a product is not going away. Only the cloud version, Project Online, is retiring.
The desktop client (Project Professional and Standard) stays alive. Project Server Subscription Edition, the on-premises version, too. What dies on September 30 is the cloud service: Project Web App, cloud portfolio management, workflows, reporting dashboards, resource administration. All of that becomes inaccessible. Not slow, not degraded. Inaccessible.
If your PMO lives in Project Online, the problem is real and the deadline is concrete.
Microsoft had been warning you for years
The official announcement came in September 2025. But the truth is Microsoft had been signaling since 2018 that Project Online wasn't the future. Nobody paid much attention. Old tools have a peculiar inertia: they work well enough not to be touched, until suddenly there's urgency.
The official reason is that Project Online has "legacy architecture" that doesn't allow delivering modern AI-powered experiences. The translation without corporate euphemisms: the code is so old that adding new things on top costs more than starting from scratch. Microsoft chose to start from scratch.
What nobody will tell you in the press release is that this "starting from scratch" means you're the one who has to do the work of moving everything.
The official successor: Planner, which isn't what it used to be
Microsoft proposes Planner as the destination. And here comes the part where you need to make an effort because the naming history of these products deserves its own miniseries.
Look at this table and breathe:
| Current plan | Previous name | Price | Includes Project Desktop | Resource management | Portfolios | Planner Agent (¹) | Available to buy today? |
|---|---|---|---|---|---|---|---|
| Planner Basic | Included in M365 | No additional cost | No | No | No | Yes | Yes |
| Planner Plan 1 | Project Plan 1 / Project Online Essentials | $10/user/month | No | No | No | Yes | Yes |
| Planner and Project Plan 3 | Project Plan 3 / Project Online Professional | $30/user/month | Yes | Yes | Partial | Yes | Yes |
| Planner and Project Plan 5 | Project Plan 5 / Project Online Premium | $55/user/month | Yes | Yes | Full | Yes | No. End of sale: May 2026 |
(¹) Planner Agent requires a Microsoft 365 Copilot license, regardless of your Planner plan.
If you missed it: the company asking you to trust its new project management ecosystem retired its most complete plan two months ago. Welcome to the real analysis.
That said, Planner Premium today is not the Planner from three years ago. It has Gantt, dependencies, baselines, sprints, and portfolios. Plan 3 is genuinely capable for most teams. And the Planner Agent, which Microsoft renamed from "Project Manager Agent" in March 2026, does things that previously required a dedicated PM: generates a plan from a goal, executes tasks, drafts status reports. With M365 Copilot active, of course.
The question nobody asks out loud
What if Plan 3 follows the same path as Plan 5?
The question is legitimate. The pattern exists: Plan 5 dead in May, Project Online Essentials gone before that, and Microsoft's track record of renaming and retiring SKUs in this segment doesn't exactly inspire blind trust.
That doesn't mean Planner is a bad decision. It means the decision has to be made with eyes open:
| If your situation is... | The most direct path | The real risk |
|---|---|---|
| Managing team tasks without complex planning | Planner Basic (already included in M365) | Minimal. This isn't going anywhere |
| Need Gantt, dependencies, and sprints | Planner Plan 1 ($10/user/month) | Low. It's the base plan |
| Used Project Online with the desktop client | Planner and Project Plan 3 ($30/user/month) | Moderate. It's the most direct successor available, but Microsoft's track record warrants monitoring |
| Your PMO depended on portfolio management at scale with Plan 5 | Third-party tool (Planview, Triskell, Smartsheet) | Low: outside the ecosystem, Microsoft's roadmap doesn't affect you |
| Can't afford another forced migration in 2-3 years | Third-party tool or Project Server SE (supported until 2031) | Low: you control the timeline |
The honest recommendation: if your usage is simple, Planner makes sense and the risk is manageable. If your PMO is complex and project management is critical to the business, this moment of forced migration is the perfect opportunity to ask whether Microsoft is still the right bet, without nostalgia or inertia getting in the way.
There's no universal answer. What there is, is a deadline, and it's already running.
Less than 3 months. The minimum plan.
Point one: audit what lives in Project Online. Projects, integrations, connected Power Automate flows, Power BI reports that depend on that data. All of that needs a destination before September 30.
Point two: choose your path before urgency chooses for you. Migrations that are planned in advance cost less and break less. The ones that happen in the last two weeks of September are a different kind of experience.
Point three: start testing the new environment before it's the only one you have.
Migrating from Project Online isn't just a technical exercise. It's the opportunity to redesign how your PMO delivers value, without the architectural debt that Project Online was carrying. Use it well.
The point
Microsoft isn't killing project management. It's closing a version of it that stopped evolving, and transferring the responsibility of the transition to you.
What you do with that transition depends on how much you want to keep depending on their roadmap, and how much you'd rather take control.
Want to stay on top of these changes without tracking 40 different sources? Subscribe to the macareno.net newsletter. One article per week, no noise.
Sources
- Microsoft Project Online is retiring: What you need to know — Microsoft Tech Community
- Frequently asked questions about Microsoft Planner — Microsoft Support
- Microsoft Project Online Retirement 2026: Migration Guide and Alternatives — Epicflow
- Microsoft Project Plan 3 and 5: Name Changes — Schneider.im