Once you certify out of a ULA, the perpetual licenses you captured can run on Oracle Cloud Infrastructure under bring your own license. The workloads keep running on entitlements you now own, but the value depends on the conversion you apply and the documentation that proves every OCI system sits on a certified license.
Bring your own license is what gives a certified count a long life on the cloud. The unlimited right has ended, but the perpetual licenses you captured at certification are yours to deploy, and OCI is built to accept them. The mechanics are not complicated, but they have two edges that decide whether the move pays: the conversion that maps your owned licenses to OCI compute, and the documentation that ties each cloud workload back to a certified entitlement. Get both right and your OCI estate runs cleanly on licenses you already own. Get either wrong and you either oversize the footprint or leave an audit question open. As ever the specifics turn on your products and the current OCI terms, so treat this as the shape and confirm the numbers against your own entitlements.
Usually yes. Certification converts your unlimited deployment into a fixed number of perpetual licenses, and those licenses behave like any other owned entitlement once the term has ended. Bring your own license lets you apply them to OCI, so the workloads you run there draw on the count you captured rather than on an unlimited right that no longer exists. There is no need for a fresh purchase to cover what your certified licenses already permit. The detail varies by product, edition, and the OCI terms in force, and some products have their own cloud rules, so the safe path is to confirm that your specific licenses qualify for bring your own license on OCI before you build around the assumption. Where they do, OCI becomes one of the most natural homes for a certified estate.
A certified license is an asset you own. Bring your own license is how you put that asset to work on the cloud without paying twice for the right to run it.
OCI measures compute in OCPUs, and Oracle publishes how an owned processor license maps to OCPUs under bring your own license. The mapping is not the same across every product and edition, and it is the single number that decides how much OCI capacity your certified count covers. If you size your OCI footprint without working out the conversion, you risk either buying compute your licenses already cover or, worse, running more than your entitlement permits and creating exposure. The discipline is to take the conversion per product, apply it to the certified count you hold for that product, and size the OCI estate to the result. Because the published rules change, confirm the current mapping at the time you plan the move rather than relying on a figure from a previous project.
| Step | Illustrative figure |
|---|---|
| Certified processor licenses, one product | 100 processor licenses owned after certification |
| Published BYOL mapping to OCPUs | Applied per the current OCI rule for that product and edition |
| OCI compute covered | Sized to the mapping, not to the raw license count |
| Headroom check | Confirm OCI usage stays within the converted entitlement |
Figures are illustrative and indicative; use the current published OCI BYOL mapping for your products.
Document the mapping between certified licenses and OCI workloads, the conversion you applied, and the date each workload moved, and keep it alongside the evidence file that supports your certification. This is the same discipline that protects you in the years after exit, applied to the cloud. If Oracle reviews the estate after certification, the question it tends to ask is whether every running system sits on a real entitlement. A clean mapping answers it directly: this OCI workload runs on these certified licenses, converted on this date under this rule. Without that record, an OCI estate can look like deployment with no obvious license behind it, which is exactly the appearance an audit team probes. The documentation is light to maintain and decisive to hold, which is why it belongs in the move rather than after it.
It pays most where you have a maximized certified count and a genuine need for cloud capacity, because then the licenses you already own absorb the OCI footprint and you avoid buying cloud entitlements you do not need. It pays less, or not at all, where the certified count is thin, since a small count converts to limited OCI compute and you may need to buy more anyway. The deciding factor, again, is the size and quality of the certification behind you. A count maximized at exit gives bring your own license something substantial to work with for years; an under counted certification leaves you converting a small entitlement and reaching for the purchase order sooner. That is one more reason the value of life after the ULA is largely set on the day you certify, and why the count is worth maximizing while you still can.
Bring your own license is the natural sequel to a clean OCI exit. Read OCI and your ULA exit for how OCI counts toward the baseline, and the partial exit, certify and migrate for combining the count with a planned move. For the full exit picture, read the ULA exit strategy guide.
Usually yes. Once you certify out of a ULA you hold perpetual licenses, and those licenses can generally be applied to OCI under bring your own license terms in the same way as any owned entitlement. The unlimited right has ended, so the workloads run on the count you captured. The product detail and conversion depend on your licenses and OCI terms, so confirm before relying on it.
OCI uses OCPUs, and Oracle publishes how an owned processor license maps to OCPUs under bring your own license, which differs by product and edition. The mapping matters because it decides how much OCI compute your certified count covers. Work it out per product against the current OCI BYOL rules, and size your OCI footprint to the licenses you actually hold.
Record which certified licenses cover which OCI workloads, the conversion you applied, and the date the workload moved. Keep it alongside the evidence file behind your certification. If Oracle reviews the estate after exit, that mapping is the answer that shows every OCI workload sits on an owned, certified entitlement rather than on a lapsed unlimited right.
Book a confidential assessment and we will work the conversion, size your OCI footprint to the licenses you own, and document the mapping that keeps it clean.