We Built PPMX Because Our Clients Deserved Better Than Another Microsoft Pivot
After 17 years implementing Project Server and Project Online for enterprise organizations, EPMA didn’t wait for Microsoft to announce a replacement. We built one.
On September 30, 2026, Microsoft will retire Project Online.
Not sunset it gradually. Not keep it in maintenance mode. Retire it. The service will shut down. Your data will no longer be available. The platform that thousands of organizations have built their project portfolio management practices around will simply be gone.
Microsoft’s recommended path forward is Planner. If you’ve used Planner, you already know what that means. It’s a task management tool. It’s useful for what it is. But it is not enterprise PPM. It does not do portfolio-level resource capacity planning. It does not do financial governance across a program portfolio. It does not connect project execution to organizational strategy.
For organizations that were using Project Online for its actual purpose, managing complex portfolios of work, allocating resources intelligently, tracking financial performance at the program level, aligning project investments to business outcomes. Microsoft’s answer is not an answer.
EPMA saw this coming. And we didn’t wait.
Why EPMA Built PPMX – The Honest Version
EPMA has been a Microsoft Gold Partner in project and portfolio management for over 15 years. We implemented Project Server and Project Online for organizations ranging from mid-market to Fortune 500. We know what it does well. We also know exactly what it doesn’t do, what workarounds our clients built around its limitations, and what they always wished it could be.
When Microsoft announced Project Online’s retirement in September 2025 with no meaningful replacement for organizations that genuinely needed enterprise PPM we made a decision. We had built the first version of PPMX in 2013, a layer on top of Project Server that made enterprise governance actually usable. Microsoft designated us a competitor and we stepped back. We spent the next decade becoming the best Project Online implementation partner in the industry instead.
But now the platform is going away, and Planner is not the answer. So we built PPMX again, completely standalone, no Microsoft product required to run it, no Microsoft roadmap decision that can affect your operations. The version we always wanted to build.
This isn’t a product launch. It’s the answer we built before the deadline because our clients are going to need it.
Every feature in PPMX came from a real problem we watched real organizations struggle with on Project Online. The guided status report wizard exists because EPMA watched project managers spend 45 minutes on inconsistent weekly reports while PMO directors received data they couldn’t trust. The resource heatmap exists because EPMA watched resource managers make allocation decisions based on spreadsheets and gut feel while the actual capacity data sat inaccessible across dozens of projects. The strategic priorities module exists because EPMA watched boards ask ‘is our project portfolio actually delivering on our strategy?’ and watched PMO directors struggle to answer.
None of those features came from a product roadmap meeting. They came from 17 years of being inside the problem.
What PPMX Actually Is
PPMX is an enterprise project and portfolio management platform built specifically for mid-market organizations that need serious governance capabilities without the implementation nightmare that comes with enterprise-tier tools like Planview or Clarity.
It is not a task management tool dressed up as PPM. It is not another Microsoft add-on that will be at the mercy of the next Microsoft pivot. It is a purpose-built, standalone platform that covers the full spectrum of what a mature PMO actually requires:
- Portfolio visibility – every active project, resource, risk, and approval in a single role-based dashboard. Project managers see what’s relevant to their work. Executives see what’s relevant to theirs. The same system, completely different experiences.
- Resource intelligence – a color-coded heatmap showing workload across every team member across every project simultaneously. Green means balanced. Amber means near capacity. Red means overloaded. No more spreadsheet guesswork. No more finding out someone is over-allocated after the commitment has already been made.
- Guided governance – a status report wizard that walks every project manager through risks, issues, budget, tasks, and team health in a structured sequence. Nothing gets missed. Every report is complete. Every report is consistent. Governance that happens because the tool makes it the path of least resistance, not because someone is enforcing it.
- Financial oversight – budget forecasting, actuals tracking, burn rate, and variance analysis across the entire portfolio in real time. Know where every dollar is going before it’s gone.
- Strategic alignment – every project connected directly to a business objective. Revenue growth, risk reduction, margin improvement. See in real time whether your portfolio is actually delivering on what your organization committed to.
- Skills and workforce development – resource allocation by specific skills, not just job titles. Find the C# developer with AI experience across your entire organization instantly. Give team members a place to track development goals and map their growth.
The Migration Decision Is More Consequential Than It Looks
Most organizations are treating the Project Online retirement as a technology swap. Find a tool, migrate the data, retrain the team, move on.
The organizations that will come out of this transition significantly better are the ones treating it as something more: a forced opportunity to build the portfolio management infrastructure they should have had years ago.
Before any migration decision, there’s a question worth asking honestly: where are your projects actually living right now? Not where they’re supposed to live, where are they actually living? For most organizations, the honest answer is: in Project Online, and also in Jira for the engineering teams, and Smartsheet for the operations group, and Azure DevOps for software development, and Excel spreadsheets that have been running for years, and email threads that nobody can search.
That fragmentation is normal. It’s also invisible until you try to answer a question like: across everything our organization is working on right now, do we have the capacity to deliver it? Or: what is our total project investment and what return are we getting?
A migration that moves what’s in Project Online to a new platform without addressing that fragmentation just creates a cleaner version of the same incomplete picture.
“The organizations making good migration decisions right now aren’t just asking ‘what tool do we move to.’ They’re asking ‘what should our portfolio management infrastructure actually look like and how do we build it?”
Parthiv Bhuta
Vice President
PPMX can integrate with the tools teams are already using. Engineering teams in Jira, operations teams in Smartsheet, development teams in Azure DevOps. That data comes into PPMX at the portfolio level. Teams keep their execution tools. Leadership gets the single view of the portfolio they’ve never had before because the data was scattered.
This isn’t just a project management best practice. It’s the foundational investment that makes AI-assisted project management actually possible. AI works on data. Fragmented data produces incomplete insights. Centralized, real-time portfolio data is what makes Avery – PPMX’s built-in AI guide – actually useful rather than aspirational.
Two Paths Forward
PPMX is available in two configurations, designed for the reality that not every organization needs the same thing.
PPMX SaaS is for mid-market organizations ready to move quickly. Cloud-hosted, full enterprise PPM out of the box, operational in 6 to 8 weeks. Three pricing tiers: Starter, Professional, and Enterprise, based on user count, starting at $45 per user per month. No year-long implementation. No army of consultants. A clean deployment by a team that has done this hundreds of times.
PPMX Enterprise Custom is for organizations with genuinely specific requirements that off-the-shelf tools don’t serve well. The frustration of tools that almost fit, requiring expensive workarounds, process compromises, or custom development that costs a year and still doesn’t quite work, is a real and common problem. PPMX Enterprise Custom uses the full PPMX platform as the foundation and builds custom modules on top for what makes your organization unique. You get 17 years of proven enterprise PPM capability out of the box, plus the specific governance workflows, reporting structures, and integrations your organization actually requires.
Both paths include implementation support from EPMA’s consulting team, the same team that has been doing this for 17 years. The software and the expertise are not separate products. They were built to work together.
The Deadline Is Real
September 30, 2026 is not a soft deadline. The service will shut down. Enterprise migrations take 6 to 8 weeks minimum under normal conditions. Organizations that wait until summer will be competing for implementation resources that are already booking up, paying premium rates for compressed timelines, and risking disruption to active projects during the transition.
The organizations moving now are getting priority scheduling, thoughtful implementations, and the time to approach the transition as the governance reset opportunity it actually is rather than a scramble to get something, anything, live before the service goes dark.
SharePoint 2013 workflows, which many Project Online environments depend on, have already ended as of April 2, 2026. The transition has already begun.
A Final Note
EPMA built PPMX because 17 years of implementing enterprise project management taught us exactly what organizations need and exactly where every existing option falls short. This is not software built from a product roadmap or a whiteboard. It is software built from the experience of a consulting firm that has been inside the problem for nearly two decades.
We succeed when our clients succeed. That is not a tagline. It is the operating principle that produced a 100% project success rate across 17 years of enterprise engagements. It is the principle behind every design decision in PPMX.
If you are navigating the Project Online transition and want a real conversation about your options – not a sales pitch, just an honest assessment of your situation, We are here for that conversation.
Learn More at PPMX.Ai
Book a conversation with PPMX
Frequently Asked Questions
What is Microsoft's Project Online replacement?
Microsoft's recommended path is Planner, which is a task management tool rather than enterprise project portfolio management. Microsoft set September 30, 2026 as Project Online's retirement date. Organizations that used Project Online for portfolio-level resource planning, financial governance, and strategic alignment need a PPM platform built for those capabilities.
Is Microsoft Planner a replacement for Project Online?
Not for portfolio management. Planner is useful for organizing tasks and team work, but it does not do portfolio-level resource capacity planning, financial governance across programs, or connect project work to organizational strategy. If your PMO relied on Project Online for those capabilities, Planner leaves a gap.
What happens to Project Online data after retirement?
Once the service shuts down, the data in it is no longer available. The retirement is a full shutdown, not a move into maintenance mode. Project data, resource assignments, and custom fields have to be moved or exported before the September 30, 2026 retirement date.
What is PPMX?
PPMX is a standalone enterprise project and portfolio management platform built by EPMA for mid-market organizations. It covers portfolio visibility, resource capacity heatmaps, guided status reporting, financial oversight, strategic alignment, and skills-based resource allocation. It runs without any Microsoft product and was built from 17 years of implementing Project Server and Project Online.
How long does it take to implement PPMX?
PPMX SaaS is typically operational in 6 to 8 weeks. PPMX Enterprise Custom builds additional modules on top of the platform for organizations with specific governance, reporting, or integration requirements, so its timeline depends on scope. Both include implementation support from EPMA's consulting team.
About the Author
Avery is the AI guide built into PPMX by EPMA. She draws on 17 years of enterprise project management consulting knowledge to help organizations make better portfolio decisions. This post reflects EPMA’s institutional perspective on the Project Online transition.