Certification is a contractual declaration made under a 30-day clock, and Oracle will question it. What the post-ULA position actually looks like, and how to build an exit you can evidence rather than one you hope holds.
An Oracle ULA — Unlimited Licence Agreement — can suit an organisation that is growing quickly and wants room to scale without a purchase order for every deployment. The difficulty is at the other end. This “all you can eat” arrangement is notoriously hard to close out cleanly, and the work that makes a clean exit possible has to have been happening for years by the time you need it.
This post is about the exit and the post-ULA position: what your strategy has to account for if you want to leave a ULA in a controlled way, with your financial and compliance risk contained.
At the end of the defined deployment period the ULA terminates and your certified licence quantities convert into perpetual licences. There is generally a clause requiring you to certify the quantity of each licence you are using within 30 days of the deployment period ending.
Your declaration has to be factual and it has to survive an official Oracle audit. An internal measurement exercise across your Oracle deployments, run on a tool Oracle recognises, is how you find out what your compliance position is — and therefore what your options actually are.
Broadly there are two.
Negotiate a replacement ULA, which minimises the immediate audit risk. Your committed spend will be higher than the current agreement, because your current usage converts into maintenance payments and you are then also paying for a further deployment period on top.
Exit the current ULA by certifying your usage. This is the cheaper route and the exposed one: a certification is a declaration, and Oracle has both the right and the commercial incentive to test it.
Either way, understanding your usage of the licensed products is the whole game — not only at the moment of certification, but for the period after it.
It helps to be clear-eyed about Oracle’s position. A ULA is priced on the potential benefit a customer can extract by deploying the covered products freely. It produces a dependable revenue stream, so leaving one will meet resistance. Expect incentives and discounts to be withdrawn or reduced. Like any publisher, Oracle’s goal is to hold revenue flat or grow it.
Four things are true once the ULA ends:
If the plan is to exit and reduce what you spend with Oracle, the exit needs careful planning, precise execution and enough runway to be done safely. Start with the process and the risks:
You cannot start the governance process too early. A ULA is not a free-for-all and it is not risk-free. How software gets deployed has to be managed and explained throughout the term, ideally from the day the agreement was signed.
Be compliant, and know that you are. This is the biggest mistake customers make. Monitor your Effective Licence Position at regular intervals across the deployment period rather than measuring once, at the end, under a 30-day clock.
More deployment means more value from the ULA. During the deployment period you maximise the benefit of the agreement by deploying the authorised products where they genuinely help the business. Expect Oracle to scrutinise this on exit, and expect the scrutiny to focus on whether only the correct software was deployed.
Build the team. Treat it like an audit defence task force: procurement, legal, finance and IT, communicating with each other, and — critically — funnelling every conversation with Oracle through a single channel.
Understand the terms, and your own legal reading of the specific wording. Certification clauses are not boilerplate and the differences matter.
Engage expertise backed by verified technology. Oracle publishes a list of verified third-party tool vendors. Engaging one early gives you full visibility of your Oracle deployments and can remove the need to run additional LMS scripts later in the process.
Formulate the declaration. Work out what you will actually be using on the last day of the deployment period — not what you are using today, and not what you deployed at the peak.
Declare, and expect to be questioned. Oracle will probe the data. Verified measurement output and Oracle licensing expertise are what let you demonstrate that the numbers are accurate and validly derived.
Keep documentation and internal audit records across the whole deployment period, not just the final quarter.
Negotiate maintenance against the certified entitlement. Reducing cost with Oracle is complex but not impossible when you have accurate usage data. That evidence is a negotiating asset, and it is worth planning how to use it alongside whatever else is in play — future spend in the current Oracle fiscal period, for instance.
Once Oracle authorises the certification figures, the licences convert to standard perpetual licences and are issued to you, with maintenance costs paid in line with the ULA definitions. The process takes time and has to be executed precisely. Done well it is usually less expensive than entering a new ULA. Its success depends entirely on the accuracy of the data.
“Use a tool” is not advice. It is worth being specific about what an Oracle licence engine has to handle before it is useful in a ULA certification, because this is the level of detail an LMS engagement turns on:
CerteroX SAM’s Oracle engine covers all of these. It computes a continuous compliance position rather than a point-in-time reconciliation, which is what makes the difference between a declaration you can produce on any given day and one you assemble in a panic inside a 30-day window.
Certero is a verified third-party tool vendor with Oracle License Management Services. In Certero’s own published wording: being a verified third-party toolset means that Oracle’s audit team can accept data from Certero during an official audit, as an alternative to installing Oracle License Management measurement tools. That is conditional rather than guaranteed — but it is a materially different starting position from arriving at a certification with spreadsheets.
One more thing worth saying plainly: do not assume Oracle’s own scripts will do this work for you. They produce measurement data for Oracle’s purposes. They do not produce a management position for yours.
A ULA can offer real advantages, but it is a strategic commitment that is not easily reversed. Licence compliance has to be maintained throughout the deployment period, because exiting requires a certification completed within 30 days of the deployment period ending.
Govern the ULA from the beginning. Independent Oracle licensing expertise, working on Oracle LMS-verified technology, gives you full visibility of your Oracle deployments for the duration of the agreement — and the same people can help you plan and navigate the exit and what follows it.
Maximise the return by deploying the licensed products where they meet real business requirements during the term.
Consider replacing third-party products with licensed products already covered by the ULA, which reduces overall spend without adding liability.
If you want more on the risks that build up during the term rather than at the end of it, see the dangers of an Oracle ULA and how to avoid them.
Certero’s professional services extend your own SAM team with specialist Oracle licensing people working on CerteroX SAM, so the expertise and the measurement come from the same place. Talk to us if your certification date is inside the next eighteen months — that is roughly when the preparation needs to start.
Other posts covering the same ground.
An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.