Partial Migration as an Exit Strategy.
Move most of the estate off Oracle Java in waves while leaving the few workloads that need it in place. Partial migration delivers a carve out and captures most of the savings without a risky big bang.
Partial migration moves most of the estate off Oracle Java while leaving the few workloads that need it in place. It is the mechanism that delivers a carve out, and it lets a buyer capture most of the savings without a risky big bang.
Why partial, not all at once
A full migration off Oracle Java in one motion sounds decisive, but for a large estate it concentrates risk and effort into a single window and gives Oracle a deadline to negotiate against. Partial migration takes the opposite approach. It moves the estate in waves, starting with the workloads that are easiest and safest to shift, and leaves the genuinely Oracle dependent workloads for last or for keeping. Each wave removes a slice of the population from Oracle's reach, so exposure falls steadily rather than waiting on one large event. It is the practical way to deliver the carve out approach to Oracle Java without betting everything on a single cutover.
The metric makes the waves worth it. Since January 2023 Oracle has priced Java SE on the Universal Subscription 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. Because the price is tied to headcount rather than installs, the saving comes from reaching the point where the only Oracle Java left is so contained that the licensed population can be argued down to a fraction, or moved off the per employee model. Partial migration is how you get there safely.
Sequencing the waves
| Wave | What moves | Why first or last |
|---|---|---|
| Wave 1 | Standard apps on common Java versions | Lowest risk, fastest proof |
| Wave 2 | In house tools your team owns | You control the code and the testing |
| Wave 3 | Vendor apps that support free builds | Needs vendor confirmation first |
| Hold | True Oracle only dependencies | Keep, isolate, or press the vendor |
Indicative ordering. Sequence by risk and effort so each wave builds confidence for the next.
The advantage of moving in waves
Partial migration gives a buyer three things a big bang cannot. It produces early proof, because the first wave shows the business that free OpenJDK runs its workloads with no impact. It spreads effort, so teams are not overwhelmed and the program survives competing priorities. And it preserves optionality, because at any point the buyer can decide to stop, having already shrunk exposure, rather than being committed to an all or nothing date. That optionality is itself leverage. An Oracle account team watching an estate migrate wave by wave knows the buyer can keep going, and that knowledge softens the renewal long before the migration is complete. The wider plan that frames this is set out in building a credible Java exit strategy.
Running a partial migration
- Inventory and group. Sort workloads by risk and by whether they truly need Oracle.
- Prove with wave one. Move the safest group first and document that nothing broke.
- Scale the waves. Roll forward through the estate, retaining evidence at each step.
- Hold the dependencies. Keep or isolate the few true Oracle only workloads.
- Govern the result. Stop new Oracle builds from undoing the migration.
Each migrated wave is a workload Oracle cannot price, but only if you can prove it moved. Retain the records. The full ordering question is covered in sequencing a full exit from Oracle Java.
What partial migration is worth
By the time the early waves are done, most of the estate already runs free and the Oracle conversation is about a small remainder. That is where the leverage and the savings are. A buyer who has migrated the bulk of the estate negotiates the residual from strength, and across our work that disciplined approach delivers an average reduction of 68 percent versus Oracle's opening number. Partial migration captures the large majority of the savings of a full exit while keeping risk low and keeping the few workloads that need Oracle exactly where they are.
This is the work we do alongside your teams. We sit between you and Oracle, we never take vendor money, and we sequence the migration so exposure falls fastest with the least disruption. 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 on the buyer side.
Where to go next
Partial migration is the engine of most exit strategies. Ground it in our Oracle Java licensing guide for 2026, then read the carve out approach to Oracle Java to see the target it serves. To plan your own waves, download the guide and bring your estate to a Strategy Call.
Download the guide.
Get the buyer side OpenJDK migration guide for the full playbook on shrinking your Oracle Java footprint, then bring your questions to a Strategy Call.
Download guide