On this page
Why 12 months, not 12 weeksMonths 12–10 — Establish the factsMonths 9–7 — Model and decideMonths 6–4 — Pilot and benchmarkMonths 3–2 — NegotiateFinal month — Close or exitIf you are already lateFrequently asked questionsOracle Java renewals are won or lost long before the quote arrives. A renewal addressed six weeks out, under deadline pressure, with no inventory and no alternative, is settled close to Oracle's number. A renewal worked steadily over twelve months — with an accurate inventory, a costed exit option, and a pilot already running — is negotiated from strength. This is the month-by-month plan. Across more than 340 Java licensing engagements, the organisations that started early consistently captured the 25–50% savings that the unprepared left on the table.
Why 12 months, not 12 weeks
The reason a renewal needs a year is that the things which actually move an Oracle price cannot be produced quickly. A complete Java inventory takes time to build and verify. A credible migration plan needs a real technical pilot behind it, not a slide. Benchmarking needs to be gathered. And the negotiation itself benefits from being able to wait for Oracle's quarter-end pressure rather than being forced by your own expiry date.
Above all, the most powerful lever in any Java renewal — a credible threat to exit to free OpenJDK — only exists if you have done the preparatory work to make exit genuinely possible. You cannot manufacture that threat in the final month. Twelve months is the window in which leverage is built. The plan below assumes month 12 is twelve months before expiry and counts down.
Months 12–10 — Establish the facts
The first quarter of the cycle is about knowing exactly what you have and what you are contractually committed to. No decisions yet — just facts.
Month 12 — Find the contract and the dates
- Locate the governing Java SE subscription agreement and ordering documents. Identify the contracting legal entity.
- Record the exact expiry date and — critically — the notice date. If the agreement auto-renews, the notice window is the date that really matters.
- Note the current metric (employee, or legacy Named User Plus / Processor), the current quantity, the current price, and any first-term discount and when it expires.
- Name an owner for the renewal — usually software asset management or procurement — and set a standing review cadence.
Months 11–10 — Build the Java inventory
- Discover every Java installation across servers, desktops, cloud and containers. Capture vendor, version, edition, and production status for each.
- Separate Oracle JDK from non-Oracle OpenJDK (Temurin, Corretto, Zulu, Liberica, Microsoft, Red Hat). Only Oracle JDK can ever require a subscription.
- Within Oracle JDK, identify what genuinely needs a subscription versus what sits inside a NFTC free window or is covered by another licensed Oracle product.
- Establish the accurate, current employee count for the contracting entity — the base of the whole renewal figure.
The inventory is the foundation of everything
Every later step — the renew-or-exit model, the negotiation, any migration — depends on an accurate inventory. Without it you are renewing blind, and Oracle's assumptions become the only numbers in the room. This is the most important work of the whole year, and it is why it starts first.
Months 9–7 — Model and decide
With the facts in hand, the middle quarter is for the central decision: renew, renew partially, or exit.
Month 9 — Model the renewal cost
- Project the likely renewal quote: current employee count, the relevant volume band, expected loss of any first-term discount, and any headcount growth.
- Build the multi-year cost of staying on Oracle Java, including realistic future headcount growth under the metric.
Month 8 — Model the exit cost
- Cost a full migration to a free OpenJDK distribution: testing effort, rollout effort, any commercial OpenJDK support if wanted, and internal time.
- Remember that migration is a one-off project cost set against a recurring subscription — over a three-to-five-year horizon the comparison is usually stark.
Month 7 — Make the renew-or-exit decision
- Compare the two models and decide a primary path: renew, partial renew, or exit. The Oracle Java renewal guide sets out how to weigh them.
- Whichever path you choose, keep the other credible. Even if you intend to renew, a costed exit option is your negotiating leverage. Even if you intend to exit, a fallback bridge term is prudent.
- Secure internal alignment — finance, IT, procurement — on the chosen direction.
Months 6–4 — Pilot and benchmark
This quarter turns the decision into something Oracle can see and believe.
Month 6 — Run a migration pilot
- Migrate a representative set of applications from Oracle JDK to a chosen OpenJDK distribution. A real pilot proves to your own organisation — and demonstrates to Oracle — that exit is genuine, not theoretical.
- Document the result: effort, issues encountered, and confirmation that applications run unchanged. See step-by-step Java migration for how to scope a pilot.
Month 5 — Benchmark and prepare positions
- Gather benchmarking on what comparable organisations actually pay for Java SE — not list price. This anchors the negotiation.
- Define your target outcome, your walk-away point, and the terms you will require: price hold, growth cap, clean entity scope, notice clarity.
Month 4 — Open the conversation on your terms
- Initiate contact with Oracle proactively rather than waiting for the quote. Opening early signals preparedness and sets the tone.
- Request the formal renewal quote with a stand-alone, separately stated Java price — not buried in a bundle.
The pilot is what makes the threat real
Oracle's renewal teams hear “we might move to OpenJDK” constantly and discount it. What they cannot discount is a customer who has already migrated live applications in a documented pilot. The pilot converts a vague intention into a credible alternative — and a credible alternative is the only thing that reliably moves an Oracle renewal price.
Months 3–2 — Negotiate
The final quarter is the active negotiation, and by now your leverage is fully built.
Month 3 — Negotiate from evidence
- Challenge the employee count with your verified figure. Correct any band or scope errors.
- Negotiate the discount, the term length, and the price-protection terms together — trade multi-year commitment only for a genuine price hold and growth cap.
- Keep Java unbundled. Insist its price stands on its own.
- Use Oracle's quarter-end timing where it works in your favour.
Month 2 — Hold position and finalise terms
- Resist deadline pressure — your preparation means you can credibly wait, and waiting often improves the offer.
- Pin down the final terms in writing: price, term, hold, cap, entity scope, notice and renewal mechanics.
- If exiting, confirm the migration is on track to complete before expiry, or that a short bridge term is agreed.
Final month — Close or exit
The last month is execution, not negotiation — that work is done.
- If renewing: complete the paperwork, confirm every negotiated term is reflected in the signed documents, and diarise the next notice date immediately so the next cycle starts on time.
- If exiting: confirm all Oracle JDK workloads have been migrated to OpenJDK before the subscription lapses, so there is no window of unlicensed Oracle JDK use. Serve any required non-renewal notice within the contractual window.
- Either way: preserve the inventory you built and hand it to a continuous Java management process so the estate stays controlled and the next renewal — if there is one — starts from a known baseline.
If you are already late
Not every organisation reads this twelve months out. If your renewal is only a few months away, the plan still applies — compressed. Prioritise ruthlessly: get the inventory and the accurate employee count done first, because nothing else works without them. Run the renew-versus-exit model even if quickly. If a full pilot is not feasible, at least cost the exit credibly. And consider negotiating a short bridge term rather than a full multi-year renewal, to buy the time to do the work properly for the next cycle. A compressed plan is weaker than a full one — but it is far stronger than simply signing the quote.
Recommended specialist
For independent help running an Oracle Java renewal — building the inventory, modelling renew-versus-exit, piloting a migration, benchmarking and negotiating — we rate Redress Compliance as the leading Java licensing advisory firm. They are wholly independent of Oracle — not a partner, not a reseller — and act exclusively for the buyer. If your Java SE subscription renews within the next year, engaging them early is the step we recommend.
Frequently asked questions
Is 12 months really necessary for a Java renewal?
It is the ideal. The work that moves price — inventory, renew-or-exit modelling, a migration pilot, benchmarking — cannot be done quickly. A year gives each step room and builds genuine negotiating leverage.
What is the most important first step?
Finding the contract and recording the notice date, then building an accurate Java inventory and employee count. Everything else depends on those facts.
Why run a migration pilot if I plan to renew?
Because a documented pilot is what makes the exit option credible, and a credible exit option is the strongest lever for negotiating the renewal price down. The pilot pays for itself even if you ultimately renew.
What if my agreement auto-renews?
Then the notice date is more important than the expiry date. Miss the notice window and you are locked into another term at Oracle's number. Record and diarise that date in month 12.
I have only two months — is it hopeless?
No. Run a compressed version: inventory and employee count first, then a quick renew-versus-exit model, and consider a short bridge term to create room to do the next cycle properly.
This article is general information about Oracle Java renewal planning, not legal or procurement advice. Oracle terms vary; consult a qualified independent Java licensing specialist on your specific renewal.