Project Server End of Life vs Project Online: Which Microsoft PPM Has a Future
Project Server end of life: PS 2019 exits support July 14, 2026, 77 days before Project Online retires. What this means for PMOs planning a stopgap move.
The most common misconception about Project Server end of life is that it buys Project Online customers more time. Check the dates before that reasoning gets further than a whiteboard.
Project Server 2019 extended support ends July 14, 2026. Microsoft Project Online retires September 30, 2026. That gap is 77 days. Any organization that migrates from Project Online to Project Server 2019 and considers itself safe for the medium term will discover it landed on a product that was already out of support before its predecessor even retired.
Project Server Subscription Edition is still supported, but it is an entirely different product: on-premises, per-server licensed, requiring dedicated Windows Server and SQL Server infrastructure. For most M365-native organizations, installing an on-premises SharePoint and Project Server stack is not a stopgap; it is a deliberate infrastructure regression.
Project Server 2019 extended support ends July 14, 2026: before Project Online retires on September 30, 2026. Migrating to Project Server 2019 as a stopgap puts you on an unsupported product within weeks of completing the move. Project Server Subscription Edition is still supported but is an on-premises deployment requiring Windows Server, SQL Server, and SharePoint Server. For most Project Online PMOs, the right path is a cloud-native platform that accepts your existing .mpp exports directly and does not require on-premises infrastructure.
The diagram below shows the support windows for both Microsoft PPM server products alongside the Project Online retirement date.
What "Project Server End of Life" Means in Practice
"End of life" means different things depending on the lifecycle policy a product follows. For Project Server 2019, Microsoft uses the Fixed Lifecycle Policy: a defined mainstream support end date followed by an extended support end date. After extended support expires, Microsoft no longer provides security updates, bug fixes, or technical assistance for that product version.
Mainstream support for Project Server 2019 ended January 9, 2024. The product has been receiving security patches only, with no new feature development, since then. According to the Microsoft Lifecycle page for Project Server 2019, extended support ends July 14, 2026. After that date, any security vulnerabilities discovered in the product will not receive patches.
For an on-premises server product hosting your organization's schedule data, baselines, resource pools, and financial reporting, running without security patches is a significant compliance and governance risk. A PMO subject to SOC 2 or ISO 27001 requirements, or operating in a regulated industry, cannot knowingly run unsupported server software against those frameworks.
The impact is not theoretical. A PMO that completes a Project Online to Project Server 2019 migration in Q2 or Q3 2026 lands on an unsupported product within weeks of finishing. The IT team then faces immediate pressure to either upgrade to Project Server Subscription Edition or accelerate another migration.
Project Server 2019 Exits Extended Support Before Project Online Retires
This is the fact that makes "use Project Server as a bridge" collapse as a strategy. When people propose that migration path, they typically picture a multi-year runway. The actual runway from today to Project Server 2019's support end is approximately ten weeks, and it expires before Project Online even shuts down.
If your PMO runs 50 active projects and your migration planning estimate is 12 to 16 weeks, you cannot complete a migration to Project Server 2019 before its extended support ends. And even if you started today, you would be targeting a destination product in its final weeks of patched support.
Running a migration to a product near the end of extended support also creates an immediate follow-on problem. After July 14, 2026, you face a choice: upgrade Project Server 2019 to Subscription Edition, or begin planning yet another migration to a different platform. That is not time purchased; that is a second migration commitment added on top of the first.
The organizations with the cleanest September 30, 2026 migrations are the ones that evaluated this path early and took it off the board.
Project Server Subscription Edition: Still Supported, But a Different Product
Project Server Subscription Edition (PSSE) follows Microsoft's Modern Lifecycle Policy. There is no published retirement date. Microsoft is contractually required to provide at least 12 months of advance notice before any retirement, which makes PSSE a supported platform for the foreseeable future.
That changes the options analysis, but it does not make PSSE a simple choice for Project Online customers. PSSE is fundamentally different from Project Online in terms of deployment model:
- On-premises only. PSSE requires Windows Server, SQL Server, and SharePoint Server. You are trading a zero-infrastructure cloud subscription for a server environment your organization owns and maintains.
- Per-server licensing. Project Online charges per user per month. PSSE uses a per-server license plus user CALs. For a mid-size PMO of 30 to 100 project managers, the actual cost comparison requires a detailed SKU analysis.
- Your team owns patching. Microsoft managed infrastructure and security updates for Project Online. With PSSE, your IT team applies SharePoint cumulative updates, SQL patches, and Windows Server patches on whatever cadence your change management process requires.
- SharePoint Server dependency. PSSE requires SharePoint Server (not SharePoint Online). If your organization is M365-native, you would be introducing an on-premises SharePoint Server footprint specifically to support Project Server.
For organizations that already operate SharePoint Server environments and maintain dedicated on-premises infrastructure teams, PSSE can be a viable long-term platform. For organizations that migrated to Microsoft 365 specifically to eliminate on-premises server maintenance, installing PSSE reverses that posture.
Why the Project Online to Project Server Migration Logic Breaks Down
The reasoning typically sounds like this: "We know the Microsoft stack. We use SharePoint. Project Server is familiar. Let's stay with Microsoft rather than evaluate third-party platforms." That logic is worth examining on three counts.
First, Project Server 2019 does not survive long enough to be a useful bridge. The only supported Microsoft server PPM option is PSSE, which requires on-premises infrastructure. If your organization eliminated on-premises servers to reduce overhead, PSSE reintroduces that overhead.
Second, PSSE shares most of Project Online's architectural characteristics. The parts of Project Online that drive the migration pressure: the aging PWA interface, the OData-dependent reporting model, the manual resource leveling workflow, the absence of any AI-assisted features. PSSE has the same interface and the same reporting model. Moving to PSSE preserves the status quo on infrastructure your team now maintains.
Third, migrating from Project Online to Project Server is not simpler than migrating to a cloud-native platform. You still export data from PWA, map custom fields, migrate resource calendars, and rebuild report consumers. The destination is different; the migration complexity is similar. If you are going to do the migration work, the destination should provide meaningful improvement over where you started.
Before committing to any migration path, use the free Migration Preview tool to map what your current PWA data contains and what different migration targets would actually involve.
Comparing the Microsoft PPM Server Options Side by Side
The decision tree below shows how the Project Server viability analysis plays out for most Project Online PMOs.
| Dimension | Project Online | Project Server 2019 | Project Server SE |
|---|---|---|---|
| Retirement / EOS | September 30, 2026 | July 14, 2026 | No published date |
| Support model | SaaS (Microsoft-managed) | Fixed lifecycle | Modern lifecycle |
| Deployment | Cloud | On-premises | On-premises |
| Infrastructure required | None | Windows Server, SQL Server, SharePoint Server | Windows Server, SQL Server, SharePoint Server |
| Licensing model | Per-user/month subscription | Server license + CALs | Server license + CALs |
| PWA interface | Yes | Yes | Yes |
| OData reporting API | Yes | Yes | Yes |
| Enterprise resource pool | Yes | Yes | Yes |
| AI project features | None | None | None |
| Security patching | Microsoft-managed | Ends July 14, 2026 | Current patches available |
The table shows the core tradeoff directly. If your organization needs continued Microsoft PPM with security support past July 2026, PSSE is the only Microsoft server path. But it comes with an infrastructure requirement and operational overhead that most cloud-first organizations have deliberately moved away from. Neither Microsoft server option includes the AI-assisted scheduling and project creation features that modern cloud platforms provide.
What to Evaluate Before Committing to a Migration Target
Whether you are considering PSSE or a cloud-native platform, the evaluation criteria are the same. Working through them before selecting a destination saves significant rework.
Direct .mpp import. Your project managers saved schedules as .mpp files or can export them from PWA. A destination that reads .mpp files directly saves the field-by-field remapping work. Test this with your actual project files, not a vendor demo.
Enterprise resource pool equivalent. Most Project Online PMOs rely on the ERP for resource availability, multi-project allocation, and capacity planning reports. If the destination does not have a comparable capability, your resource planning workflow will regress after migration.
Custom field migration path. PWA Enterprise Custom Fields are the most common source of scope surprises in Project Online migrations. Run the inventory before selecting a platform. The Project Online migration checklist for 2026 walks through the full pre-migration audit.
Report consumer audit. Every Power BI report, Power Automate flow, or dashboard hitting the OData endpoint will break on retirement day. Map those consumers before selecting a platform, because the destination's data model determines how complex the rebuild is.
Time to cut over. With the September 30, 2026 date fixed, your platform selection needs to leave 12 to 16 weeks for migration execution. If you have not selected a destination platform by mid-June 2026, you are in the late-stage window where emergency consultant rates apply.
Review the full cost analysis for migrating from Project Online before finalizing your platform decision. Organizations that complete Q3 2026 migrations at standard rates start the process now.
The Practical Path Forward
The migrations finishing cleanly before September 30, 2026 are the ones that eliminated the bad options early and committed to a realistic destination. Project Server 2019 is eliminated: its support ends before Project Online retires. Project Server Subscription Edition is technically viable but requires an on-premises infrastructure investment that most M365-native organizations have moved away from.
The realistic options are cloud-native PPM platforms built for the modern enterprise: capable of importing your existing .mpp files, providing an enterprise resource pool equivalent, and offering the AI-assisted scheduling features that Project Online never had.
The Project Online migration guide covers the full end-to-end process for moving your tenant to a cloud platform. The goal by the end of June 2026 is a signed contract with a destination and a migration sprint plan. That leaves three months for execution: enough for a focused PMO.
Run a free Migration Preview Map your Project Online tenant's complexity in 10 minutes and understand exactly what a migration would involve before committing to a platform. No signup required. → Open Migration Preview
Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.
Ready to make the switch?
Start your free Onplana account and import your existing projects in minutes.