Moving Oracle workloads to Oracle Cloud Infrastructure or Cloud@Customer? The licenses you already own can cut your cloud bill dramatically, or create a compliance gap that follows you into the cloud. We manage the licensing side of the move end to end: discovery, compliance, BYOL eligibility, OCI sizing and commitment, and Oracle Support Rewards.
On-premise estateLicenses, support, deployments
OCI or Cloud@CustomerBYOL services, Universal Credits
Support Rewards: 25% to 33% of eligible OCI spend, applied to your on-premise support invoices
Bring Your Own License (BYOL) lets you apply Oracle licenses you already own, and support, to Oracle Cloud services. Instead of paying Oracle again for the software inside a cloud service, you pay a much lower BYOL rate for the infrastructure and automation. On Oracle’s own price list, BYOL database rates run up to 78% below the equivalent license-included price. For the basics, read what Oracle BYOL is.
License includedBYOLBYOL saving
Exadata Database (Exascale)16 ECPUs
US$4,000
US$961
−76%
Base Database High Performance16 ECPUs
US$2,640
US$576
−78%
Base Database Enterprise8 ECPUs
US$640
US$288
−55%
Base Database Standard4 ECPUs
US$160
US$144
−10%
Database ECPU rates from Oracle’s cloud price list, 1 November 2026, at 744 hours a month. Infrastructure and storage are billed separately, and your discounted rates will differ.
For every Oracle workload you move, there are three ways to pay:
License includedOracle bundles the software license into the hourly rate. No entitlement risk, but the highest price.
BYOL to a managed service (PaaS)Base Database, Exadata Database Service, Autonomous Database and similar services billed at the BYOL rate, offset by licenses you own. Oracle requires your license support to stay current throughout.
BYOL to infrastructure (IaaS)You install and run Oracle software yourself on OCI Compute and license it against the capacity you use.
| Rule | What it means for you |
|---|---|
| OCI has its own counting rules | OCI is not treated like AWS, Azure or Google Cloud. One Oracle Processor license covers two x86 OCPUs, and services billed in ECPUs use different ratios by edition. The rules come from Oracle’s Universal Credits service description and your order, not from the on-premise core factor table. |
| Support must stay current | BYOL relies on licenses that are owned and supported. If support lapses or is moved to a third party, BYOL eligibility for managed services is lost. |
| No mixing within an instance | An instance is either BYOL or license included. You can add license-included instances alongside BYOL ones, but you cannot scale a BYOL instance beyond what your licenses cover. |
| Options must be owned | Under BYOL you must own every database option you use, with limited concessions: Enterprise Edition on PaaS includes the Diagnostics, Tuning, Data Masking and Real Application Testing rights, and Transparent Data Encryption is included. These concessions do not apply to IaaS. |
| Standard Edition has limits | Standard Edition licenses map to Standard Edition cloud services, with their own ratios and size caps. |
| ULA deployments behave differently | Under Oracle’s standard terms, deployments in Oracle Cloud under an Unlimited License Agreement cannot be counted at certification. ULA customers must plan BYOL and certification together. |
| Licenses can move | Entitlements can move between on-premise, OCI and Cloud@Customer, and back again. Counting the same license in two places at once is where compliance risk begins. |
Get these rules right and BYOL is the single largest saving available in an Oracle cloud move.
Most of the cost of an Oracle cloud move is decided before the first workload migrates. These are the mistakes we see most often:
Moving a compliance gap into the cloudUnlicensed options, virtualization exposure or ageing deployment data travel with the workload. In the cloud, Oracle can see the configuration directly.
Defaulting to license includedTeams pick license-included services because it feels safer, then keep paying support on the on-premise licenses those services replaced: paying twice for the same software.
Assuming licenses qualify when they don’tLicenses on third-party support, licenses tied to specific entities or hardware, ULA quantities and missing options can all fail BYOL eligibility.
Using the wrong counting ruleApplying the on-premise core factor, or the AWS and Azure vCPU rule, to OCI can halve or double the licenses required. Mixing OCPUs and ECPUs makes it worse.
Over-committing Universal CreditsCommitments sized on the migration plan rather than steady-state usage. Unused credits expire; usage above the commitment is billed at the rate card.
Leaving Support Rewards on the tableRewards that are never claimed, expire after 12 months, or have nothing to offset because on-premise support was cancelled too early.
Cancelling support the wrong wayDropping some licenses from a support contract can trigger Oracle’s repricing rules on the licenses that remain, eroding the saving you expected.
Paying twice during cutoverLong dual-running periods, with on-premise and cloud environments both active and both counted.
Cloud providers and implementation partners focus on getting workloads running. Oracle’s account team focuses on the size of the cloud commitment. We focus on the licensing and commercial decisions in between, which is where most of the money is.
Our service covers the whole journey, from the first inventory to the year after migration. You can engage us for the entire program or for any single stage.
We establish what you own and what you run before anything moves.
A cloud migration is the best time to close a compliance gap, because you control the timing and the target design. See our Oracle License Review.
We confirm which licenses can be brought to OCI and, where they fall short, find the most economical way to close the gap.
Five yes answers: BYOL ready. Every no is a decision, not a dead end: we model the cheapest way to close each gap.
We choose the right service and the right licensing model for each workload, not one answer for the whole estate.
We size your Universal Credits commitment to steady-state usage, not to the migration plan, and negotiate the terms that protect it.
Sized on the migration plan
Sized on steady state
Actual consumptionCommitted, unused (expires)Overage at the rate card
Every dollar consumed on eligible OCI services under a Universal Credits order earns 25 cents in Support Rewards, or 33 cents for customers with a current Unlimited License Agreement, which can be applied to your Oracle technology support invoices. Used well, Support Rewards can reduce that support bill substantially; used carelessly, they expire unclaimed.
Illustrative figures. Not eligible: Pay As You Go, Oracle SaaS, Java subscriptions, Oracle Linux, VMware and Marketplace services.
The savings are only real once the old environment is retired and the new one is controlled.
Most of the cost of an Oracle cloud move is decided before the first workload migrates.
For organizations that need data to stay in their own data center, for regulatory, latency or sovereignty reasons, Oracle offers OCI services on premises: Exadata Cloud@Customer, Compute Cloud@Customer and OCI Dedicated Region. They bring OCI pricing and BYOL into your own facility, but they come with their own commercial structure. For the Exadata license rules, see Oracle Exadata licensing.
A two-part billA multi-year infrastructure subscription plus consumption billed through Universal Credits. Only the Universal Credits portion earns Support Rewards.
Long, fixed commitmentsMinimum terms and activation levels make sizing errors expensive to unwind.
BYOL still appliesThe same eligibility and support conditions apply as in the public cloud, so the licenses must be tested just as carefully.
Exit and refresh planningWhat happens at the end of the term, or when hardware is refreshed, should be agreed at signing.
We assess whether Cloud@Customer is the right choice against public OCI, multicloud and staying on premises, then size and negotiate it on the same principles as any other OCI commitment.
We have sat on Oracle’s side of the tableRythium is led by a former Oracle Vice-President. We know how cloud commitments and Support Rewards are positioned, and how Oracle account teams are measured on them.
Licensing and cloud economics in one teamMost advisors cover either licensing compliance or cloud cost. BYOL decisions need both at once.
Strictly independentWe take no fees, commissions or migration funding from Oracle, any cloud provider or any implementation partner. Our only incentive is your outcome.
The whole Oracle estate in viewOn-premise licenses, support contracts, ULAs, Java, SaaS and cloud commitments are linked. We make sure a saving in one does not create a cost in another.
We stay after migrationWe remain involved through decommissioning and the first year of consumption, when most cloud savings are either secured or lost.
Oracle’s account team focuses on the size of the cloud commitment. We focus on what you actually need.
Bring Your Own License lets you use Oracle licenses you already own, with current support, on Oracle Cloud services. You pay a lower BYOL rate that covers the infrastructure and Oracle’s automation, instead of paying again for the software. More in our guide: what is Oracle BYOL.
On x86 OCI shapes, one Processor license covers two OCPUs for Enterprise Edition. Services billed in ECPUs, Arm-based shapes and Standard Edition each follow their own ratios, set out in Oracle’s service descriptions. The on-premise core factor table does not apply, and neither do the vCPU rules Oracle uses for AWS, Azure and Google Cloud.
Usually, but not always. If you already own the licenses and will keep paying support on them anyway, BYOL is almost always the better choice. If licenses would be bought new, or a workload is small, short-lived or highly variable, license included can win. We model both over three to five years for each workload.
For Oracle’s managed database services, no: Oracle requires current Oracle support on the licenses you bring. For self-managed software on OCI Compute the position is less clear-cut and depends on your contract. Treat any plan that combines third-party support with BYOL as a compliance risk until it has been reviewed.
Under BYOL, yes, apart from specific concessions. Bringing Enterprise Edition to Oracle’s managed database services includes the Diagnostics, Tuning, Data Masking and Real Application Testing rights, and Transparent Data Encryption is included. Options such as Partitioning, Multitenant, RAC or Active Data Guard must be owned if you use them. Many license-included services bundle these options, which is why the choice must be made workload by workload.
You can deploy, but under Oracle’s standard terms deployments in Oracle Cloud are not counted when you certify. If certification is likely, the timing and design of the cloud move must be planned with the ULA exit. ULA customers also earn Support Rewards at the higher 33% rate. See also our ULA Certification & Exit service.
Consumption of eligible OCI services under a Universal Credits order earns rewards of 25% of spend, or 33% with a current ULA. Rewards can be applied to invoices for Oracle technology license support, such as Database and WebLogic, before tax. They expire 12 months after they are earned.
Pay As You Go usage, Oracle SaaS, Java subscriptions, Oracle Linux and third-party services such as VMware or Marketplace offerings do not earn or redeem rewards. On Cloud@Customer, only the Universal Credits portion earns rewards.
On its own, no. You must spend about four dollars on OCI to offset one dollar of support, so rewards reduce the net cost of a move you have already justified; they do not justify the move. We treat Support Rewards as one lever in the negotiation, alongside discounts and support reduction, not as the business case.
Often, yes, but how you do it matters. Removing some licenses from a support contract can trigger Oracle’s repricing rules on those that remain, and cancelling support removes the invoices Support Rewards would offset. We sequence support reductions so the saving is real.
To steady-state usage, not the migration plan. Unused credits expire at the end of the term, while usage above the commitment is billed at the rate card. It is usually cheaper to commit conservatively and secure expansion at your negotiated rate than to over-commit up front.
The licensing rules are largely the same, including BYOL. The commercial structure is not: a multi-year infrastructure subscription plus consumption, with minimum terms and activation levels. Only the consumption portion earns Support Rewards.
Yes. We work alongside your implementation partner or internal cloud team. They design and run the migration; we make sure the licensing and commercial decisions behind it are right, and we take no fees or funding from either Oracle or the partner.
Tell us what is on your desk: a migration plan, an OCI proposal, a Cloud@Customer quote or a Support Rewards business case. A senior advisor replies within 48 hours.
Request a confidential conversation
At Oracle from 1998 to 2015, in leadership roles including Vice President Sales, and before that at Compaq and DEC. Amongst the foremost Oracle license experts globally.
Cookies on rythium.com
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy