The hybrid outcome: certify some, renew some.

A ULA exit is often framed as all or nothing. For a mixed estate it does not have to be. You can certify the products that have matured and renew only the ones still growing.

By Daniel Voss · Ex Oracle LMS · 4 June 2026

The short answer

A ULA exit is not always all or nothing. Where the agreement allows products to be treated separately, you can certify the mature products whose deployment has stabilized, capturing them as permanent entitlement at no fee, while renewing only the products still in genuine growth. The result is a smaller, focused renewal instead of paying again for the whole estate. Whether a split is possible turns entirely on the specific contract language, so the wording has to be read before the option is assumed.

Not every product is at the same stage

Why the binary framing is often wrong

Most ULAs cover several named products, and those products are rarely at the same point in their life. A database footprint may have flattened years ago while an analytics or middleware product is still in active rollout. The standard certify or renew framing forces the whole estate onto one path, which means either certifying products that are still growing, or renewing products that have stopped, paying again for an unlimited right they no longer need. Neither is efficient, and for a genuinely mixed estate the better answer is to split.

The hybrid outcome treats the decision product by product. Mature products are certified into permanent entitlement at no fee. Growing products are renewed, but only those, so the renewal is narrow and priced for the capacity you will actually add. The estate ends with the right path under each product rather than a single compromise across all of them.

Can you certify some products and renew others at ULA exit?

Often you can, but it depends on the structure of the agreement. Some ULAs treat the named products as a single bundle that must be certified or renewed together. Others allow products to be separated, which is what makes a hybrid possible. This is the first thing to establish, because the whole strategy rests on it. Where separation is allowed, you certify the stable products and carry only the growing ones into a renewal. Where it is not, the hybrid may still be achievable through negotiation, but it cannot be assumed, and the contract language decides.

The Meridian principle

Decide the path per product, not per agreement. The right outcome for a flat database and a growing analytics platform is rarely the same outcome. Read the contract for whether products can be split, then certify what has matured and renew only what is genuinely still growing.

When the hybrid is the right outcome

A hybrid earns its complexity when the estate is genuinely mixed. The clearest signals are a divided footprint and a funded growth plan that applies to some products but not others.

  • Mature products with a high defensible count. Products whose deployment has flattened and whose count is large relative to a renewal are strong certification candidates. Certifying captures them permanently at no fee and no support increase.
  • Growing products with a funded plan. Products in real, scheduled expansion can justify another term of unlimited rights, because the renewal absorbs that growth cheaply. The key word is funded, not hoped for.
  • A contract that permits separation. The agreement allows the named products to be treated individually at exit, or Oracle is willing to agree to it. Without this, the split has to be negotiated rather than taken.

When all three are present, the hybrid usually beats both pure paths. It avoids paying to renew mature products and avoids prematurely certifying products that still have growth to capture under an unlimited right.

A short worked example

An anonymized example shows the shape. A technology group held a ULA on database, several database options, and an analytics platform. The database and options had been flat for three years with a large defensible count. The analytics platform was in a funded, multi region rollout expected to double over the next term. A full renewal would have paid again for the stable database estate the group had no plan to grow. Instead, the group certified the database and options into permanent entitlement at no fee, and renewed only the analytics platform, where the unlimited right genuinely earned its cost. The figures are indicative, but the renewal was a fraction of the full quote, and the mature products were captured for good.

The next step

If your estate is mixed, do not force it onto one path. Read the contract for whether products can be separated, then certify what has matured and renew only what is funded to grow. See when a clean certification is the answer in when certifying is clearly right, use the certify path to sharpen the renewal in using the certify option as leverage, and ground the whole decision in our certify or renew guide.

The right path under each product

Split the exit where it pays to.

Book a ULA assessment and we will read your contract for separation, measure each product, and structure a hybrid that certifies what has matured and renews only what is growing.

Book a ULA assessment