Vendor Support Requirements During Exit.

Many Oracle Java exits stall on a single claim: that a third party application vendor requires an Oracle build. Most of those claims do not survive a direct question. Pressing them is some of the highest value work in the whole exit.

The claim that holds exits hostage

Almost every Oracle Java exit reaches a moment where someone says a third party application requires an Oracle build of Java, so that part of the estate cannot move. Since January 2023 the Universal Subscription has priced Java SE at 5.25 to 15.00 dollars per employee per month, counting every full time and part time employee, every contractor, and every temporary worker. The danger of accepting a vendor support claim too quickly is that a small, supposedly stuck workload keeps the entire workforce priced against the per employee metric. That is why pressing these claims is some of the highest value work in the exit. A claim that turns out to be false can release the whole estate.

Three kinds of vendor claim

Indicative. In our experience the first two categories cover most claims. The third is real but rare, and it should never price your whole headcount.

Certified is not the same as required

The most common claim is that an application is certified only on Oracle Java. Certification usually means the vendor tested against Oracle and did not test alternatives, not that the software fails on a free build. The distinction matters enormously. A buyer can ask the vendor for the specific technical reason an OpenJDK distribution would not work, and can test the application against a free build in parallel. More often than not the application runs. Where it does, the certification claim becomes a documentation question rather than a licensing one.

Version dependence is solvable

The second claim is that the application needs a particular Java version. This is real but rarely points to Oracle specifically. Free OpenJDK distributions ship the same major versions, including long term support lines that cover older estates. A version requirement is usually met by matching the version with a free distribution, not by paying Oracle for the whole workforce. The exit work here is mapping each application's version need and matching it, which is the same discipline used for older estates in exit strategy for Java 8 estates.

When the dependency is genuinely real

Sometimes the dependency is real and narrow: a specific Oracle feature with no free equivalent, or a contractual support term that genuinely requires it. That workload becomes part of the residual, and the rule for the residual is firm. It must be contracted to its true, contained size and never priced against your full headcount. A genuine dependency on one application is not a reason to subscribe the whole organization. Scoping it correctly is covered in the residual subscription after an exit.

How to handle vendor claims

1. Inventory every claim. List each application said to require Oracle and who said it.
2. Ask for the technical reason. Put the question to the vendor in writing.
3. Test in parallel. Run the application on a free build and record the result.
4. Match versions where needed. Use a free distribution that ships the required version.
5. Scope the genuine residual. Keep only the truly dependent workloads, contracted to their real size.

What pressing vendor claims is worth

Every false vendor claim that you retire releases more of the estate from the per employee metric, and a smaller counted footprint is what drives the saving. Across our buyer side work, clients who challenge vendor support claims rather than accepting them reach an average reduction of 68 percent versus Oracle's opening number. We sit between you and Oracle, we never take vendor money, and we press these claims on your behalf with the technical detail to back it up. A Fixed Fee starts from $18,000, agreed up front. Or choose Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you. We have defended more than $120M in Java exposure and over 300 Java audits, with more than 20 years of combined experience.

Where to go next

Vendor claims are where exits get stuck and where they get unstuck. Ground your approach in our Oracle Java licensing guide for 2026, then read exit strategy for Java in third party apps for the deeper version. To press your own vendor claims with buyer side backing, book a Strategy Call.