OpenJDK migration is the buyer side answer to the per employee Universal Subscription. This playbook lays out the sweep, the sort, and the residual negotiation that shrink your Oracle Java bill instead of locking it in.
Why migration is the strongest move you have
Since January 2023 Oracle has priced Java SE on a per employee metric that counts every full time and part time employee, every contractor, and every temporary worker, regardless of who actually touches Java. For most estates that makes the Universal Subscription the most expensive answer to a question that has cheaper answers. OpenJDK, the free and open source implementation that underpins most Java distributions, runs the same applications without the per employee bill. Migration is the buyer side move because it shrinks the only number Oracle can charge against. For the full picture, see the OpenJDK migration playbook pillar.
The playbook in four moves
A disciplined migration follows the same sequence every time.
- Sweep the estate and find every place Oracle Java is installed and running.
- Sort each workload into move now, move later, or keep on Oracle Java.
- Migrate everything that can move to a free OpenJDK distribution.
- Negotiate the residual against the much smaller envelope that remains.
The order matters. You cannot negotiate a residual you have not yet defined, and you cannot define it until the estate is swept and the workloads are sorted.
Sweep the estate first
You cannot migrate what you cannot see. The first move is a complete inventory of every machine, container, and image where Oracle Java is installed, what version it runs, and what application depends on it. This sweep does double duty: it tells you what can move, and it gives you dated evidence that protects you if an LMS audit arrives, since audits intensified in 2026 with a three year lookback. A clean inventory is the foundation of both the migration and the defense.
Sort the workloads
| Category | Typical workloads | Action |
|---|---|---|
| Move now | Standard server side and internal applications | Migrate to a free OpenJDK distribution |
| Move later | Apps needing a test cycle or a vendor confirmation | Schedule into a phased plan |
| Keep for now | A few apps with a hard Oracle Java dependency | Isolate and license narrowly |
The keep pile is almost always far smaller than the account team implies. The work is proving that, workload by workload.
Negotiate the residual
Once the movable workloads are migrated, what remains is a small set of applications that genuinely need Oracle Java. That residual is your real negotiating position. Instead of licensing your entire employee base for a handful of applications, you negotiate against a defended, documented, and much smaller footprint, with a credible walk away in your pocket because the rest of the estate already runs on OpenJDK. The safe way to execute the move without breaking applications is covered in how to migrate off Oracle Java safely.
Run it in phases, not all at once
A migration that tries to move everything in one weekend creates risk and invites mistakes. The buyer side approach runs in phases: a low risk pilot, then waves of workloads grouped by similarity, with testing at each step. Phasing also lets you start cutting cost early while the harder workloads are still in flight. The full sequencing is set out in planning an OpenJDK migration in phases.
The buyer side takeaway
OpenJDK migration is the one move that changes the math instead of just arguing about it. Sweep the estate, sort the workloads, migrate everything that can move, and negotiate the residual against a small defended envelope. Done in phases, it cuts cost early and gives you a credible walk away for the rest. Download the field guide below to run the playbook yourself.
Download the OpenJDK Migration Field Guide
A buyer side playbook for CIOs, procurement, and general counsel planning a move off Oracle Java. Trade a work email, get the guide and The Java Audit Brief.
Download guide