A buyer side guide to converting an unlimited agreement into permanent value. It covers the certification mechanics with real numbers, a deployment maximization framework, and a pre exit checklist your team can act on this quarter. Written by ex Oracle licensing specialists who now sit only on your side of the table.
The certification window arrives once and sets your entitlements permanently. This guide gives you the mechanics and the moves before that window opens, so the number you declare is the largest one you can defend.
Why a ULA exit is a seven figure decision, why most teams under count, and why support fees do not rise with the certified number.
Processor counting with core factors, Named User Plus where it applies, and how production, test, development, disaster recovery, and standby instances qualify.
How certified counts often land 1.5 to 2.5 times higher than a first estimate once cloud, disaster recovery, and non production deployments are handled properly. The multiple is indicative and depends on your estate.
The cloud counting trap, the VMware sweep, and the scope clauses, each with the defensive move, closed by a pre exit checklist you can run against your own contract.
The figures below are indicative and illustrate the processor count mechanics only.
| Environment | Physical cores | Core factor | Processor licenses |
|---|---|---|---|
| Production cluster | 64 | 0.5 | 32 |
| Disaster recovery | 32 | 0.5 | 16 |
| Test and development | 24 | 0.5 | 12 |
| Defensible total | 60 |
A team that counted production alone would certify 32. Counting every environment they were entitled to claim takes the defensible total to 60, all backed by the evidence file.
The guide tells you what to do. A confidential assessment tells you what your certification is worth and what we would do to protect it.