Should you migrate off Oracle Java in 2026? Four numbers decide it, and sometimes the answer is stay.

Most enterprises should leave Oracle Java, because the subscription charges for every employee while the alternatives charge for the machines that run Java. Four numbers settle your case in one meeting, and your notice date sets how late you can start.

Should you migrate off Oracle Java at all?

For most enterprises, yes, and the reason is commercial. Oracle's Java SE Universal Subscription prices Java against your total counted headcount, while every alternative prices it against the machines that run it. That gap drives nearly every answer this decision produces.

Some organizations should stay, though. We work with four possible destinations, and the short gate on this page tells you which one applies before you spend a quarter of engineering time finding out.

We compare the four in detail, including the option most buyers never price, in our guide to alternative Java options. The decision arithmetic set against Oracle specifically is in our Oracle Java versus OpenJDK decision guide, and the builds themselves are compared in Oracle Java alternatives, distribution by distribution.

Which four numbers decide it?

You do not need an inventory to make this decision. You need four numbers, and a competent platform lead can produce credible ranges for all of them in an afternoon.

• Counted employees. Total staff, including people who never touch Java, plus the contractor and outsourcer population that supports your internal operations, as Oracle defines it.
• Running JVMs. Server, container, desktop and appliance. An order of magnitude is enough at this stage.
• Oracle certification dependencies. The number of applications whose vendor support matrix names an Oracle build specifically, as opposed to "Java 17" in general.
• The contract calendar. Your Java anniversary, your notice period in days, and every Oracle Database, middleware or applications renewal that falls inside the next 18 months.

Is any Oracle Java binary running in production today?

Ask this first, and insist on evidence rather than belief. The answer sorts organizations into three groups, and two of them need no migration project at all. It settles about a third of cases in ten minutes.

• No Oracle binaries, no subscription. You are already done. What you need is an evidence pack and a block on Oracle Java downloads at the proxy, and a program would be wasted effort.
• No Oracle binaries, but a live subscription. You are paying for something you stopped consuming. The work is contractual, and the deadline is your notice date.
• Oracle binaries present. Only this group faces a real migration decision, and only this group should read the rest of this page as a project brief.

In roughly half the environments we open, the buyer either stopped using Oracle Java and kept paying, or believed they had stopped and had not. Either way, the answer comes from installation evidence, whatever people in the room believe.

How do you check what is installed without a full inventory?

A spot check is enough for the decision. These sources exist in almost every enterprise and can be pulled in a day or two.

• The version string. Running java -version on an Oracle JDK prints "Java(TM) SE Runtime Environment". OpenJDK builds such as Temurin, Corretto and Zulu print "OpenJDK Runtime Environment" with the vendor's name.
• Endpoint management records. Microsoft Configuration Manager, Intune or Jamf list installed Java packages by publisher. Filter on Oracle, and remember they miss copies unpacked from zip or tar archives.
• Linux package lists. rpm or dpkg queries filtered for jdk and jre show packaged server installs. Container images need a separate scan of your image registry.
• Proxy logs. Requests to Oracle's Java download pages show who still fetches Oracle builds, from which network, and how recently.
• Bundled runtimes. Many applications ship their own Java directory. A file system search for java executables outside the standard install paths finds most of them.

The detailed method is in our guides on telling Oracle JDK apart from OpenJDK and what to inventory before a migration. Treat the spot check as input to the decision and the full inventory as input to the project.

What makes an Oracle Java decision urgent in 2026?

Six dated triggers create the urgency, and only one of them is technical. Urgency in Java licensing comes from calendars you do not control: Oracle's free use windows, your own renewal anniversary, and the renewal of an adjacent Oracle product where Java becomes a bargaining chip.

What changed when the free Oracle JDK 21 window closed?

Oracle's No Fee Terms and Conditions license allowed free production use of Oracle JDK 21 for a bounded window. Historically that window runs to one year after the following long term support release ships. JDK 25 shipped on September 16, 2025, and the JDK 21 window closed on September 16, 2026.

The last quarterly free update was 21.0.12, released July 21, 2026, and a 21.0.12.1 fix release followed on August 18, 2026, inside the window. Starting with the October 2026 Critical Patch Update, Oracle's roadmap puts JDK 21 updates under the Java SE OTN license, which does not cover general production use without a subscription.

JDK 17 went the same way in September 2024, after build 17.0.12, and Oracle plans the same switch for JDK 25 in 2028. With a new long term support release every two years, expect one of these windows to close every two years.

Check the current wording yourself on the Oracle Java SE Support Roadmap and in the license text, and save both with a date. Oracle has changed Java terms three times in six years, and the version you plan against should be one you can produce later.

What are the traps inside the free window?

• An existing subscription overrides it. If you hold any Java SE subscription, that agreement governs your use. The No Fee Terms are a route for organizations that never subscribed, and current customers cannot use them to escape.
• The window forces an upgrade treadmill. Staying free on Oracle binaries means moving the whole environment to the next long term support release inside every window, on Oracle's schedule. Our note on the LTS upgrade treadmill shows what that costs in test cycles.
• Patched builds after the window are not free. The security update you want is the one published after the window closes, and that is exactly the one that carries the paid terms.
• Desktop and developer machines count. Moving servers onto the free release while laptops stay on an older paid build leaves a compliance gap on the machines that are hardest to track.

Which warnings look urgent but are not triggers?

Three things arrive dressed as emergencies. An unsolicited note from an Oracle license team offering a "review" is a sales approach presented as compliance. A partner email warning that you are "at risk" is usually lead generation. The third is a general market article about Java pricing.

None of these change your ratio, your calendar or your certification dependencies, and none of them should compress a decision you have not modeled. When a formal approach does land, follow the sequence in our Oracle Java audit guide and answer in your order, which is rarely the order Oracle asks its questions.

Why does the employee metric change the answer for nearly everyone?

The employee metric cuts the link between price and consumption. Oracle's Java SE Universal Subscription is quoted per employee per month, and the counted population is your workforce rather than your Java users. One server running Java obliges you to license the entire company.

Oracle's definition reaches further than most buyers expect. It covers full time, part time and temporary staff, plus the equivalent people at your agents, contractors, outsourcers and consultants where they support your internal business operations. Our guide to counting contractors and consultants works through the edge cases.

How do you read the employees per JVM ratio?

Divide your counted employee number by your running JVM count. That single figure predicts the outcome better than any inventory tool, because it shows whether Oracle is charging you for what you use or for who you employ.

A retailer with 40,000 counted employees and 300 JVMs sits at 133. A trading firm with 400 employees and 900 JVMs sits at 0.4. Those two organizations are having completely different conversations, and generic advice serves neither of them.

What does the ratio look like in dollars?

Price the same two organizations at Oracle's published list. Oracle states that pricing starts at $15 per employee per month and that the lowest published tier is $5.25, with lower pricing possible above 50,000 employees. The table prices the retailer at that $5.25 floor, so its real list cost can only be the same or higher.

At $8,400 per JVM a year, a support contract priced on cores or servers, or a free build run by your own platform team, has a great deal of room to come in cheaper. At $80 per JVM, many footprint priced support contracts cost more than Oracle, so the trading firm may be right to stay.

The full cost model, including the internal effort that never reaches a business case, is priced end to end in our three migration patterns cost model. The finance version is in the CFO business case to leave Oracle Java.

Who counts, and which part of the count can you argue?

The counted quantity is where the money is, and it is more negotiable than the rate. Oracle's opening position treats every contractor with any system access as a counted employee, which is broader than the contractual language supports.

In the Java negotiations we worked in 2024 and 2025, Oracle's opening counted quantity ran well above the number a buyer could support after a clean headcount reconciliation. A narrower definition held in roughly four cases out of five. Build that reconciliation before the first quote arrives, using the procurement steps in our 20 Java SE procurement insights.

A 30 percent discount on a headcount you never had to concede is a poor result. Fight the counted quantity first and the rate second.

What will the Oracle account team say, and how should you answer?

• "Everyone who could touch Java has to be counted." Ask for the clause. The count follows the employee definition in your ordering document, and contractors count where they support your internal operations. Reply with your reconciled number and the basis for each exclusion.
• "Migrating will cost you more than the subscription." Ask to see the calculation, then set your own beside it: three years of subscription at your counted headcount against the one time migration effort for your JVM count. At the ratios most large enterprises run, the subscription side is usually the larger number.
• "Sign now and we will hold this price." A price hold is only worth something against a quantity you accept. Ask what happens to the price if headcount falls, and whether the count can go down at renewal.
• "Our records show Oracle Java downloads from your company." A download record proves a download, and it may predate your migration. Answer with dated removal evidence. Our note on download account attribution covers how those records are tied to a company.
• "Moving to OpenJDK takes you out of certification." Ask which product and which matrix. For Oracle middleware and applications it can be true, and for most custom code it is not. Get the answer in writing, product by product.

When is staying on Oracle Java the right answer?

Staying is right in four situations, and they are more common than the migration literature admits. An advisor who never recommends staying is being predictable, and you should read that as a warning about the advice.

Low headcount with a dense Java footprint

This case rarely gets written about. If you employ 300 people and run 2,000 JVMs, the employee metric charges you for 300 units to cover 2,000 machines. At the $15 starting rate that is $54,000 a year, or $27 per JVM, which is about the cheapest Java you will ever buy.

Software vendors, quantitative trading firms and specialist engineering businesses land here regularly. Run the numbers before you accept a migration recommendation, because in this situation a support contract priced on footprint can cost more than Oracle does.

A certification matrix you cannot leave

If your Java runs inside Oracle products, the Java decision is a product decision. Oracle WebLogic, E-Business Suite, Forms and Reports, Hyperion and the Retail applications are supported against Oracle's own runtime, and replacing the JDK underneath them can take you outside that product's certification matrix.

The same logic applies to other vendors that name a specific build. Get the matrix in writing before you assume it, because vendor sales teams and vendor support teams often disagree about what is certified. The overlapping middleware exposure is covered in our Oracle iAS licensing guide and in our note on WebLogic and its Java SE coupling.

Rights you already paid for

Two kinds of contract commonly grant Java rights that buyers forget they hold. Check both before any renewal conversation starts.

• Pre 2023 perpetual licenses. A Named User Plus or Processor license bought before 2023 remains valid for what it covers, even though Oracle no longer sells those metrics and you cannot expand them. Our note on legacy perpetual licenses explains what they still cover.
• Java that comes with another Oracle product. Oracle's subscription FAQ says that if you use an Oracle product that requires Java SE, you are already licensed to run the Oracle Java SE runtime for the sole purpose of running that product. We regularly find organizations paying a Java SE subscription for servers already covered this way.

Check the embedded and OEM terms in the Java embedded and OEM licensing guide before you renew anything.

An obligation you cannot transfer in time

Some buyers carry a contractual or regulatory requirement for a named commercial runtime vendor with specified indemnities. A non Oracle support contract usually satisfies that requirement, though not always, and not always inside the time you have.

When the deadline is closer than the approval cycle for a new supplier, subscribing for one controlled term while you do the work properly is a sound commercial decision. Document it as a bridge with an end date, so it does not turn into the permanent answer by default.

Which contract terms should you ask for if you stay?

• A written employee definition with named exclusions. Listing the contractor groups, subsidiaries and outsourcers that fall outside the count stops the argument from restarting at every renewal.
• A right to renew at a lower count. If headcount falls or a partial migration finishes, the renewal should start from the new number. Without it, the next quote starts from last year's quantity.
• A cap on the renewal price increase. A one year term protects your exit but exposes you to a new rate each year, so ask for a stated ceiling on the uplift.
• Agreed treatment for acquisitions. Settle when an acquired company enters the count, so a deal that closes mid term does not trigger an immediate true up. Our note on acquisitions and divestitures sets out the options.
• Notice terms you can operate. The notice period in days, the address for notice, and the form it must take, all written into the ordering document. The wording we ask for is in contract language that caps headcount.

What have we seen in Oracle Java decision gates in 2024 and 2025?

Across roughly 30 to 45 Oracle Java engagements that I ran or reviewed in 2024 and 2025, the decision itself was rarely the hard part. Three patterns came up again and again.

• The destination was clear within the first hour. The employee to JVM ratio usually settled it. What took months was getting five people to agree to own the outcome.
• Buyers were paying for Java they no longer ran. In 4 or 5 cases out of every 10, the buyer had already stopped using Oracle binaries in production and was still paying, or believed they had stopped and had not.
• Late starts bought another year. Every organization that started the decision less than four months before its renewal anniversary ended up buying at least one more year, whatever the technical answer was.

Two measurements from the same work sit behind the timing advice on this page. For environments of 200 to 1,000 JVMs, under 15 percent of the elapsed time went on engineering, and the rest went on approvals and freezes. The typical notice window before renewal was 30 days.

How do you run the decision gate in one session?

One ninety minute session is enough, with five named people and six documents on the table. Java decisions drift for a year because the people who can say yes were never convened in the same room, and the analysis is rarely the obstacle.

Who has to be in the room?

• The platform or runtime owner. Produces the JVM count and knows where the base images come from.
• The procurement or vendor manager. Owns the anniversary date, the notice period and the ordering documents.
• The application portfolio owner. Knows which applications have a vendor support matrix and which are being retired anyway.
• Whoever chairs the change advisory board. This person sets the real timeline, and is almost always invited last.
• A finance partner. Attends to state the budget cycle the answer has to fit inside, without an approval role in the session.

Which six documents should be on the table?

1. The Java ordering document and any amendments, with the notice clause marked.
2. The latest HR headcount report, with contractor and outsourcer numbers shown separately.
3. The platform team's JVM estimate, split by server, container, desktop and appliance.
4. A single list of every Oracle agreement and its end date.
5. The vendor support matrices for your top ten vendor applications.
6. The change calendar, with every freeze window for the next 18 months.

What are the eight questions, and how do you score them?

Score each answer as leave, stay or unknown. Any question that scores unknown becomes a named action with a date, and it does not postpone the decision.

1. What is our counted employees to JVM ratio, to one significant figure?
2. Is any Oracle branded Java binary running in production today, with evidence?
3. Do we hold a live Java subscription, and what is the notice date?
4. How many applications have a vendor support matrix that names an Oracle build specifically?
5. Do we already hold Java rights through a middleware, applications or pre 2023 agreement?
6. What other Oracle agreements renew inside the next 18 months?
7. Which release freezes and regulatory validation windows fall between now and our target date?
8. Who owns the outcome, by name, and what is their next reporting date?

Question eight decides more programs than the other seven combined. A session that ends without a named owner and a reporting date has produced an opinion, and the organization will treat it as one.

When is the latest you can start and still make the date?

Work backwards from the deadline. The deadline is whichever comes first: the end of a free use window, your renewal notice date, or the start of an adjacent Oracle negotiation that you want Java settled before.

What does back planning look like for a specific renewal?

Take a hypothetical company with 600 JVMs across departmental applications, a Java anniversary of July 1, 2027, and a 30 day notice period in its ordering document. Treat the notice date as the deadline, so that you serve notice with Oracle Java already removed and the evidence in hand.

A team in this position that starts on October 1, 2026 is already about seven weeks behind the table. It can recover by booking change windows around the remaining closes now and running application owner sign off in parallel with the build. If that is not realistic, price one short bridge term today, while it is still your choice.

Why does change governance set the pace?

Swapping a runtime is a configuration change. Getting two hundred application owners to accept a configuration change to production systems they answer for is an organizational problem, and it runs at the speed of your governance. That is why engineering accounts for so little of the elapsed time.

The phased schedule and the overruns we see most often are broken down in how long an OpenJDK migration takes, and wave planning in our guide to rollout phasing. Use those as the delivery plan once the decision has been made.

Which freeze windows eat a quarter?

• Financial period end. Most enterprises freeze changes around quarter and year end close. Four quarters means four dead weeks at a minimum.
• Peak trading or seasonal load. Retail, travel and logistics businesses lose eight to twelve weeks to a peak freeze, and it is never negotiable.
• Regulatory validation cycles. In validated environments each change carries an evidence package, and the evidence takes longer to produce than the change.

Add those up before you promise a date. A twelve month plan with three freeze windows inside it behaves like a nine month plan.

What does deciding late cost?

Deciding late costs you three things, and only one of them appears on an invoice. Late decisions remove your options one at a time, until the only option left is the one Oracle prefers.

• A bridge year you did not need. Miss the notice window and you buy a full further term at the counted quantity you were trying to shrink.
• Your negotiating position. A credible ability to leave is what reliably shifts an Oracle Java quote, and that credibility comes from a dated plan. A statement of intent carries little weight, as our note on migration credibility in negotiation shows.
• Migrating under scrutiny. Running the program while Oracle is asking questions adds an evidence burden to every step and slows the work at the moment you need it fast.

The migration also has to reach the places inventories miss. Build pipelines and developer laptops are covered in cleaning Oracle JDK out of CI/CD and developer workstations, and vendor products that carry their own runtime in when third party applications bundle Oracle Java.

What do you give up by leaving Oracle Java?

You give up little in the runtime itself. Every mainstream distribution is built from the OpenJDK project and follows the same quarterly security cycle, so the technical loss on a version for version swap is close to zero.

What you give up is the Oracle support desk, Oracle specific commercial features, and Oracle's position in your product certification matrices. Whether that matters is an application by application question, and it deserves real time. The support and rollback exposure is examined in OpenJDK support and rollback risk after leaving Oracle Java.

Why we would not wait for a full inventory before deciding

The standard advice is to inventory first and decide afterwards. We disagree, because the timing does not work. A full inventory takes two to three months in a real enterprise, far longer than a typical notice window, and in nine cases out of ten the inventory does not change the destination, because the employee to JVM ratio already decided it.

What the inventory changes is the plan, the sequence and the cost, and you need all three after the decision. Decide the destination on four numbers this month, appoint an owner, then let the inventory shape the program. Buyers who wait for perfect data pay for another year of the thing they were trying to stop buying.

Which mistakes cost the most at this stage?

• Serving notice before you can prove removal. Leaving the subscription without dated evidence that Oracle binaries are gone invites the audit conversation you wanted to avoid. Build the record as each environment is cleared, following our guide to proof of removal.
• Treating Oracle JDK 25 as the exit. Moving to the free JDK 25 buys about two years and does nothing for current subscribers. It restarts the same clock, and you face this decision again with a larger environment on Oracle's upgrade schedule.
• Forgetting the base images. A container base image built on Oracle JDK puts it back into production with every build. Fix the images before the servers, as our note on Oracle Java in Docker base images explains.
• Leaving the download route open. Once you have migrated, a developer who pulls a current Oracle JDK 8, 11, 17 or 21 update from oracle.com creates a fresh download record, and any copy that reaches production needs a subscription. Block the download endpoints at the proxy on the day you finish.

What to do next

1. Today. Pull your Java ordering document and write down two dates, the anniversary and the last day for notice. Put both in a calendar with a named owner.
2. This week. Produce the four inputs to one significant figure: counted employees, running JVMs, Oracle certified applications, and every Oracle agreement end date inside 18 months.
3. Same week. Divide employees by JVMs and read your band from the ratio table. Write the provisional destination down before anyone runs a tool.
4. Within two weeks. Establish, with evidence you could show an auditor, whether Oracle branded binaries are running in production right now.
5. Within a month. Hold the ninety minute session with all five roles present, including whoever chairs the change advisory board.
6. At the session. Verify the current No Fee Terms position on Oracle's roadmap page and save a dated copy for your file.
7. After the session. Back plan from your deadline using the latest safe start table, subtract your freeze windows, and confirm the date is still reachable.
8. Once the answer is leave. Pick a primary build using the distribution choice comparison, then sequence the exit with the Oracle Java SE exit map.

Frequently asked questions