Oracle Cloud Infrastructure offers flexible licensing models that CIOs can leverage to optimise costs and preserve existing investments. This playbook provides a strategic framework for BYOL cost management, licence portability for Database, WebLogic, and Java SE, Universal Credit optimisation, and steps to ensure compliance during cloud migration.
Migrating enterprise Oracle workloads to the cloud introduces new licensing considerations. Oracle addressed this by designating OCI (and certain third-party clouds) as "authorised cloud environments" where special licensing rules apply.
Licence-Included: The cloud subscription price includes the Oracle software licence. Higher rate, but no separate licence needed.
BYOL to PaaS: You bring an existing licence and pay only for cloud infrastructure/management, resulting in a significantly lower service rate. Oracle manages the platform, but you contribute the licence entitlement from on-prem.
Oracle introduced the Universal Credits model to simplify cloud purchasing. Instead of buying specific services à la carte, customers purchase a pool of credits (via pay-as-you-go or annual commitment) that can be consumed on any OCI IaaS/PaaS service. This model provides flexibility to shift spending across services and regions. Oracle has also offered incentives like Support Rewards to further entice customers: as OCI usage grows, organisations earn credits that can offset on-premises Oracle support fees.
CIOs must craft a licensing strategy that balances new cloud subscription models with existing entitlements. The goal: avoid double-paying for licences, maintain compliance during and after migration, and fully exploit Oracle's programmes (BYOL, Universal Credits, Support Rewards) for cost savings.
BYOL allows an enterprise to apply pre-existing Oracle software licences to equivalent Oracle Cloud services, yielding substantial savings since you are not "renting" the software licence from Oracle.
Active Support: Oracle mandates that any BYOL licence must have an active support contract. You continue paying Oracle annual support as if the licences were on-prem. If you stop support, you lose BYOL rights and upgrade entitlements. Ensure your Oracle CSI (Customer Support Identifier) is active for every licence you bring.
| Edition / Type | BYOL Conversion Rule | Limits |
|---|---|---|
| Enterprise Edition (Database, WebLogic Enterprise) | 1 Processor Licence = 2 OCPUs | No upper limit |
| Standard Edition (SE) | 1 Processor Licence = 4 OCPUs | Max 16 OCPUs per instance |
| Standard Edition 2 (SE2) | 1 Processor Licence = 4 OCPUs | Max 8 OCPUs per instance |
| Named User Plus (NUP) | Standard NUP minimums apply | 25 NUP per processor for EE DB |
IaaS (Self-Managed): BYOL operates exactly as on your own hardware — allocate licences for CPUs used, including any database options or packs you enable. Full responsibility for compliance.
PaaS (Oracle-Managed): Provision as "BYOL" for a lower hourly rate. Oracle includes rights to Diagnostic Pack, Tuning Pack, Data Masking and Subsetting, and Real Application Testing at no additional licence cost — even if your on-prem licence didn't include those. Other options (Multitenant, Partitioning, Advanced Security) must also be licensed via BYOL if used.
Java SE: OCI does not automatically include Java SE rights. If your workloads use Oracle's Java SE (Oracle JDK), you must have a Java SE subscription for the appropriate metric (Oracle moved Java SE to a subscription model, often per employee or processor). You can use your Java SE subscription licences in the cloud as on-prem. CIOs should ensure any Java usage in OCI is covered by existing subscriptions (BYOL) or by switching to open-source Java alternatives.
In summary, all major Oracle middleware and development licences — WebLogic, SOA Suite, Oracle HTTP Server — can generally be ported to OCI, either on IaaS or via Oracle's PaaS services.
| Factor | Licence-Included | BYOL |
|---|---|---|
| Cost | Higher hourly rate (licence bundled) | Significantly lower rate (infra only) |
| Pre-requisite | No existing licences needed | Must own equivalent licences + active support |
| Features | All options/packs generally enabled | Only features you're licensed for |
| Compliance | Oracle handles it | Customer must track and verify |
| Best for | Short-term, burst, or new projects | Long-running production with existing licences |
| Factor | Pay-As-You-Go (PAYG) | Annual Flex (Universal Credits) |
|---|---|---|
| Commitment | None — pure consumption | Annual or multi-year committed spend |
| Pricing | List paygo rates (baseline/highest) | ~30–35% lower than paygo rates |
| Billing | Monthly in arrears | Prepaid (annual), then consume against pool |
| Risk | No waste risk, but highest unit cost | Unused credits expire ("use it or lose it") |
| Best for | Trial, dev, unpredictable workloads | Production, steady-state deployments |
Standard rate: 25 cents in support credit for every $1 spent on OCI.
ULA customers: 33 cents per $1 — a higher rate to incentivise cloud adoption.
Application: Rewards can reduce your Oracle technology licence support invoices (Database, Middleware, Java) — even to $0 if OCI spend is high enough.
If you spend $1M on OCI annually, you earn $250K in Support Rewards (or $330K if ULA). Applied against your maintenance renewals, this dramatically improves the cloud business case and alleviates the "double spend" concern during migration — paying for cloud resources while still paying for on-prem support.
Migrating to OCI or optimising existing deployments with BYOL requires licence savvy and operational planning. The following 9-point framework guides CIOs in making the most of Oracle licensing in OCI.
Long-running production: BYOL will almost always be cost-effective. You avoid paying again for licences and pay only for cloud infrastructure.
New projects without spare licences: Compare purchasing new licences + BYOL against licence-included pricing. For short-term or small-scale use, the higher hourly rate might be simpler than procuring a new perpetual licence.
Dev/test/transient: Consider Oracle's free tier or licence-included on a short-term basis. Reserve BYOL for steady-state, heavy usage where it saves the most.
SaaS transition: If moving to Oracle Fusion Cloud (SaaS), BYOL for the interim is less relevant except for underlying tech (databases). Plan accordingly so you're not carrying support costs for licences that will be shelved.
Support Rewards: Factor into your ROI calculations. The more you move to OCI with BYOL, the more you offset support costs. Communicate this virtuous cycle to your CFO: cloud spend is partially returned as support savings.
Oracle Licence Mobility: OCI has unique advantages — the 2 OCPUs per licence ratio vs stricter counting on AWS/Azure. Oracle is also more lenient and integrated with licensing on OCI, so consolidating Oracle workloads on OCI simplifies compliance. Take advantage of any migration promotions (extra credits, free migration assistance).
For each system being moved, schedule the cutover within a 100-day window from when you first instantiate it on OCI using BYOL. Running longer than 100 days in both places would technically require extra licences or violate terms.
If delays occur: consider negotiating a short extension with Oracle, or temporarily switch the OCI instance to licence-included (so you're at least paying for the licence in the cloud after day 100).
Perpetual ULA (PULA): Oracle sometimes offers PULAs or extensions that include cloud usage rights. Weigh the costs — this can simplify compliance for very large customers.
Licence Migration Agreements: In some cases, Oracle may allow conversion of on-prem licences to cloud subscriptions (trade unused licences for cloud credit). This isn't a standard programme, but Oracle's sales teams have some flexibility, especially to lock you into OCI longer-term.
Ensure cloud admins select BYOL only when confirmed available licences exist. Maintain a central registry or request process.
Dashboards showing OCPUs in use under BYOL per product, compared against on-prem licence counts.
Tag OCI resources with licenseType=BYOL and which licence pool it maps to for audit readiness.
Use OCI compartments and IAM policies to restrict who can launch Oracle services. All Oracle software deployments through central governance.
Keep Proof of Entitlement: Maintain copies of licence agreements, proof of purchase, and current support status.
Periodic Self-Audit: Run Oracle audit scripts in your OCI environment. Check if any DBA is enabling options (partitioning, etc.) on a BYOL database that your licence doesn't cover.
New Cloud Services: If Oracle releases a new PaaS service and you want to use it under BYOL, check the fine print. Some cloud-only services have no on-prem equivalent, so BYOL doesn't apply.
Proactive Preparation: Having OCI usage data mapped to licences makes audits much smoother. If shortfalls exist, correct them before an official audit finds them.
Pilot Phase: Start with non-production and less critical systems to test BYOL processes, performance, and licence tracking. Surface configuration or tracking issues early.
Hybrid Transition: Run some workloads on-prem, some on OCI, to gradually shift capacity. Helps staff adapt and lets you measure cloud usage to refine Universal Credit needs.
Detailed Runbook: Each major system (e.g. Oracle ERP database) should have a migration runbook including a step for turning off the on-prem version and documenting the date — critical for proving 100-day rule adherence.
Cloud@Customer Option: For workloads with data residency or latency constraints, Oracle's Cloud@Customer (OCI in your data centre) allows a longer dual-use period of up to 180 days. BYOL applies similarly.
Procurement teams: Brief on how Universal Credits contracts work, billing management, and the "use it or lose it" expiration of uncommitted credits.
Oracle relationship: Get any special terms in writing (exceptions on licensing rules must be explicit in your contract or an addendum). Oracle often provides guidance — and pressure — for cloud migration.
Cloud architects: Train on the practical steps of implementing BYOL in OCI — choosing the BYOL option when launching an autonomous database, attaching licences for WebLogic JCS, etc. Avoid technical mistakes with licensing consequences.
For a CIO ready to implement an Oracle OCI and BYOL strategy, here is a concise action plan.
Create a detailed list of all Oracle software licences — types (Enterprise vs Standard), quantities, and support status. Map current on-prem usage and identify OCI migration candidates.
For each target workload, determine if you have sufficient licences to BYOL or need licence-included. Prioritise workloads where BYOL yields greatest savings (e.g. large databases already paying support).
Discuss cloud plans with Oracle. Enable Support Rewards in your contract. Gather Oracle documentation on BYOL policies. Negotiate a Universal Credits agreement aligned with projected OCI spend.
Establish internal processes for OCI deployments: require approval to use BYOL for new instances, tied to verifying available licences. Set up tagging and monitoring in your OCI tenancy.
Launch a small-scale pilot migration using BYOL — e.g. a development database or non-critical application. Validate performance, cost, and licence tracking. Adjust plans based on lessons learned.
Develop a phased schedule for larger systems. Use the 100-day dual-use window wisely. Checklist per wave: provision in OCI (BYOL mode), migrate data/config, test, switch production, decommission on-prem.
Verify BYOL instances stay within entitlement limits. Optimise cloud usage (right-size VMs, auto-scaling) to avoid wasting credits. Track Support Reward accrual and apply to reduce support invoices.
Document every BYOL deployment with its corresponding licence assignment. Keep records of when on-prem instances were turned off. Prepare a "licensing dossier" for audit readiness.
Quarterly or bi-annually review overall OCI licensing strategy. Has usage changed? Need to true-up licences or terminate unused ones? Adjust Universal Credit commitment for the next period. Stay updated on Oracle policy changes.
Need help with Oracle Cloud licensing strategy?
Oracle Advisory Services →By executing this strategic approach, CIOs turn Oracle's licensing complexity into an advantage — leveraging BYOL to preserve existing investments, using Universal Credits for flexible consumption, and applying Support Rewards to reduce total cost of ownership. The result: an optimised OCI environment that remains agile, audit-ready, and fully capitalises on prior Oracle investments throughout the cloud journey.
Download independent guides on OCI licensing, BYOL strategies, and cloud migration planning
Share your Oracle licence inventory, target workloads, and OCI deployment plans. We'll provide an independent BYOL mapping, compliance assessment, and cost optimisation strategy.