Oracle JDK 20 EOL September 2023: Budget Planning Guide

What the September 2023 Date Means

Oracle JDK 20 reaches end of life on September 19, 2023, when both active support and security updates cease. Version 20.0.2 is the final release in this line. Because JDK 20 is not a long-term support release, Oracle provides updates only until the next non-LTS version ships, making the support window brief and predictable.

For organizations running JDK 20 in production, the end-of-life date marks the point when no further patches—including critical security fixes—will be issued through Oracle's standard channels. Systems remaining on 20 after September will accumulate unpatched vulnerabilities as new CVEs emerge.

Why This Matters for Next Year's Budget Cycle

Most enterprises finalize their annual IT budgets between now and mid-year. The September 2023 EOL falls squarely in the next fiscal year, which means the decision on how to handle JDK 20's retirement must be funded in the budget you are building today.

Defer the line item now, and you will either face an emergency procurement in Q3 or run unsupported Java instances into the following year. Both outcomes are expensive: emergency vendor renewals come without negotiation leverage, and unsupported software creates audit findings, compliance gaps, and operational risk that auditors and insurers increasingly refuse to overlook.

What Upgrading Typically Involves

Migrating from JDK 20 to the next LTS release—currently JDK 21—requires more than swapping binaries. Engineering teams must regression-test applications against the new runtime, update build pipelines, verify third-party library compatibility, and coordinate deployment across development, staging, and production environments.

For a mid-sized application portfolio, plan on two to four months of engineering calendar time. Larger estates with hundreds of services, legacy codebases, or vendor applications that certify slowly can stretch migration projects beyond six months. Add the fact that your platform and security teams are already booked, and the September deadline becomes difficult to meet if you start planning in Q2.

Why Teams Often Cannot Migrate in Time

Three factors commonly derail Java upgrade projects. First, dependencies: a single uncertified library or vendor module can block an entire application stack. Second, competing priorities: security incidents, feature roadmaps, and infrastructure migrations all consume the same engineering resources. Third, testing rigor: enterprises with strict change-control processes require extensive QA cycles that cannot be shortcut, even when an EOL deadline looms.

The result is that many organizations reach September with migration work incomplete. The options then narrow to running unpatched, paying for vendor extended support, or engaging a third-party maintainer.

Comparing Your Options: Migration, Vendor Extended Support, and Third-Party Support

Budget requests should present decision-makers with a realistic cost comparison. Break down each path:

Migration to a Supported Release

Capture engineering labor (internal FTE hours at loaded cost), testing infrastructure, potential application rewrites, and the risk buffer for unforeseen compatibility issues. Include the ongoing cost of staying current, because non-LTS releases ship every six months. If your organization cannot sustain that tempo, factor in the cost of moving to an LTS track instead.

Oracle Extended Support

Oracle does not typically offer extended support for non-LTS JDK releases. If your commercial agreement includes custom terms, obtain a quote now. Extended support from any vendor is priced as a premium over standard maintenance, often two to three times the annual cost, and becomes more expensive each year.

Third-Party Support

Third-party maintainers provide security patches, bug fixes, and technical support for Oracle JDK 20 and other non-LTS releases beyond the vendor's EOL date. Coverage includes vulnerability remediation, compatibility guidance, and access to support engineers without the requirement to migrate on Oracle's release schedule. Contracts are typically annual, priced per instance or per socket, and cost significantly less than vendor extended support while delivering comparable SLA terms.

You can learn more about third-party support options on our Oracle software support page.

What to Put in the Budget Request Now

Your budget line item should reflect the true cost of the decision, not just the renewal figure. Include:

• Discovery and assessment: audit your JDK 20 footprint, identify dependencies, and estimate migration effort. Allocate two to four weeks of architect or senior engineer time.
• Migration costs: engineering labor, testing tools, contractor support if needed, and a contingency for delays. Budget for the full project, even if you plan to phase it.
• Bridge support: if migration will not complete by September, include third-party support costs to cover the gap. A twelve-month contract provides breathing room and eliminates the risk of running unsupported.
• Ongoing support: whether you migrate to LTS or remain on a non-LTS cadence, budget for the annual support cost—vendor or third-party—plus the engineering time to handle future upgrades.

Present these options with a recommendation. If your team can realistically migrate by September, fund the project fully. If the timeline is uncertain, budget for third-party support as a risk-mitigation control and revisit migration as a later-phase initiative.

Getting a Third-Party Support Quote as a Benchmark

Before you finalize vendor renewal paperwork or commit to a migration budget, obtain a third-party support quote. The process is straightforward: provide your instance count, deployment topology, and current support SLA requirements. Quotes typically arrive within one business day.

Use the third-party figure as a benchmark during vendor negotiations. Procurement teams armed with a credible alternative often secure better terms. Even if you ultimately renew with Oracle or complete the migration, the comparison ensures you are paying a market rate rather than accepting the first offer.

Third-party support also functions as a safety net. If your migration project runs past September, the contract keeps your JDK 20 instances patched and compliant without forcing an incomplete cutover or an expensive vendor escalation.

Taking Action Before Budget Lock

The September 19, 2023 end-of-life date is fixed. Your budget window is not. Start the assessment now: inventory your JDK 20 deployments, estimate migration effort honestly, and model the cost of each option. Build a line item that reflects the real work, not the optimistic case.

If you wait until the budget is locked, your choices narrow. If you wait until Q3, you are managing a crisis instead of executing a plan. The organizations that navigate Java EOL transitions successfully are the ones that budget for them early.

Contact our team to discuss third-party support options for Oracle JDK 20 and receive a quote you can include in your budget planning.