Project Server 2019 End of Life: July 14, 2026
Microsoft Project Server 2019 reaches end of extended support on . After that date, no security updates, no bug fixes, no compatibility patches. No Project Server 2026 or 2029 successor has been announced; the on-premises Project Server product line ends with the 2019 release. This page covers what happens at EOL, Microsoft's recommended upgrade path (Project Server SE), sovereignty-aware alternatives, and the overlap with the cloud Project Online retirement that lands two-and-a-half months later.
until Project Server 2019 extended support ends
What end of extended support means
Microsoft's lifecycle policy has two phases: mainstream support (5 years, feature updates + bug fixes + security patches) and extended support (5 more years, security patches only). Project Server 2019's mainstream support ended January 9, 2024; extended support ends July 14, 2026. After that, the product is out of support entirely.
What stops shipping after July 14: security updates for newly discovered vulnerabilities, bug fixes for issues reported after EOL, and any compatibility patches that would otherwise let the product run on newer SQL Server, .NET, or Windows Server versions. Microsoft Defender will continue to detect threats but cannot patch them in Project Server itself.
What does NOT stop: existing installations continue to run on their existing hardware. The binaries don't self-destruct, and your project data stays accessible through PWA. Microsoft does not enforce a technical shutdown the way they do for cloud services. So in the literal sense, you can keep using Project Server 2019 past July 14, 2026 — the cost is that you're doing so with zero vendor backstop on new vulnerabilities.
What this means for regulated industries: running unsupported software past EOL is typically a policy violation. Government (FedRAMP, FISMA, DoD STIGs), defence contracting (NIST SP 800-171, CMMC), healthcare (HIPAA), and financial services (SOX, PCI-DSS) all require that systems handling regulated data run on vendor-supported software. Project Server 2019 after July 14 isn't supported, so any system or person depending on it for regulated workflows triggers an audit finding.
Who's impacted
Three cohorts run Project Server 2019 on-premises today and need a migration plan before July 14, 2026:
Government and defence PMOs
The largest cohort by spend per seat. Federal civilian agencies, state and local government PMOs, defence primes and subs running Project Server 2019 inside FedRAMP, IL2/IL5, or air-gapped environments. Sovereignty and data residency rule out the public Microsoft 365 cloud for most of these, which means Project Online (also retiring) isn't a fallback either. The migration target is either Project Server SE (Microsoft on-prem path) or a self-hosted third-party platform.
Healthcare and life sciences PMOs
Hospital systems, pharmaceutical companies, medical-device manufacturers with HIPAA and FDA 21 CFR Part 11 constraints. Many run Project Server on-premises because their compliance posture predates the cloud-first era, and the migration to a cloud-hosted PM platform requires a full HIPAA Business Associate Agreement (BAA) negotiation cycle. Self-hosted options that stay inside their existing Azure or AWS BAA boundary are typically faster to greenlight than new-vendor cloud SaaS.
Financial services PMOs
Tier-1 banks, insurance carriers, investment management firms running Project Server 2019 for regulated change-control workflows. SOX, PCI-DSS, and jurisdiction-specific banking regulators (OCC, FCA, ECB) require vendor support on regulated systems. Many of these PMOs have already approved cloud migrations for other workloads but kept Project Server on-prem because the migration cost outweighed the benefit. July 14, 2026 changes that math.
Upgrade paths
Microsoft's recommended path is to Project Server Subscription Edition (SE), but it's not the only option. Three honest paths from Project Server 2019:
Project Server Subscription Edition (Microsoft on-prem path)
Project Server SE runs on SharePoint Server SE, the successor to SharePoint Server 2016/2019. The closest like-for-like upgrade from Project Server 2019 with the same on-premises operational model, refreshed Microsoft support lifecycle, and same general feature set. Subscription-licensed rather than perpetual + Software Assurance.
Migration effort: 2 to 6 months for an enterprise PMO with custom solutions, third-party extensions, and Power BI integrations. Not an in-place upgrade — fresh SharePoint Server SE deployment, fresh Project Server SE install, then content database migration and customisation reapply.
Cost note: subscription pricing is not publicly listed. Get a quote from a Microsoft licensing partner. Budget noticeably higher annual cost than the Software Assurance line on the perpetual Project Server 2019 license, the subscription model is the new norm.
Project 2024 LTSC Professional / Project 2024 Professional
The desktop client successor. Single-user planning tool, no PWA, no enterprise resource pool, no portfolio rollup, no governance pipeline. Fits if the Project Server 2019 deployment was mostly used as desktop Project plus a shared SharePoint document library, and the enterprise PPM features weren't load-bearing.
Not a real PMO-grade successor. Microsoft positions it as the desktop-focused alternative; PMOs that actually used Project Server 2019's enterprise features will find Project 2024 LTSC insufficient on its own.
Self-hosted third-party PM platform
The path most regulated PMOs evaluate when the Microsoft subscription cost makes the upgrade math difficult. A self-hosted PM platform runs in your own infrastructure (Azure, AWS, GCP, or on-prem Kubernetes) under your sovereignty boundary, with no vendor cloud dependency.
Onplana's self-hosted Enterprise+ option: ships a Helm chart and Docker Compose stack that deploys inside the customer's environment. The customer holds the data, controls upgrades, and runs the platform entirely under their own compliance posture. Same PMO-grade depth as the cloud-hosted Onplana (enterprise resource pool, costed timesheets, AI risk detection, formal governance) minus the cloud-tenant dependency.
Sovereignty and compliance considerations
Most Project Server 2019 deployments exist because the cloud Project Online wasn't an option for sovereignty or compliance reasons. The July 14, 2026 EOL forces those same shops to re-evaluate the sovereignty question against the new product landscape.
Data residency. Project Server SE inherits the same on-prem residency story as Project Server 2019, the data stays in your data centre. Cloud Project Online (also retiring) operates from Microsoft datacentres in the regions Microsoft 365 supports, which may or may not align with your residency requirements. Self-hosted Onplana inherits whichever cloud or on-prem you deploy it on, full sovereignty control.
Air-gap environments. Project Server 2019 supports fully-disconnected operation. Project Server SE inherits this. Cloud Project Online does not work air-gapped. Self-hosted Onplana runs air-gapped on Kubernetes with internal LDAP/SAML and no external network dependencies.
Audit and certification. Microsoft's on-prem products ride on the certifications of whatever environment you put them in (your FedRAMP authorisation, your HIPAA BAA boundary, etc.). Cloud Project Online rode Microsoft 365's certifications. Self-hosted third-party platforms ride your environment's certifications by the same logic as on-prem Microsoft, which is usually the most familiar audit posture for your compliance team.
Vendor cloud dependency. The strict reading of sovereignty for some regulators (e.g. German BSI, French ANSSI Critical Infrastructure) requires that no foreign-vendor cloud dependency exist in the operational path. Microsoft's on-prem path satisfies this only if the licensing activation doesn't phone home — Project Server SE's subscription activation does require Microsoft connectivity, which can be an issue for the strictest interpretations.
The Project Online cloud overlap
Project Server 2019 EOL on July 14 is followed by the cloud Project Online retirement on September 30, 2026, just two-and-a-half months later. For organisations running both (or planning to use cloud Project Online as the landing pad for an on-prem migration), this is a sequencing trap to avoid.
The trap: migrate from Project Server 2019 to cloud Project Online in May or June 2026 to get off the unsupported on-prem product, then face the cloud Project Online retirement three months later and migrate again. Two migrations in six months at the cost of a single migration. Avoid this entirely by picking your final destination platform up front, not the transitional one.
The honest sequencing:
- Decide the final platform first. Project Server SE (Microsoft on-prem continuation), Planner Premium (Microsoft cloud-light successor for teams that don't need PMO depth), or a third-party platform (self-hosted or SaaS). The /microsoft-retirement-2026 aggregator page has the full decision framework.
- Migrate once, directly to the final platform. Don't bridge through cloud Project Online unless your final platform truly is cloud Project Online (which it can't be, because it's retiring).
- Sequence the cutover around July 14 OR September 30. For Project Server 2019 shops, the July 14 deadline is binding. For shops also running cloud Project Online, the September 30 deadline is binding. Pick the earlier of the two that applies and treat that as your cutover target.
Frequently asked questions
The questions teams ask most often about the Project Server 2019 EOL, embedded as FAQPage schema so they surface in Google's “People Also Ask” feature.
When does Project Server 2019 extended support end?
July 14, 2026, per Microsoft's lifecycle policy for Project Server 2019. The date is published on Microsoft Learn at learn.microsoft.com/lifecycle/products/project-server-2019. Mainstream support ended January 9, 2024; extended support ends July 14, 2026.
What happens after July 14, 2026?
No security updates, no bug fixes, no compatibility patches. Microsoft stops shipping anything for Project Server 2019. Existing installations continue to run on the hardware they're installed on, but they receive zero vendor support, and any new vulnerability discovered after that date is unpatched. For regulated industries (government, defence, healthcare, financial services), running unsupported software past EOL is typically a policy violation that triggers audit findings.
Is there a Project Server 2026 or 2029?
No. Microsoft has not announced a Project Server release after 2019. The on-premises Project Server product line ends with the 2019 release. Microsoft's recommended path for customers wanting Microsoft-brand PPM with on-premises operational characteristics is Project Server Subscription Edition (SE), a subscription-licensed product that runs on SharePoint Server Subscription Edition.
What is Project Server Subscription Edition?
Project Server SE is Microsoft's ongoing on-premises PPM product. It runs on SharePoint Server SE (the successor to SharePoint Server 2016/2019) and ships under a subscription licensing model rather than the traditional perpetual + Software Assurance pattern of Project Server 2019. Feature set is the closest Microsoft offers to a continuation of the Project Server line. Pricing requires direct quoting from a Microsoft licensing partner — there is no public per-seat list price.
Why does the same date apply to SharePoint Server 2016?
Project Server 2019 runs on top of SharePoint Server 2016 — they share the underlying platform. Microsoft aligned the lifecycle dates so the entire on-premises Project Server stack reaches end of extended support in one operations window. If you upgrade, you upgrade both layers together: Project Server SE on SharePoint Server SE.
Can we just upgrade to Project Server SE?
Yes for most workloads, but it is not an in-place upgrade. You need a fresh SharePoint Server SE deployment, then install Project Server SE on top, then migrate the Project Web App content database and customisations. The migration takes 2 to 6 months for a typical enterprise PMO depending on number of custom solutions, third-party extensions, and integrations. Budget the same effort as a major upgrade, not a service-pack install.
What about cloud Project Online — isn't that also retiring?
Yes. Microsoft Project Online (the cloud-hosted PWA, separate from on-premises Project Server) retires September 30, 2026 — about two-and-a-half months after Project Server 2019's extended-support end. For organisations running both (or planning to move from on-prem to cloud as part of the upgrade), the two retirements need to be planned together, see the /microsoft-retirement-2026 aggregator page for the combined timeline.
We can't move to the cloud for sovereignty reasons. What are our options?
Two patterns. First: stay on Microsoft's on-premises path by upgrading to Project Server SE on SharePoint Server SE. Same operational profile as today, refreshed licensing, ongoing vendor support. Second: migrate to a self-hosted third-party PM platform that supports your sovereignty requirements (data residency, air-gap option, BYO-cloud). Onplana ships a self-hosted Enterprise+ deployment option where customers run the entire platform inside their own infrastructure — Azure, AWS, GCP, or on-prem Kubernetes — with no Onplana-hosted dependency.
Self-hosted Onplana for sovereignty-bound PMOs
Project Server 2019 ends July 14, 2026. If sovereignty rules out cloud successors, Onplana's self-hosted Enterprise+ option runs entirely inside your infrastructure with no vendor cloud dependency. Full PMO depth: enterprise resource pool, costed timesheets, AI risk detection, formal governance.