How to exit the Oracle Java SE subscription. Inventory first, notice in writing, nothing left at term end.

Leaving the Oracle Java SE subscription is an inventory project first: find where Oracle Java runs, move it to free OpenJDK builds and record every removal. Your rights end at term end, and one reinstalled binary reprices the whole workforce.

Why does exiting the Oracle Java SE subscription start with an inventory?

The invoice tells you nothing about where Oracle Java runs. The Java SE Universal Subscription is priced per employee, so the bill is the same whether Oracle Java sits on every laptop or on a few servers. Across the exits we guided, Oracle Java ran on only 10 to 30 percent of the machines the bill implied.

That gap shifts the hard part of an exit away from the technology. The blocker is visibility: you cannot remove what you have not found, and you cannot prove a removal you did not record.

Why does the employee metric make the business case for leaving?

A subscription priced on headcount for software running on a tenth of your machines pays for the whole exit program. The migration effort is bounded and ends on a date you set. The subscription has no end date and grows with every hire, so the reduction you bank repeats every year.

How do you find every Oracle Java install before you leave?

Scan file systems for the runtime binaries themselves. Installer lists miss the places that matter most: private JREs bundled inside third party applications, jlink images baked into internal tools, and build pipelines that pull an Oracle JDK by default.

The discovery method is the one set out in our JRE licensing brief and the shadow install analysis. An exit adds one column to it. Every install gets a disposition (migrate, retain commercially, or retire), a named owner and a target date.

Which checks show whether a machine runs Oracle Java?

• Version string. Run java with the version flag against every Java binary the scan finds, not only the one on the path. Oracle JDK builds report "Java(TM) SE Runtime Environment". OpenJDK builds report "OpenJDK Runtime Environment" and usually name the distributor. IBM's own SDK also prints "Java(TM)", so confirm the java.vendor property (java with the XshowSettings:properties flag) before you count a machine as Oracle.
• Windows machines. Check installed programs for entries such as "Java 8 Update" and the JavaSoft registry keys, then search disks for java.exe, because bundled runtimes rarely register.
• Linux and Unix servers. Query rpm or dpkg for JDK packages, then search for java binaries the package database does not know about, such as those inside application folders.
• Containers and pipelines. Inspect base images, Dockerfiles and CI definitions. An Oracle JDK base image, or a GitHub Actions setup step with the distribution set to oracle, puts Oracle binaries into everything built from it. See our notes on Docker base images and pipeline and workstation cleanup.

Will your applications run on OpenJDK once Oracle Java is gone?

Almost all of them will, unchanged. OpenJDK builds come from the same codebase as the Oracle JDK, so the work is in sequencing, testing and replacing binaries at scale. Our migration decision guide and the three cost modeled migration patterns set out the sequence:

1. Batch replacement. Standard servers and desktops move to an OpenJDK build of the same major version through your normal deployment tooling.
2. Pinned applications. Workloads tied to a runtime by a vendor are handled one at a time, with the vendor asked in writing which builds it supports.
3. Pipeline conversion. Build images and toolchains switch to the new distribution, so the next release does not bring Oracle binaries back.

The distribution comparison covers Amazon Corretto, Eclipse Temurin and Azul Zulu. All three are free to run in production, and paid support is available for teams that want a supplier to call.

Why picking the OpenJDK distribution first is the wrong place to start

Much of the published advice on leaving Oracle Java opens with the choice between Corretto, Temurin and Zulu. We think that order is backward. All three ship the same OpenJDK code on the same quarterly update cycle, so the choice is an operational preference with little risk attached.

The exits that ran into trouble in our work did so on missing inventory and missed deadlines. Start with the file system scan and the contract dates. Once you know how many machines need a new runtime, choosing the distribution takes one short meeting.

What should you do with workloads that need an Oracle build?

Treat them as a separate decision. The usual case is an application whose vendor supports it only on the Oracle JDK. Scope that set to named hosts and price it against the alternatives before anything is renewed by default.

• Rights you already hold. Several Oracle products include restricted use rights to Java SE for running that product.
• Oracle JDK under the No Fee Terms. Oracle's current long term support release can run in production free for a set window, planned until September 2028 for JDK 25. After that date, later JDK 25 updates move to the OTN license, which does not allow general production use. It helps only if the application supports that release and you plan the next upgrade, as our note on the JDK 25 free window explains.
• The application vendor's license. Where a vendor ships the runtime inside its product, ask the vendor to confirm in writing that its license covers it.
• A negotiated residual. If you still need Oracle, a bounded, evidenced list of hosts gives you a far stronger hand than the all or nothing renewal ever did.

How much does leaving Oracle Java save a 5,000 employee company?

It saves most of the subscription, provided the inventory is complete and the residual Oracle set stays small. The hypothetical company below has 5,000 employees, which puts it in Oracle's $10.50 per employee per month band, and runs 4,000 desktops and 600 servers.

The 12 retained servers are where the negotiation happens. Oracle sells the Universal Subscription on the employee metric, so those servers need cover through existing rights, the NFTC route, a vendor's license or a negotiated arrangement. Leaving them on a full employee subscription would erase the saving.

How does the exit change with company size?

• Around 500 employees. At Oracle's entry rate of $15 per employee per month, the subscription costs $90,000 a year. One team can usually scan and migrate everything in a single pass, so the real risk is administrative: the notice and the removal records need the same care a large company gives them.
• 40,000 employees or more. At 40,000 employees, Oracle's lowest published band of $5.25 still gives $2,520,000 a year at list, and above 50,000 employees Oracle prices by quote. Inventories span business units, acquisitions and outsourced IT, so plan more time for discovery than for migration.
• Legacy Named User Plus or Processor subscriptions. Oracle says legacy subscribers may renew only as far as their existing order permits, subject to confirming usage. Compare exiting with renewing on the legacy metric first.

How do you give notice so the Java subscription does not renew automatically?

Serve written non renewal notice to the party named in the notices clause of your contract, in the form that clause requires, inside its window, and keep proof of delivery. An email to your Oracle account rep does not count as notice, and an automatic renewal clause will run if that email is all you sent.

What should you check in the order documents before setting the calendar?

• Term end date. Read it from the ordering document, since invoices often show billing periods instead.
• Renewal terms. Whether the order renews automatically, and at what price.
• Notice requirements. The window, the required form, and the Oracle entity and address named.
• Governing agreement. The Oracle master agreement the order sits under, where notice and audit terms often live.
• Proof of delivery. A courier receipt, a registered post record or a written acknowledgment from Oracle's contracts team.

The notice window can close months before the subscription expires, which usually makes it your first hard deadline.

What has to happen before the subscription term ends?

Every Oracle JDK binary licensed under the subscription has to be gone by the term end date. The subscription grants term rights only. Oracle's own FAQ states that your rights to commercial software downloaded under it end with the subscription, along with Premier Support.

The day after expiry, any Oracle JDK still installed is unlicensed unless the No Fee Terms or another license covers that exact release.

Build the pack as the removals happen. Oracle's approach to Java compliance starts from its download records rather than your inventory, and a complete pack turns that opening into a short exchange of letters. Our pages on proof of removal and decommission log standards set out the format.

How do you keep Oracle Java from coming back after the exit?

Use technical controls, because under the employee metric a single reinstalled binary can support a claim across the whole workforce. For the company in the worked example, one forgotten install puts the full annual subscription back on the table.

• Application control. Block Oracle Java installers and binaries in AppLocker, Windows Defender Application Control or your endpoint tool, using a publisher rule scoped to Oracle's Java product name so other signed Oracle software keeps running.
• Pipeline gates. Fail any build whose base image or toolchain resolves to an Oracle JDK.
• Update checks. Disable the Java auto updater on Java 8 desktops not yet migrated, as covered in our note on blocking update checks.
• Gold images. Rebuild VM templates, laptop images and container base images, or old Oracle builds return with the next deployment.

The audit activity that tends to follow an exit, and the retroactive claims Oracle often opens with, are covered in our Java audit process guide and the lookback analysis.

What will Oracle say when you tell them you are leaving?

Expect the account team to test your inventory and your deadlines. Few arguments will be about the technology. These are the lines we hear most, with replies that hold up.

• "Our records show Oracle Java downloads across your company." A download record shows what someone fetched, and your removal record shows what happened to it. Ask Oracle to name any host it believes still runs an Oracle binary.
• "OpenJDK is unsupported, and you will be exposed on security." OpenJDK builds receive quarterly security fixes, and you have a named distributor plus paid support where a workload needs it. Say so once, in writing.
• "Stay one more year while you migrate, and we will improve the price." Compare the offer with the cost of finishing on time. If you do need cover, keep it short, with a fixed end date and the same notice terms.
• "We will need a license review once the subscription ends." Point to the notice, the term end date and the evidence pack, and share only what the contract requires, as our guide on what not to hand over explains.

What have we seen across 30 to 40 Oracle Java exits?

Across roughly 30 to 40 Oracle Java exits I guided between 2024 and 2026, the per employee metric drove the decision in almost every case. The proportions described above, the gap between the bill and the real footprint and the size of the saving, held from one exit to the next.

The exits that failed did so for procedural reasons. In none of them did OpenJDK break an application.

Which mistakes cause Oracle Java exits to go wrong?

The first three below are the failures we saw in those exits. The fourth is worth adding to your own checklist, because it undoes finished work.

• Notice served to the wrong party. An email to the rep, or a letter to the wrong Oracle entity, left the subscription free to renew.
• Binaries surviving past term end. They sat in forgotten corners: a build agent, a disaster recovery server, a vendor appliance, an old VM template.
• Evidence assembled after the letter. Rebuilding what ran where after Oracle writes costs far more than logging removals as they happen.
• Pipelines left unconverted. The server work finishes, and the next release ships with an Oracle JDK inside its image.

Every failed exit we saw was preventable by the same discipline the successful ones ran: inventory first, a calendar worked back from the term end, and removal records kept as part of the migration.

What to do next

1. 12 months before term end. Pull the ordering document and master agreement, note the term end date, renewal terms and notices clause, and start file system scans.
2. 9 months before. Give every install a disposition, an owner and a date, bundled and built runtimes included, and open talks with vendors whose products ship Java.
3. 6 months before. Migrate the standard workloads to an OpenJDK build, convert the pipelines and scope the residual Oracle set to named hosts.
4. Before the window closes. Serve notice in writing to the party the clause names, with delivery evidenced.
5. 1 month before. Run final scans, clear every remaining Oracle binary and close the evidence pack by the term end date.
6. After the exit. Keep reinstallation controls in policy and pipelines, and rescan on a schedule. Our Java audit defense service and the Oracle Java licensing guide cover the exit and what follows it.

Frequently asked questions