Migrating off Oracle Java is the hard part, but it is not the finish line. The per employee metric is unforgiving precisely because it does not scale with usage: a single Oracle Java SE install left running in a forgotten corner can give Oracle the opening to price a subscription against your entire workforce. Compliance after migration is the discipline of proving, on any given day, that the thing you removed is actually gone. Here is what that takes.
Why does Java compliance still matter after migration?
It still matters because the Java SE Universal Subscription counts all employees and contractors regardless of use, so the exposure is binary rather than proportional. You do not owe a little for a few installs; you potentially owe a headcount sized subscription for any licensable Oracle Java that remains. That asymmetry is the whole reason migration is worth doing, and also the reason a migration that is ninety percent complete is not safe. The last installs carry the same risk as the first, and stragglers are the rule, not the exception, in a large estate.
How do you prove Oracle Java has been removed?
You prove it with a current inventory that distinguishes Oracle Java SE from OpenJDK builds, backed by scan evidence and dates. Repeated discovery scans across servers, desktops and build pipelines should classify every Java runtime by vendor and version, not just confirm that Java is present. Oracle Java and an OpenJDK build can look superficially similar, so the inventory has to identify the distribution precisely, because that distinction is the entire licensing question. Keep the scan history, so you can show not only the current state but the trajectory from migration to clean.
- Scan continuously and classify by distribution, not just by presence of Java.
- Watch the re entry points: developer self installs, container base images, and bundled runtimes inside commercial software.
- Record the migration timeline, so an inquiry meets evidence of when and how you moved.
- Document any residual Oracle Java that is genuinely required and properly licensed, so it is a known, bounded number.
Can Oracle audit you after you leave Oracle Java?
Yes, Oracle can still make contact after you leave, because a historical Java download without a subscription remains a visible trigger. The contact often arrives as a polite request to confirm Java usage rather than a formal audit, but it should be met with the same evidenced position. A documented inventory that shows what you ran, when you migrated, and what residual Oracle Java is licensed turns that inquiry into a short conversation. Without it, you are arguing from memory against Oracle's records, which is the weakest place a buyer can stand.
A services firm believed its Java migration was complete, then received a usage inquiry from Oracle. A fresh scan found Oracle Java SE still embedded in two container base images used across the build pipeline, a re entry the team had not caught. Because the firm kept dated inventory evidence, it isolated and replaced the images within days and answered Oracle from a documented, clean position rather than a defensive one. The inquiry closed without a subscription. The lesson was that the scan, not the project plan, defines when a migration is done.
What is the ongoing discipline?
The ongoing discipline is to treat Java like any other licensable estate: inventory it continuously, govern how new runtimes enter, and keep the evidence current. The most common re entry points are developers pulling Oracle Java out of habit, container images that bundle it, and commercial applications that ship it inside. Govern those and the migration stays done. Let them drift and you can quietly rebuild the exact exposure you spent the project removing.
For why the wave is here, see the Java audit wave: 1 in 5 by 2026. For choosing a replacement build, see third party JDK options compared. The full method sits in the Oracle Java licensing guide, and our Java licensing advisory service turns it into a defended position. If Oracle has already made contact, contact us and we will scope it with you.