Java license compliance after an acquisition

Mergers and acquisitions are one of the most reliable triggers for an Oracle Java licensing problem — and one of the least anticipated. A deal that closes cleanly on every other software line can leave the combined entity badly exposed on Java, because Java’s pricing is tied to total headcount and acquisitions are, by definition, headcount events. The exposure rarely shows up in the deal model. It shows up later, in an audit letter, after the integration team has merged two estates that neither side fully understood. This guide explains how an acquisition reshapes Java compliance and what to do about it — before close, at close, and after.

Why acquisitions create Java exposure

When two organisations combine, their Java estates combine with them. The acquiring company inherits every Oracle JDK installation the target was running — on servers, on developer laptops, embedded inside third-party applications, buried in container images. It also inherits the target’s licensing position: whatever Java SE subscriptions the target held, whatever legacy BCL-era installs it never cleaned up, and whatever unlicensed usage it had accumulated and never disclosed.

The problem is that Java is almost never examined with the same rigour as the target’s database or middleware estate during diligence. Oracle Database licensing gets scrutinised because it is visible and expensive. Java gets overlooked because, historically, it felt free — and the people running the deal often still believe it is. So the combined entity walks into its first post-close year carrying a Java exposure that no one priced, and Oracle, which watches M&A announcements closely, has a fresh reason to take an interest.

The employee metric and the headcount jump

Since January 2023, Oracle has sold Java SE under the Java SE Universal Subscription, priced per employee. The metric counts your total employee population — full-time, part-time, temporary, agents, contractors, and consultants who support internal operations — not the number of people who actually use Java. That design is what makes acquisitions so financially significant.

Consider an acquiring company of 8,000 employees that buys a target of 6,000. Before the deal, if the acquirer needed a Java SE subscription, it was licensing 8,000 employees. After the deal, the licensable population is 14,000. The Java subscription does not stay the same size — it grows by the full headcount of the acquired business, even for employees who have never touched Java in their working lives. At published list pricing, every additional thousand employees is a material annual number, and an acquisition can add many thousands at once.

This is the single most important fact for any finance or IT leader integrating an acquisition: the Java line in next year’s budget is a function of combined headcount, and it must be re-modelled the moment the deal headcount is known. Treating the pre-deal Java cost as stable is the mistake that turns a manageable number into an audit surprise.

Are Java subscriptions transferable?

A common assumption is that the target’s existing Java SE subscription simply carries over to the acquirer and covers the combined entity. It does not work that way. Oracle subscription agreements are entered into by a specific legal entity, and they typically restrict assignment and transfer. Whether the target’s subscription survives the deal — and what it covers afterwards — depends entirely on the deal structure and the contract language.

In a share purchase, where the target continues to exist as a legal entity, its Oracle agreements often remain in place with that entity. But many Oracle contracts contain a change-of-control provision that is triggered by a sale, and that provision can give Oracle rights — to be notified, to consent, or in some cases to revisit terms. In an asset purchase, where the acquirer buys the business but not the legal shell, contracts generally do not transfer automatically at all; assignment requires Oracle’s consent, and Oracle is under no obligation to grant it on the old terms.

The practical lesson is that you cannot assume the inherited subscription does what you need. The contract has to be read — specifically for the entity definition, the assignment clause, the change-of-control clause, and the audit rights clause — and read before close, not after.

The due diligence gap

Software licensing due diligence on a target should answer a simple question for Java: what is the target running, under what licence, and what is the unlicensed exposure? In practice, that question is frequently skipped or answered superficially. The target’s own team may genuinely not know — Java sprawl is notoriously invisible — and the diligence checklist may not even include Java as a distinct line.

That gap matters because exposure does not disappear at close; it transfers. If the target was running thousands of Oracle JDK instances without a subscription, the acquirer now owns that liability. Oracle’s audit rights look at the entity and its usage; a buyer who absorbed an unlicensed estate inherits the claim. A proper Java diligence pass — ideally a focused compliance assessment of the target — converts an unknown liability into a priced one, which can then be reflected in the purchase price, the warranties, or an indemnity. Discovering the same exposure a year later, in an audit, gives you none of those remedies.

Carve-outs and divestitures

Acquisitions get the attention, but the reverse transaction — selling or carving out a business unit — carries its own Java trap. When you divest part of your organisation, your licensable headcount falls. The Java SE subscription you signed, however, does not shrink on its own. If your subscription was sized for 14,000 employees and a divestiture takes you to 9,000, you will keep paying for 14,000 until the subscription is renegotiated at renewal — and Oracle has no incentive to remind you.

There is also a transitional risk. During a carve-out, the divested unit often relies on the parent’s IT — including its Java entitlements — under a transition services agreement. Both sides need to be clear on who is licensed for what during that period, and the divested unit needs its own Java position established before the transition agreement ends. Handled well, a divestiture is an opportunity to right-size or exit Java. Handled poorly, it leaves you overpaying for headcount you no longer employ.

Integrating two Java estates

Once a deal closes, the operational task begins: merging two Java estates into one managed, compliant whole. The acquirer’s standards, tooling, and licensing decisions now have to extend across the target’s environment, and the target’s installs have to be discovered, classified, and brought into line.

Integration is the right moment to make the strategic call. If the acquirer has already migrated away from Oracle JDK to a free OpenJDK distribution, integration means extending that standard to the acquired estate — replacing the target’s Oracle JDK installs and removing the Java line from the combined cost base entirely. If the combined entity still needs an Oracle subscription, integration is when you size it correctly against verified combined usage and verified combined headcount, rather than guessing. Either way, the deciding input is an accurate inventory of what both organisations are actually running.

A post-acquisition Java compliance plan

1. Run Java diligence before close. Inventory the target’s Oracle JDK estate and existing subscriptions; quantify unlicensed exposure so it can be priced into the deal.
2. Read the contracts. Check both organisations’ Oracle agreements for entity definitions, assignment and change-of-control clauses, and audit rights.
3. Re-model the combined cost. Recalculate the Java SE subscription against combined licensable headcount — this is your real post-close Java budget number.
4. Inventory the combined estate. Discover every Oracle JDK install across both environments, including embedded and containerised Java.
5. Decide renew, consolidate, or migrate. Use the verified inventory to choose: a single right-sized subscription, or a migration that removes Oracle Java cost altogether.
6. Integrate and standardise. Apply one Java standard, one distribution policy, and one monitoring process across the combined organisation.
7. Document the clean position. Keep evidence of the post-integration state as your defence record against any future audit.

Getting independent help

An acquisition compresses a year’s worth of Java licensing decisions into the weeks around a deal — diligence under time pressure, contract clauses that must be read correctly, a subscription that must be re-modelled against a headcount that only just became final. The cost of getting it wrong is a combined entity that is unknowingly non-compliant and visibly attractive to Oracle’s audit teams, which monitor M&A activity precisely because it so often produces under-licensed estates.

Independent, buyer-side advisers run Java through the deal as a defined workstream: target diligence, contract review, combined-cost modelling, and a post-close integration plan. With no Oracle partnership in the picture, the advice serves only the combined entity’s interest. Our Java Compliance Assessment handles target and combined-estate diligence, and our Java Negotiation service right-sizes the subscription once the deal headcount is known. Across 340+ Java engagements, that approach has contributed to more than $180M in client savings — much of it on deals where Java was nearly missed.

Frequently asked questions