A migration that finishes the week before renewal arrives too late to change the number. The timeline that protects you works backward from the renewal date, so that real reductions in your Oracle Java footprint are visible and verifiable before Oracle prices the deal.
An OpenJDK migration creates two kinds of value. The first is the recurring saving once Oracle Java is gone from a workload. The second, often larger at the table, is the leverage the migration gives you at renewal. That second kind of value is entirely a function of timing. Oracle prices the Universal Subscription on your employee count, and the number it puts on the table reflects what it believes you depend on. If your migration is still a slide deck when Oracle prices the deal, it changes nothing. If it is a measured reduction in deployed Oracle Java, with evidence, it reframes the entire conversation. The work is the same. The timing is what turns it into leverage.
Start with the date the current agreement ends and the date Oracle typically opens the renewal conversation, usually three to six months before. That earlier date is your real deadline, because that is when Oracle forms its view of your number. Everything in the timeline has to produce visible progress before then, not before the contract expiry. Build the plan in reverse: the evidence has to be ready before the conversation opens, the migration of the largest segments has to be done before the evidence is gathered, and the estate sweep that finds those segments has to come first of all.
| Phase | Months before renewal opens | What it produces |
|---|---|---|
| Estate sweep | 9 to 12 | A full inventory of where Oracle Java runs and what truly needs it |
| First migration wave | 6 to 9 | The largest low risk workloads moved to a free OpenJDK distribution |
| Second migration wave | 3 to 6 | The remaining estate carved down to a small residual |
| Evidence pack | 1 to 3 | Verified record of what was removed and what remains |
The bands are indicative and will flex with the size of your estate, but the order does not change. A sweep that finds the footprint, two waves that shrink it, and an evidence pack that proves the new, smaller envelope before Oracle prices the deal.
You cannot migrate what you have not found, and you cannot negotiate against a number you cannot describe. The sweep maps every place Oracle Java runs, separates the workloads that genuinely need it from the ones that can move, and gives you the segments to migrate in priority order. Done early, it also gives you months of runway. Done late, it compresses the whole program into a window too tight to deliver real reductions before the renewal conversation opens.
Sequence the migration so the biggest, lowest risk workloads move first. OpenJDK and Oracle Java SE are built from the same source, so most server side and containerized workloads move with little change, and those tend to be the largest share of the estate. Moving them first produces the most visible reduction earliest, which is exactly what you want on the record before Oracle forms its view. The second wave handles the more involved cases and carves the remainder down to a small residual that genuinely needs Oracle Java, if any remains at all. For the sequencing detail, our guide to common OpenJDK migration mistakes shows the traps that slow a wave down.
A timeline that protects you at renewal cannot afford a wave that stalls and forces a rushed return to Oracle Java. Each wave needs a clean way back if a workload misbehaves, so that a single problem does not derail the schedule or hand Oracle a reason to doubt your reductions. Our guide to rollback planning for a Java migration covers how to keep that path open without slowing the program. A migration that can step back calmly is one that keeps moving forward on schedule.
The renewal conversation does not turn on what you migrated. It turns on what you can prove you migrated. The final phase assembles a verified record: what Oracle Java was deployed at the start, what was removed in each wave, what runs on a free OpenJDK distribution now, and what small residual remains. That pack is what lets you negotiate against a much smaller employee envelope rather than the full headcount Oracle would otherwise price. Without it, even a real migration reads as a claim. With it, the new footprint is a fact on the table.
Set the deadline at the date Oracle opens the renewal, not the date the contract expires. Sweep early, migrate the largest workloads first, keep a rollback path, and have a verified evidence pack ready before Oracle prices the deal. The migration only becomes leverage if it is visible in time.
This timeline is one component of a larger method. For the full approach, see the OpenJDK Migration Playbook, which sets out the sweep, the waves, and the residual strategy in detail.
Tell us your renewal date and we will build the timeline backward from it, so the reductions are real and proven before Oracle prices the deal. Get a quote for the work.
Tell us your renewal date and your estate, and we will build a timeline that lands the leverage before Oracle prices the deal. Fixed Fee from 18,000 dollars or Gainshare, a share of verified savings with zero retainer and no risk to you.
Get a Quote Book a Strategy CallFixed fee or gainshare, both backed by our guarantee. We sit between you and Oracle and we never take vendor money.
Get a QuoteWeekly intelligence on Oracle Java licensing moves and the buyer side defenses that work.