The certify or renew decision is not a matter of taste. Five questions settle it: your real growth, the maturity of your deployment, your cloud plans, your support cost, and the scope of your contract. Answer them honestly and the right path is usually clear.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Certify when your deployment is mature, your near term growth is modest, and your count is high and defensible, because certification converts that count to perpetual licenses at no fee and leaves support flat. Renew only when genuine, near term growth in the named products would outrun the count you could certify today. Everything else is detail. The five questions below turn that principle into a decision you can defend to a board, and the honest answer always depends on your contract language.
Certification is free and permanent. Renewal is a fresh fee for more unlimited time. The only reason to pay for more time is growth you can prove is coming and cannot capture by certifying now. Test that growth before you accept a renewal quote.
The single most important input is genuine, forecastable growth in the named products over the next two to three years. Not aspiration, not a cloud slide, but deployment you can defend in a plan. If you expect to materially expand Oracle Database, options, or middleware footprint, renewal keeps the unlimited right alive while you grow. If your estate is steady or shrinking, every month of renewed unlimited rights is a month you paid for and did not use. Be ruthless here, because Oracle's renewal pitch is built on the assumption that you will grow, and that assumption is theirs, not yours.
A ULA late in its term, with a wide and well used deployment, is usually a certification candidate, because the count you can certify is already large and certifying locks it in for free. The work is to make sure the count is complete and defensible, including virtualization, disaster recovery, and non production, before you declare it. Certified counts often land well above a first estimate once those are handled properly. A thin or immature deployment, by contrast, has less to lock in and may justify more time. The maximization mechanics matter as much as the decision itself.
Cloud changes the calculus because cloud counting is contract specific. Many ULAs require deployments in AWS or Azure to run a continuous period, often 365 days, to count toward the certification baseline, and some exclude public cloud entirely. If you plan to move Oracle workloads to public cloud, the question is whether those deployments will count at exit, and whether timing them before certification captures value you would otherwise lose. If cloud does not count under your terms, repatriation or a move to OCI before exit can bring those workloads back into the count.
Support is the quiet driver of the long run number. At certification, support continues at the ULA level regardless of the certified count, so a higher certified number is free value and does not raise your support bill. Renewal usually folds a fresh license fee into a new, higher support base that compounds for years. Modelling support across both paths over five to ten years often reveals that the renewal fee is the smaller part of the cost. We work that model in modeling support costs under each path.
The last question is whether your contract scope is clean. Customer definition, entity lists, and territory clauses bite at exit, especially after a merger or acquisition during the term. Deployments in an entity or territory outside scope can trigger remediation demands at certification. If your corporate structure has changed, the scope question may push you toward renewal to buy time to fix it, or toward a carefully managed certification with the scope issues resolved first. The renewal pitch itself is worth understanding, which we cover in how Oracle sells the renewal.
| Question | Leans certify | Leans renew |
|---|---|---|
| Real growth | Flat or shrinking | Strong, provable |
| Deployment | Mature, wide, high count | Thin, early stage |
| Cloud | Counts or repatriable | Large, will not count yet |
| Support cost | Hold flat by certifying | Accept higher base for growth |
| Contract scope | Clean and in scope | Unresolved scope issues |
The view is indicative. Most real cases lean clearly one way once all five are answered honestly, and where they do not, the contract language is usually the tie breaker, so read it before you decide.
The certify or renew choice rewards honesty about growth and discipline about the count. Answer the five questions with evidence, not optimism, and the path is usually plain. When the answers are mixed, the contract decides, which is why the decision belongs with someone who reads ULAs for a living. The full framework, with the scorecard and the cost models, lives in our pillar, the certify or renew guide.
Certify when growth is modest and your count is high and defensible, because it is free and permanent. Renew only when real, near term growth would outrun what you could certify today. The five questions, growth, deployment, cloud, support, and scope, settle it, and the contract breaks any tie. Test the renewal quote rather than accept it, because it is an opening position, not a price.
Certify when your deployment is mature, your near term growth is modest, and your count is high and defensible, because certification converts that count to perpetual licenses at no fee. Renew only when genuine, near term growth in the named products would outrun the count you could certify today. The honest answer depends on five questions and your contract.
Renewal carries a fresh license fee and continued support, while certification carries no fee and leaves support flat at the existing level. Renewal can still be the right call if real growth would exceed the certified count, but the renewal quote is an opening position that typically moves, so it should be tested, not accepted.
Book a confidential assessment and we will run the five questions against your deployment and your contract, and tell you which path serves you.