Software End of Life 2026: The Complete EOL Calendar

2026 is an unusually dense year for software end-of-life events. Dozens of enterprise-grade products — from operating systems and databases to runtimes and productivity suites — lose security patches or shut down entirely, most between April and October.

Two definitions separate these events. End of support means the software keeps running but stops receiving security fixes, bug fixes, or vendor help. Retirement is harsher: the vendor turns the service off. That distinction matters in 2026 because a server like SharePoint 2019 can still boot after July 14, but Project Online becomes completely inaccessible after September 30. (learn.microsoft.com)

Every entry below has been verified against vendor documentation. We will update this page as dates shift or new EOL announcements drop.

For a deep dive into the Microsoft-specific stack (SharePoint, Exchange, OOS), see our Microsoft 2026 End-of-Support Timeline.

Operating Systems & Infrastructure EOL Calendar

Operating system EOLs carry the highest blast radius. An unpatched OS exposes every workload running on it, regardless of how current the application layer is.

Product	EOL / Support End Date	Impact	Migration Path
Windows Server 2012 / 2012 R2 (ESU Year 3)	October 13, 2026	Final paid ESU window closes; no further security patches from Microsoft at any price	Upgrade to Windows Server 2022/2025 or migrate to Azure VMs (free ESUs as a bridge)
Windows 10 (consumer ESU)	October 13, 2026	One-year paid ESU program ends for home users	Upgrade to Windows 11 or purchase compatible hardware
Debian 11 "Bullseye" (LTS)	August 31, 2026	LTS patches stop permanently — silently affects Docker base images and CI runners	Rebase to Debian 12 "Bookworm" (debian:bookworm-slim)
Debian 12 "Bookworm" (regular support)	June 10, 2026	Regular security support ends; transitions to LTS only	Upgrade to Debian 13 or switch to Bookworm LTS
SUSE Linux Enterprise 15 SP4	December 31, 2026	LTSS ends	Migrate to SP5 or SP6

Microsoft officially ended standard support for Windows Server 2012 and 2012 R2 in October 2023. Organizations that purchased Extended Security Updates bought themselves three additional years. ESU Year 3 — the final year — ends October 13, 2026. After that date, Microsoft will not provide security updates for on-premise deployments at any price. (learn.microsoft.com)

If you need short-term runway, Microsoft offers free ESUs for workloads running in Azure. That is a bridge, not a strategy. If you are running legacy applications that cannot migrate to Windows Server 2022, you must containerize those workloads or refactor them for a modern cloud environment before Q3 2026.

There are fewer true Linux OS cliffs in 2026 than many teams expect. Ubuntu 22.04 LTS runs until May 2027, and RHEL 9 is supported well past 2026. The real Linux fire drill is Debian 11. (ubuntu.com)

One common misread: Windows Server 2022 mainstream support ends October 13, 2026, but extended support continues. Do not spend urgent migration budget there first. Windows Server 2016, however, hits extended support end on January 12, 2027 — only three months past the 2026 boundary. If you are still running it, plan the upgrade now. (learn.microsoft.com)

Database Deprecations in 2026

Database EOLs are uniquely dangerous because upgrade paths often involve schema changes, driver compatibility issues, and replication topology reconfiguration. Treat these as data engineering projects, not version bumps.

Product	EOL Date	Impact	Migration Path
MySQL 8.0	April 2026	Moves to Sustaining Support; no more security patches or bug fixes from Oracle	Upgrade to MySQL 8.4 LTS (supported through 2032) (mysql.com)
Amazon RDS for MySQL 8.0	July 31, 2026 (standard support)	Auto-enrollment in paid RDS Extended Support after this date	Upgrade to MySQL 8.4 on RDS before August to avoid per-vCPU-hour surcharges
MariaDB 10.6	July 6, 2026	Community security and bug-fix window closes	Upgrade to MariaDB 11.4 LTS (mariadb.com)
SQL Server 2016	July 14, 2026	Extended support ends; ESU Year 1 starts the next day	Target SQL Server 2022 or Azure SQL Managed Instance before ESU pricing becomes the default (learn.microsoft.com)
PostgreSQL 14	November 12, 2026	Final minor release, then unsupported	Upgrade to PostgreSQL 16 or 17 via pg_upgrade or dump/reload (postgresql.org)
IBM Db2 11.1 LUW	April 30, 2026	Extended support window closes	Upgrade to Db2 11.5 or 12.1

MySQL 8.0 is the highest-profile database EOL this year. MySQL 8.0.x Community Edition is a landmark version reaching end of life in April 2026. Oracle will not be releasing any additional updates for this MySQL version. Oracle has split MySQL into Innovation releases (short-lived, feature-heavy) and LTS releases (long-term support). The recommended target is MySQL 8.4 LTS, which receives patches through 2032. MySQL 8.4 is a Long-Term Support release with patches through 2032.

This is not a drop-in replacement. MySQL 8.4 deprecates older authentication plugins (like mysql_native_password) and changes default replication behaviors. Your engineering team must audit application connection strings and driver compatibility before executing the upgrade.

AWS moves MySQL 8.0 into RDS Extended Support by the end of July 2026. Starting in August, those continuing to run MySQL 8.0 will be auto-enrolled into a paid support tier with an additional fee per vCPU-hour. If you are on RDS, upgrade before August to avoid the surcharge.

Programming Languages & Runtimes EOL in 2026

Runtime EOLs hit differently than infrastructure EOLs. The software keeps running, but your supply chain quietly decays: packages drop CI support, CVE fixes only ship for supported versions, and compliance scanners start flagging.

Product	EOL Date	Impact	Migration Path
Node.js 20	April 30, 2026	No more security patches from the Node.js project	Upgrade to Node.js 22 LTS or Node.js 24 for longer runway
Ruby 3.2	April 1, 2026	Security maintenance ends	Upgrade to Ruby 3.3 or 3.4; retest gems with native extensions (ruby-lang.org)
Jenkins Java 17 support	March 31, 2026	No new Jenkins controller releases supporting Java 17	Move Jenkins environments to Java 21 (community.jenkins.io)
Python 3.10	October 2026	Upstream security-fix window ends	Upgrade to Python 3.12+ (peps.python.org)
.NET 8 (LTS)	November 10, 2026	End of support	Plan new projects on .NET 10; .NET 9 (STS) also expires in 2026 (dotnet.microsoft.com)
PHP 8.2	December 31, 2026	Security support ends	Target PHP 8.3 or 8.4; test deprecated behavior early (php.net)

Node.js 20 EOL Timeline

Node.js 20 reaches end of life on April 30, 2026. For a version that entered Active LTS in October 2023, it has seen broad adoption in production environments. However, from May 1, 2026, any vulnerability discovered in Node.js 20 won't receive an official patch.

Because Node.js heavily relies on the npm ecosystem, upgrading the core runtime requires auditing third-party packages for compatibility with newer V8 engine features and updated native modules.

On AWS Lambda, the deprecation follows a three-phase schedule: Phase 1 (April 30, 2026) — security patches stop and the runtime disappears from the AWS Console. Phase 2 (August 31) blocks function creation, and Phase 3 (September 30) blocks function updates. Migrate Lambda functions to nodejs22.x before Phase 2.

For teams that cannot upgrade immediately, migrating directly to Node.js v24 is worth considering. While Node.js v22 is a solid release, it is scheduled to reach End of Life in April 2027, which makes v24 the better long-term target for most teams.

Java 17 Is Not Universally EOL — but Jenkins Is Moving On

This is where generic EOL roundups get sloppy. Saying "Java 17 ends in 2026" is wrong as a blanket statement. Oracle's roadmap keeps Java 17 supported through September 2029. (oracle.com)

The real issue is toolchain-specific. The Jenkins project will not release new controller versions supporting Java 17 after March 31, 2026. If your CI/CD pipelines rely on Jenkins, you must upgrade your controller environments to Java 21 before that deadline to continue receiving security patches for your build infrastructure.

For Node, Python, PHP, and .NET, the safer operating pattern: upgrade the runtime and the build image together, then rerun dependency, test, and TLS checks in the same sprint. Teams that patch only the app version and ignore the base image usually discover the second breakage later, under deadline pressure.

Enterprise Applications & Productivity Retirements

Enterprise app retirements have the widest organizational impact because they affect business processes, not just infrastructure. Several 2026 deadlines are hard retirements — the service becomes inaccessible, not just unsupported.

Product	EOL / Retirement Date	Impact	Migration Path
Dynamics CRM 2016 (v8.2)	January 13, 2026	Extended support ended	Migrate to Dynamics 365 Online (learn.microsoft.com)
Microsoft ATA 1.x	January 13, 2026	Final release support ends	Retire ATA sensors; rebuild on Defender for Identity (learn.microsoft.com)
SharePoint Add-ins / Azure ACS	April 2, 2026	Add-ins stop working; Azure ACS principals stop working for SharePoint Online	Replace with SPFx and modern auth (learn.microsoft.com)
SharePoint 2013 workflows	April 2, 2026	Removed from existing Microsoft 365 tenants	Rebuild in Power Automate (learn.microsoft.com)
Dynamics NAV 2016	April 14, 2026	Extended support ends	Migrate to Business Central (learn.microsoft.com)
Exchange Server 2016/2019 ESU	April–October 2026	Official support ended October 2025; ESU bridge expires in 2026	Migrate to Exchange Online or Exchange Server Subscription Edition
QuickBooks Desktop 2023	May 31, 2026	Payroll, payments, bank feeds, support, and security updates stop	Export financial data and migrate (quickbooks.intuit.com)
SharePoint Server 2016 / 2019	July 14, 2026	Extended support ends	Migrate to SharePoint Online or SharePoint Server Subscription Edition (learn.microsoft.com)
Project Server 2016 / 2019	July 14, 2026	Extended support ends	Upgrade to Subscription Edition or exit to Planner/another PPM stack (learn.microsoft.com)
Dynamics GP 2016 / 2016 R2	July 14, 2026	Extended support ends	Plan exit with reporting history preserved (learn.microsoft.com)
InfoPath 2013 / SharePoint Designer 2013	July 14, 2026	Long-extended support window closes	Replace forms and workflow editing with modern tooling (learn.microsoft.com)
SAP Commerce on-prem (2205)	July 31, 2026	Mainstream maintenance ends; no new support packs or third-party library updates	Migrate to SAP Commerce Cloud (help.sap.com)
Microsoft Project Online	September 30, 2026	Hard retirement — projects and data become inaccessible	Migrate to Planner Premium, Project Server SE, or third-party PPM
EWS in Exchange Online	October 1, 2026 (phased); April 1, 2027 (permanent)	EWS requests start getting blocked (techcommunity.microsoft.com)	Migrate integrations to Microsoft Graph API
Office LTSC 2021	October 13, 2026	No more security updates, bug fixes, or support; no ESU available	Upgrade to Microsoft 365 Apps or Office LTSC 2024
Visio LTSC 2021 / Project LTSC 2021	October 13, 2026	Same as Office LTSC 2021	Upgrade to LTSC 2024 versions or Microsoft 365
Office Online Server	December 2026	Product retires	Migrate to Office for the web (Microsoft 365) (learn.microsoft.com)

Project Online: The Hardest Stop

Unlike on-premise software that simply stops receiving patches, Project Online is a hard retirement. Microsoft officially announced that Project Online retirement will take place on 30 September 2026. From this date, users will have no access to their data and projects.

Organizations must migrate project data, resource allocations, and custom fields to Planner Premium (formerly Project for the Web), Project Server Subscription Edition, or a third-party PPM solution. Because the underlying data structures between Project Online and Planner Premium are fundamentally different, this requires a custom data mapping strategy. If you wait until Q3 to think about data mapping, historical reporting, and downstream integrations, you are already late.

Read our full technical breakdown in our Microsoft Project Online Retiring Sept 2026 guide.

Exchange Server: Already Past End of Support

Both Exchange 2016 and 2019 are out of support since October 2025. Microsoft created a "Period 2" Exchange Server ESU program lasting from May 2026 through October 2026. There will be no further extensions after that.

If you are still running on-premise Exchange, your migration window is closing fast. Unpatched Exchange servers remain high-value targets for the next iteration of ProxyLogon or ProxyShell exploits. For a detailed risk analysis, see our Exchange 2016 end-of-support breakdown.

Office LTSC 2021: No ESU Safety Net

Office LTSC 2021 will reach end of support on October 13, 2026. After this date, Microsoft will no longer provide technical support, bug fixes, or security updates. Unlike Windows Server or Exchange, there are no Extended Security Updates (ESU) for Office LTSC 2021 — it is a hard cutoff. Your options are Microsoft 365 Apps (cloud) or Office LTSC 2024 (on-premises, supported until 2029).

The Extension Model Dies Before the Core Platform

The pattern that kills migration plans: the extension model often dies before the core platform. SharePoint Add-ins, Azure ACS, and SharePoint 2013 workflows retire in April, months before SharePoint Server 2016 and 2019 hit July. Office Online Server retires at year-end, but Power BI Report Server users lose supported OOS configuration earlier.

For SharePoint Add-in retirement details, see our SharePoint Add-ins April 2026 migration guide. For SaaS teams relying on EWS for email integration, see our EWS to Microsoft Graph migration guide. For legacy Microsoft ERPs, see our Dynamics 365 On-Premise End of Life guide. For SAP Hybris migration planning, see our SAP Hybris end-of-life migration framework.

The "Do Nothing" Tax: Security, Compliance, and Cost

Every month you run past an EOL date, three costs compound:

1. Unpatched CVE exposure grows linearly. Vulnerability researchers do not stop finding bugs in EOL software — they stop fixing them. MySQL 8.0, for example, averaged 15–20 CVEs per year during its supported life. Those will keep coming, without patches.

2. Compliance frameworks treat EOL software as a control failure. PCI DSS 4.0 now requires you to manage your software's full lifecycle. Running unsupported databases is a big red flag. Unless you put strong compensating controls in place, you could lose your ability to process payments or pass your next audit. The same applies to SOC 2, HIPAA, and ISO 27001 — running Windows Server 2012 or MySQL 8.0 past their 2026 deadlines guarantees an audit exception.

3. Extended support costs real money — and rises annually. Microsoft's ESU pricing typically doubles every year. Third-party support providers (Percona for databases, TuxCare for Linux/runtimes) offer temporary reprieves, but you are paying a premium to maintain the status quo. Treat these as an 18-to-24-month upgrade runway, not a long-term solution. Check to make sure dates have not changed while planning.

What This Means for You by Company Type

Small business (under 100 employees)

Your biggest exposure is likely Office LTSC 2021 and Windows 10. Both hit EOL on October 13, 2026. If you are running QuickBooks Desktop 2023, that also loses support on May 31, 2026. Budget for Microsoft 365 migration or Office LTSC 2024 now.

Mid-market (100–1,000 employees)

You likely have a mix of MySQL 8.0 databases, Node.js 20 in production, and possibly Exchange on-prem. Prioritize by blast radius: database and Exchange upgrades first, then runtimes. Scan Docker images for Debian 11 base layers.

Enterprise (1,000+ employees)

The convergence of Project Online retirement, SAP Commerce EOL, Exchange ESU expiry, SharePoint Server 2019 end of support, and SQL Server 2016 creates a multi-front migration year. This cannot run sequentially — you need parallel workstreams with separate teams and budgets. If you are also running Dynamics 365 on-premise, check our Dynamics 365 EOL guide for the full timeline.

SaaS and product teams

Prioritize runtimes and databases before line-of-business apps. Node.js, MySQL, PostgreSQL, .NET, and PHP upgrades cascade into CI images, ORMs, background workers, and observability agents. If your product integrates with Exchange Online via EWS, that API starts getting blocked October 1 — plan the Graph migration now.

How to Plan Your 2026 Migration Roadmap

Step 1: Build a dependency inventory, not a server inventory. List versions, auth models, data stores, scheduled jobs, exports, and downstream integrations. A SharePoint farm that looks "current enough" can still carry Add-ins, Azure ACS, or old workflow engines. Run SELECT VERSION() on every database. Check node --version in every container and CI pipeline. Shadow IT is your biggest risk — an unpatched database running a legacy marketing tool is just as dangerous as your primary production cluster.

Step 2: Classify each deadline by failure mode. Some are patch-loss dates. Some are hard retirements. Some are auth or compatibility cliffs. An April EOL on a database holding payment data is more urgent than an October EOL on an internal wiki server. Sort by data sensitivity and blast radius, not calendar order.

Step 3: Choose the landing zone before you scope the project. Decide between MySQL 8.4 LTS vs. PostgreSQL 16/17, SharePoint Online vs. Subscription Edition, Microsoft Graph vs. EWS, and Planner Premium vs. Project Server SE before discovery drags on. Choosing the target early prevents teams from doing discovery twice. (dev.mysql.com)

Step 4: Budget for parallel migrations. 2026 is unusual because multiple EOLs stack. If you try to sequence everything, the last project will start too late. Allocate separate budgets and teams for infrastructure (OS, DB) and application-layer (Exchange, Project Online, ERP) migrations.

Step 5: Test upgrades in staging, not production. MySQL 8.0 → 8.4 is broadly compatible, but removed config variables will crash a server on startup. Node.js 20 → 22 is low-risk, but native addon ABI mismatches surface at runtime. Every upgrade deserves a staging dry run. Document your rollback plan before you start — if you cannot articulate how to revert, you are not ready to cut over.

Step 6: Pull near-term 2027 dates into the 2026 budget. Windows Server 2016 (January 12, 2027) is the obvious example. If you wait, you will finish one emergency project and walk straight into the next. (learn.microsoft.com)

Front-Load the Hard Work

2026 is not one big deadline — it is a chain of smaller ones. The dangerous mistake is assuming the server date is the only date that matters. In real environments, the auth layer, workflow engine, rendering service, or data export path usually breaks first.

When your team hits capacity — especially on complex data migrations involving legacy databases, CRM/ERP systems, or enterprise applications — that is where outside expertise pays for itself. Not with generic advice, but with custom scripts that handle the API rate limits, the undocumented edge cases, and the relational mapping to move your actual data safely.