Buying Microsoft Project now resembles the kind of assignment for which one might open Microsoft Project. There are dependencies, milestones and a retirement date. A buyer can purchase Project Standard 2024 for a single PC, step up to Project Professional 2024, subscribe to Planner and Project Plan 3, or consider Project Server Subscription Edition. Existing Project Online customers have one more date on the chart: September 30, 2026, when Microsoft says that service will retire.
This does not make Microsoft’s software weak. Project’s scheduling vocabulary remains unusually serious. Standard includes baselines, milestones, critical path, cost management and resource leveling. Professional adds broader resource management, timesheets and a connection to Project Server. The subscription brings the desktop app together with web and Teams experiences, portfolios and advanced dependencies. The problem arrives one level above the feature list. Before a team can plan work, somebody must decide which Microsoft product represents the work.
That is the opening for Smartsheet, Planview and Wrike. None is a universal substitute, and none is free of tiers, add-ons or sales calls. But each tells a more immediate story. Smartsheet starts with a grid. Planview starts with a portfolio. Wrike starts with a workflow. Microsoft starts with a product genealogy.
The price list is an org chart
Microsoft’s US store lists Project Standard 2024 at $679.99 and Professional at $1,129.99, each as a one-time purchase. The company lists Planner and Project Plan 3 at $30 per user per month, paid yearly. Those figures are not clean equivalents. A perpetual desktop license and a cloud subscription answer different questions, include different services and age differently.
The split matters because a software license is also a collaboration policy. Standard is licensed to one user on one PC. A file can still be shared, but the desktop remains the center of gravity. A cloud plan makes access, identity and collaboration part of the service. Project Server gives an organization control, plus the obligation to operate customer-managed infrastructure. These are different operating models wearing one family name.
The expensive part is not always the license. It is the meeting where somebody explains which license keeps the plan authoritative.YesPress analysis
The retirement of Project Online makes that distinction urgent. Microsoft says the change does not affect Project desktop, Project Server or Planner. It also says Project Online-only SKUs stopped being sold to new customers in October 2025. The message is not that Microsoft is leaving project management. It is that the cloud center is moving to Planner while older and on-premises modes remain available. Flexibility survives, but so does the translation work.
Four products, four centers of gravity
Smartsheet’s advantage is not that it has a single SKU. Its pricing page lists Pro, Business, Enterprise and Advanced Work Management. Its advantage is that the interface gives those tiers a common noun: the sheet. A team that understands rows, columns and formulas can begin with a work surface it recognizes, then add dashboards, automation, governance and portfolio layers. This reduces the conceptual cost of adoption, even when commercial complexity grows.
Planview occupies the other end of the telescope. Its broad product family includes Portfolios, AdaptiveWork, ProjectPlace, PPM Pro and more. That lineup is hardly a triumph of minimal naming. Yet Planview organizes the conversation around strategic portfolio management, capacity, investment and governance. It is clearest when executives and a PMO need to decide which work deserves resources, not merely when a project manager needs to adjust a finish date. One revealing exception is ProjectPlace, whose page advertises one pricing plan with unlimited projects, Kanban boards, Gantt charts and roadmaps.
Wrike sits nearer the daily flow of cross-functional work. Requests become tasks; tasks move through custom workflows; teams review, approve and report in the same web environment. Its packaging still needs inspection. Wrike says Business and higher plans are annual, and smaller accounts buy seats in groups of five or ten depending on size. A seven-person team may therefore pay for capacity it does not use. Simplicity in the interface does not repeal procurement arithmetic.
Where each product puts the weight
Editorial assessment, qualitative rather than a feature score
The chart is deliberately a map of emphasis, not a winner’s podium. Microsoft’s desktop scheduling depth is useful when a plan depends on exact task logic, resource leveling and a practiced project manager. Smartsheet’s familiar grid lowers the first step for broad participation. Planview is built to connect investments, capacity and portfolios. Wrike makes repeatable movement across teams visible. A buyer who converts these differences into one total score discards the reason the products differ.
A better way to buy the plan
Begin with the hardest truth the organization must preserve. If one scheduler must maintain a rigorous dependency model, desktop Project may be entirely rational. If dozens of occasional contributors must update status without training as project managers, Smartsheet or Wrike may be easier to sustain. If leadership needs to compare proposed investments against finite skills and budget, Planview earns its heavier footprint.
Choose Microsoft when
Schedule logic, desktop continuity and the Microsoft 365 ecosystem matter more than one simple product boundary.
Choose Smartsheet when
A spreadsheet-familiar surface must grow into dashboards, automation and governed team work.
Choose Planview when
The real object being managed is a portfolio of investments, capacity and strategic trade-offs.
Choose Wrike when
Requests, approvals and cross-team workflows need a shared cloud home with visible ownership.
Then run a pilot that includes the awkward cases. Invite a contractor. Change a baseline. Reassign an overloaded specialist. Ask an executive to read a portfolio view without help. Export the data. Remove a license. Calculate the bill at the actual seat count, including bundles and add-ons. Finally, ask where the authoritative plan lives after six months. A polished demo tends to show the moment a plan is created. Most failures happen later, when responsibility crosses a boundary.
Migration reveals the real product
Project Online customers face a deadline, but migration should not be treated as a bulk copy exercise. A project system contains more than tasks and dates. It carries custom fields, status conventions, permissions, reports, resource pools, integrations and the quiet workarounds people stopped documenting years ago. Moving every artifact can preserve the clutter that made the old system expensive. Moving only the obvious fields can erase the controls that kept it useful.
The sensible first step is an inventory of decisions, not data. Which reports cause leaders to change funding? Which baselines support contracts? Which resource views prevent overcommitment? Which workflows exist only because the current tool made a simple approval difficult? That inventory separates essential institutional memory from software-shaped habit. It also creates a fair test for any replacement. A rival does not need to reproduce every screen. It needs to preserve the decisions that matter and make the rest easier.
Parallel operation deserves suspicion. Running two systems can reduce cutover risk, but it creates two versions of status and a new reconciliation job. Give the overlap a purpose, an owner and an end date. Pick a small set of representative projects, freeze the field mapping, compare outputs and record exceptions. If the pilot expands every week because another team needs one special field, the organization has discovered a governance problem before signing the next contract.
Total cost should include that human layer. Add administration, training, integration maintenance, report building, guest access, premium connectors and the unused seats created by bundle rules. Add the cost of a project manager exporting a weekly slide because executives cannot read the live dashboard. Add the risk of one specialist becoming the only person who understands the portfolio model. A lower license price can fund a surprisingly expensive ritual.
This is where packaging becomes more than marketing. A coherent product boundary tells administrators what they must govern, tells users where to work and tells finance what will renew. When that boundary is blurry, organizations compensate with process. Microsoft has time-tested tools inside its boundary. Its rivals compete by making their preferred boundary easier to see.
Microsoft’s fragmentation can be defended as choice. Perpetual software suits controlled desktops and long-lived file workflows. Subscriptions suit connected teams. Server software suits organizations that need operational control. The trouble is not the existence of those options. It is the cognitive gap between the Microsoft Project name people remember and the set of products they can now buy.
Smartsheet, Planview and Wrike should not be mistaken for frictionless alternatives. Smartsheet can accumulate sheets and automations that need governance. Planview’s breadth can require specialists and deliberate implementation. Wrike gates capabilities and sells seats in bundles. Their lesson for Microsoft is narrower: a buyer should be able to state the product’s center of gravity in a sentence.
Project management software is supposed to expose uncertainty before it becomes cost. The purchasing experience deserves the same discipline. Microsoft still offers a capable scheduling engine and several viable futures around it. The buyer’s first project is choosing which future the rest of the organization can understand.
Common questions
Is Microsoft Project still sold as desktop software?
Yes. Project Standard 2024 and Project Professional 2024 are perpetual purchases licensed for one user on one PC.
When does Project Online retire?
Microsoft says Project Online will retire on September 30, 2026. Project desktop, Project Server and Planner are not included in that retirement.
What is Microsoft’s cloud planning path?
Microsoft is directing cloud project work toward Planner. Planner and Project Plan 3 includes web and Teams apps, portfolios, baselines, critical path, advanced dependencies and the Project desktop app.
Which tool best suits spreadsheet-oriented teams?
Smartsheet offers the most familiar starting surface for teams used to rows and columns. A pilot should still test governance, resource management and reporting needs.
What should buyers test first?
Test the hardest real workflow, actual license count, guest access, integrations, data export, resource conflicts and the path for migration or cancellation.