Blog
Microsoft Project is no longer one simple product. Today, the lineup includes Planner, Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5, Project desktop, Project Server Subscription Edition, and Project Online, which retires on September 30, 2026. Microsoft also moved Project for the web into the broader Planner experience.
That is why the topic gets confusing fast. “Microsoft Project” can mean a lightweight planning app, a browser-based scheduling layer, a desktop scheduler, or an enterprise platform. This guide breaks down the full lineup, covers Project Online retirement, and looks at key alternatives, with practical examples, usage tips, and switching guidance.
The right choice depends on three things: schedule complexity, collaboration needs, and portfolio scale. If you get those three right, the lineup becomes much easier to navigate.
What MS Project tools, apps, and editions include
Microsoft‘s project stack now falls into four practical groups: Planner, Planner premium, Project desktop, and enterprise project platforms. Planner covers lighter teamwork. Planner premium covers modern web-based project scheduling. Project desktop handles deeper scheduling control. Project Server and the retiring Project Online sit on the enterprise side. Microsoft‘s pricing and retirement pages support exactly that layered picture.
That framing matters because the official names are not always intuitive. A buyer can jump from Planner to Plan 3 to Project desktop to Project Online and still not know which layer actually fits the work. This is one of those product families where the brand looks simple from far away and turns into a filing cabinet once you open it.
Example: A department lead running simple internal initiatives in Teams probably needs Planner or Planner Plan 1. A PMO building large schedules with baselines and critical paths is much closer to Project desktop or Plan 3. A portfolio office managing investment priorities and shared capacity is already in Plan 5 or Project Server territory. Microsoft‘s feature pages map neatly to those different use cases.
Are there alternatives to Microsoft Project?
Microsoft Project is not the only serious option. Teams that want lighter collaboration often compare it with tools such as Asana, monday.com, ClickUp, Smartsheet, or Wrike. Teams that need stronger resource planning, portfolio visibility, and financial control may also look at platforms such as Birdview PSA.
The main difference is in the operating model. Microsoft offers broad coverage, but across several layers, from Planner to desktop and enterprise tools. Birdview PSA is easier to position when a team needs projects, resources, and finances in one connected workflow. That does not make one universally better. It means they fit different kinds of work.
Quick comparison of Microsoft Project options and one alternative
A short comparison is more useful than a giant licensing spreadsheet. For most buyers, the real differences come down to control, complexity, and whether they want one connected platform or a broader Microsoft stack.
| Tool | Best for | Main limitation |
| Planner Plan 1 | Lightweight web-based planning | Too limited for advanced portfolio control |
| Planner and Project Plan 3 | Professional project management with desktop support | More complex than lighter planning tools |
| Planner and Project Plan 5 | Enterprise portfolio and resource management | Higher cost and complexity |
| Project Online | Existing legacy Microsoft PPM environments | Retiring on September 30, 2026 |
| Birdview PSA | Teams that need projects, resources, and finances in one place | Less native to the Microsoft ecosystem |
The Microsoft rows above come from Microsoft‘s current Planner and Project pricing pages and retirement notice. The Birdview PSA row reflects Birdview PSA‘s own positioning around unified project, resource, and finance management.
How Microsoft has reorganized the lineup
Microsoft has moved the cloud project story under the Planner brand. The current public lineup is Planner in Microsoft 365, Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5. Microsoft‘s FAQ says that Project Plan 3 and Project Plan 5 were renamed to Planner and Project Plan 3 and Planner and Project Plan 5 on September 18, 2024.
That is not just branding cleanup. It signals a broader shift. Microsoft wants tasks, plans, and projects to sit under one work management umbrella, with more advanced project capabilities appearing in the higher paid tiers. If you still think in the old “Project only” naming, you are reading the current lineup with yesterday‘s labels.
Tip: When evaluating Microsoft‘s current offer, think in layers, not product nostalgia. Ask: do we need basic planning, premium web planning, desktop scheduling, or enterprise portfolio control?
What Planner and Planner premium are for
Planner in Microsoft 365 is the basic layer for team planning and task coordination. Microsoft positions it as a way to manage tasks, to-do lists, plans, and projects across Microsoft 365 apps in one place. It is designed for everyday teamwork more than formal project control.
This option fits teams that need quick adoption, shared task boards, and lightweight planning inside Teams and Microsoft 365. It does not fit teams that need formal schedules, deep dependencies, baselines, or portfolio-level control. In plain English, it is useful for coordination, but not enough for heavier PMO work. That is an inference from Microsoft‘s split between included Planner and the higher paid plans.
Planner premium is the new home for what used to be Project for the web. Microsoft states that Project for the web retired on August 1, 2025, and that its capabilities were transitioned into Planner for the web and Planner in Teams. Microsoft‘s service description also shows those capabilities available through Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5.
That makes Planner premium the real middle ground in the lineup. It is for teams that need timelines, dependencies, and structured web planning without jumping straight to desktop Project.
Example: If a marketing or operations team just needs to track owners, deadlines, and weekly progress inside Teams, basic Planner is often enough. If the same team starts coordinating multi-phase launches with dependencies and timeline pressure, Planner premium is the cleaner next step. Microsoft‘s paid tier structure is built around exactly that jump in complexity.
Tip: Stop asking “Should we buy Project for the web?” Ask “Do we need Planner premium capabilities?” That is the current buying question.
What Plan 1, Plan 3, and Plan 5 actually mean
The paid plans mainly differ in depth of control. Microsoft‘s pricing pages show a clear ladder from premium planning to desktop scheduling and then to enterprise portfolio management. In the current Microsoft pricing shown on the official site, Planner Plan 1 starts at $10/user/month, Planner and Project Plan 3 at $30/user/month, and Planner and Project Plan 5 at $55/user/month, all paid yearly on the US pricing page.
Planner Plan 1 is the lighter paid option. Microsoft describes it with premium templates, reporting, project goals, dependencies, backlogs, and sprints. It works well when teams need better structure than basic Planner, but do not need enterprise portfolio control or the desktop client.
Planner and Project Plan 3 is the practical starting point for many serious PM teams. Microsoft says it includes advanced project management capabilities plus Project desktop and Project Online. That makes it the key option when you need formal schedules, stronger controls, and the desktop app.
Planner and Project Plan 5 sits at the enterprise end. Microsoft says it includes everything in Plan 3 plus portfolio management and enterprise resource allocation. This is where leadership-level prioritization and portfolio tradeoffs come into focus.
Example: A mid-sized delivery team may only need a handful of Plan 3 licenses for schedulers, while most contributors stay in Planner. Buying advanced plans for everyone is a classic way to spend more money without getting more clarity. This is an inference from Microsoft‘s tiered feature model and pricing structure.
When Project desktop and one-time purchase still make sense
Project desktop is still the right tool when you need deep scheduling control. Microsoft continues to include the desktop client in Plan 3 and Plan 5, and Microsoft‘s retirement notice for Project Online explicitly says Project desktop remains available and is not impacted.
This is the better fit for power users who work with baselines, critical path, dense dependency networks, and detailed schedule logic. If your plan is large, sensitive, and tightly controlled, the desktop app still earns its keep. It is still the more practical tool for certain scheduling jobs, even if the broader cloud story now lives under Planner. This is an inference from the features Microsoft reserves for higher tiers and desktop inclusion.
Project Standard 2024 and Project Professional 2024 still make sense when you want on-premises desktop software without subscription dependency. That route is usually better when cloud collaboration is not the priority, the user base is small, or the organization prefers one-time purchase over ongoing licensing. It is less attractive when the team needs shared modern planning across browser, Teams, and portfolio workflows. This is an inference from Microsoft‘s split between perpetual desktop products and cloud plans.
Tip: A perpetual desktop license solves a licensing problem. It does not automatically solve a collaboration problem.
What Project Online and Project Server mean now
Project Online is now a transition product, not a future strategy. Microsoft says new customers could no longer buy Project Online-only SKUs from October 1, 2025, and that the service retires on September 30, 2026. Microsoft also says this does not affect Project desktop or Project Server Subscription Edition.
That changes the conversation. If you still use Project Online, the question is no longer whether it works today. The question is what you are moving to next. Some organizations will shift toward Microsoft Planner and the newer web planning experience. Others, especially those with stronger governance or on-premises requirements, may evaluate Project Server Subscription Edition or another platform altogether. This is an inference from Microsoft‘s retirement notice and unaffected-product list.
Project Server Subscription Edition remains Microsoft‘s on-premises enterprise project and portfolio platform. It matters most for organizations that need tighter infrastructure control, regulated environments, or on-premises governance. If cloud-only work management is not acceptable, Project Server stays in the conversation even as Project Online exits it. This is an inference from Microsoft‘s on-prem versus cloud split and retirement guidance.
Tip: Treat a Project Online move like a real project. Define target state, inventory customizations, classify active and archive-only work, then test the move with one real portfolio before touching everything.
Which MS Project apps matter most in day-to-day work
Most teams do not need one app. They need a workable stack. In Microsoft‘s world, that usually means some mix of Teams, Planner, Planner premium, Project desktop, and reporting tools. Microsoft positions Planner itself as a unified work management experience across Microsoft 365 apps.
A clean everyday setup often looks like this:
- Teams for communication and files
- Planner for daily task coordination
- Planner premium for browser-based project plans
- Project desktop for the most complex schedules
- Reporting through whatever the organization already trusts
Example: A mid-size delivery organization may keep most projects in Planner premium, reserve Project desktop for the few complex programs, and use Teams as the place where the team actually works day to day. That is usually cleaner than trying to force every project into the heaviest tool. This is an inference from Microsoft‘s layered product design.
How to avoid classic MS Project failure modes
Most Microsoft Project problems are not caused by the tool itself. They come from bad fit, bad licensing, or bad operating discipline. The most common problems are license sprawl, file chaos, and resource overload.
License sprawl happens when every user gets the same expensive plan whether they need it or not. File chaos happens when schedules live in emailed files instead of a governed process. Resource overload happens when dates are committed without checking real capacity.
Tip: Separate schedulers from contributors. Not everyone needs Plan 3. Not everyone should touch the master schedule. The more complex the tool, the more damage casual editing can do. This is an inference from Microsoft‘s tiered licensing model and the roles implied by Planner versus Plan 3 and Plan 5.
Example: If six engineers are available next week and the plan assigns eleven parallel “must-do” tasks, the issue is not motivation. It is capacity math. No software can fix that after the commitment is already made.
Birdview PSA as an alternative to Microsoft Project
Birdview PSA is one of the alternatives for teams that need more than planning and scheduling. Microsoft covers a wide range of needs across Planner, Project desktop, and higher-tier plans. But some organizations need stronger visibility into resources, utilization, and financial performance across multiple projects.
That is where Birdview PSA differs from much of Microsoft‘s stack. Microsoft gives you broad coverage, but across several layers. Birdview PSA takes a more unified approach. If your delivery model depends on capacity planning, portfolio visibility, and financial health across multiple projects, a PSA platform can be easier to position than a mix of planning tools.
This matters most for service-based teams. If the work depends not only on schedules, but also on delivery oversight and project financials, a PSA tool can be a better fit than a stack built mainly around planning tools. Birdview PSA can also fit internal teams that need stronger project and portfolio management, resource planning, budgeting, and more structured collaboration and approvals.
How to switch to Birdview PSA
Switching to Birdview PSA works best when it is treated as an operating change, not just a tool change. Start with the essentials: active projects, current resource data, key templates, and the reports teams actually use.
Do not migrate everything. Clean up old plans, remove unused fields, and leave archive-only data behind. A smaller, cleaner migration is usually faster and easier to manage.
A phased rollout is usually the safer path. Start with one team, one portfolio, or one group of active projects. Once the workflows work, expand from there.
Tip: Move current work first. Archive the rest. Most migrations get messy when teams try to carry every old project into the new system.
How to choose the right option
The cleanest decision rule is simple: match the tool to the job. Choose Planner in Microsoft 365 if your team mainly needs lightweight task coordination. Choose Planner Plan 1 if you want structured browser-based planning. Choose Plan 3 if you need formal project management and Project desktop. Choose Plan 5 if you need portfolio and enterprise resource control.
Choose Project desktop or a perpetual desktop edition if your biggest need is deep schedule control. Choose Project Server Subscription Edition if on-premises governance is the real driver. And if you are still on Project Online, treat that as a migration case, not a steady-state plan.
Choose Birdview PSA if the bigger problem is aligning projects, resources, capacity, and financial outcomes in one operating system. That is where a PSA platform starts solving a different problem from a toolset built mainly around planning and scheduling.
Final verdict
Microsoft Project is now best understood as a stack, not a single app. The center of gravity has moved toward Planner and the modern web experience, while Plan 3, Plan 5, and Project desktop still carry the heavier planning and portfolio capabilities. Project Online still exists today, but only until September 30, 2026.
That means the smartest buying question is no longer “Which Microsoft Project edition should I buy?” It is this: Do we need lightweight planning, deep scheduling, enterprise portfolio control, or one platform that connects delivery and financial reality? Once you answer that honestly, the lineup gets much easier to navigate.
FAQ
Is Project for the web still a separate product?
No. Microsoft says Project for the web retired on August 1, 2025, and that its capabilities continue in Microsoft Planner.
When does Project Online retire?
Project Online retires on September 30, 2026. Microsoft also says Project Online-only SKUs stopped being sold to new customers on October 1, 2025.
Does Project Online retirement affect Project desktop?
No. Microsoft explicitly says Project desktop remains available and is not impacted by the Project Online retirement.
Which Microsoft plan includes Project desktop?
Planner and Project Plan 3 and Planner and Project Plan 5 include Project desktop, according to Microsoft‘s current plan pages.
Which option is best for a small team?
For many small teams, Planner in Microsoft 365 or Planner Plan 1 is the cleanest choice. The right pick depends on whether the team needs simple task coordination or more structured web-based project planning.
Which option is best for PMOs or enterprise portfolios?
For organizations managing many initiatives and shared capacity, Planner and Project Plan 5 is Microsoft‘s main cloud portfolio option, while Project Server Subscription Edition is the on-premises enterprise path.
