Oracle actively incentivises on-premises customers to migrate workloads to OCI through migration credit programmes, BYOL policies, and Annual Commit deals. Understanding how these programmes work — and how to negotiate them independently — is essential for any organisation evaluating Oracle cloud strategy. This guide covers the mechanics, the economics, and the negotiation tactics for Oracle OCI migration credits in 2026.
Oracle cloud migration credits are OCI (Oracle Cloud Infrastructure) service credits offered by Oracle as part of commercial deals designed to accelerate migration of on-premises Oracle workloads to OCI. These credits reduce the effective OCI spend during the migration period and are typically structured as a percentage of the total OCI Annual Commit — for example, credits representing 20–30% of the first year's OCI commit applied to the OCI bill.
Migration credits are distinct from OCI discounts: credits are time-limited and apply to specific OCI consumption, while discounts reduce the OCI list price permanently (or for the commit period). Oracle's commercial team will often offer a combination of both — a base OCI discount on the Annual Commit plus migration credits for the initial migration period. Understanding which element is which, and modelling both independently, is important for evaluating the total deal value.
This guide is part of our broader Oracle license negotiation pillar guide, which covers the full spectrum of Oracle commercial strategy. For OCI pricing negotiation specifically, see our Oracle OCI pricing negotiation guide. For the context of how on-premises licences can be monetised in cloud migration deals, see our Oracle license optimization guide.
Oracle's OCI migration credit programmes are fundamentally a customer acquisition strategy for OCI — Oracle is using the value of on-premises licence holdings as an incentive to drive OCI commits. This is not inherently problematic for the buyer, but it means the migration credit deal must be evaluated on OCI's merits as a cloud platform, not just on the credit value. Credits that require a three-year OCI Annual Commit to an overpriced platform are not good value regardless of their face amount.
Oracle's Bring Your Own Licence (BYOL) programme is the most structurally important element of OCI economics for organisations with significant on-premises Oracle licence holdings. BYOL allows existing perpetual Oracle licences (with active Oracle Support) to be used on OCI rather than purchasing new cloud licences — typically reducing OCI compute costs for Oracle Database workloads by 50–70% compared to licence-included OCI pricing.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
The mechanics of BYOL on OCI are: the organisation uses its existing on-premises perpetual licences to license Oracle Database (or other eligible products) running on OCI; the OCI pricing for BYOL instances is lower than licence-included pricing, because the licence component is not included in the OCI charge; the on-premises licences used for BYOL on OCI cannot simultaneously be used on-premises during the period they are deployed on OCI (licence mobility rules require this).
BYOL eligibility is product-specific. Oracle Database Standard Edition 2 and Enterprise Edition are eligible for OCI BYOL. Oracle Database Enterprise Edition options (Partitioning, Advanced Security, RAC, etc.) can also be BYOLed on OCI. Java SE licences are not eligible for BYOL on OCI in the same way. Oracle Middleware products have varying BYOL eligibility that must be verified against the current Oracle Cloud Licensing policy document.
Eligible: Oracle DB SE2, EE, and EE Options with active Oracle Support.
Saving: 50–70% vs licence-included OCI pricing for Database workloads.
Eligible: WebLogic, Coherence, SOA Suite — verify current policy for specific products.
Saving: Varies by product; WebLogic BYOL typically saves 40–60% vs licence-included.
Unique to OCI: Oracle recognises OCI VM shapes as hard partitioning — licences cover only the OCPU allocated, not the full physical host.
Impact: Dramatically lower licence requirement vs AWS/Azure for DB workloads.
Condition: BYOL requires active Oracle Premier Support on the on-premises licences being used on OCI.
Implication: Third-party support and BYOL are incompatible — review if considering both.
The single most commercially significant difference between OCI and other hyperscalers for Oracle Database workloads is Oracle's hard partitioning policy. On OCI, Oracle recognises each OCI VM shape's allocated OCPU count as the licensing unit — meaning you licence only the OCPU resources your Oracle Database VM is actually using, not the full physical server. On AWS and Azure, Oracle does not recognise the underlying virtualisation as hard partitioning (with narrow exceptions), which means Oracle Database deployed on an EC2 or Azure VM instance may require licences for every CPU on the underlying physical host — a potentially massive difference in licence requirement.
This hard partitioning difference can make OCI significantly cheaper than AWS or Azure for Oracle Database workloads — not because OCI infrastructure is cheaper per OCPU, but because the Oracle licence requirement is lower. For organisations with large Oracle Database licence holdings, this licensing advantage can outweigh higher OCI infrastructure costs. The analysis requires detailed licence modelling against actual workload requirements. Our Oracle licence calculation guide provides the methodology for this comparison.
However, the hard partitioning advantage applies specifically to Oracle Database. For non-Oracle workloads, or for organisations with mixed Oracle and non-Oracle cloud requirements, OCI's infrastructure economics must stand on their own merits against AWS and Azure. A comprehensive cloud platform evaluation should assess OCI pricing across the full workload mix — not just the Oracle Database component.
Oracle's OCI Annual Commit (formerly Universal Credits) is the standard commercial vehicle for OCI consumption. The OCI Annual Commit provides a fixed annual spend commitment in exchange for a discount on OCI list prices — the larger the annual commit, the larger the discount Oracle is willing to offer. Migration credits are typically layered on top of the Annual Commit discount as additional incentive.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
Key negotiation parameters for OCI Annual Commit deals are: the discount percentage off OCI list; the term (typically one to three years); the overage provisions (what happens if actual OCI consumption exceeds the commit); the underage provisions (what happens if the organisation spends less than the commit); credit carryover (whether unused credits roll to the next year); and the services scope (whether the commit applies to all OCI services or specific ones). For detailed OCI pricing negotiation tactics, see our dedicated Oracle OCI pricing negotiation guide.
Evaluating an OCI migration credit deal? Get independent advisory before committing.
Oracle runs several structured migration incentive programmes that may be available depending on the customer's size, Oracle relationship, and migration intent. These programmes change regularly as Oracle adjusts its OCI growth strategy, so the specific programme names and terms available in 2026 should be verified with Oracle's cloud commercial team and — critically — evaluated independently before accepting them.
Common migration incentive structures include: Licence Migration Credits, where Oracle credits a portion of the existing on-premises licence value toward OCI Annual Commit; Migration Support Credits, which provide OCI credits specifically for migration workloads during a transition period; Hybrid Consumption Credit arrangements, where existing Oracle on-premises support spend is partially credited toward OCI consumption; and custom deal structures for large enterprises where Oracle's strategic accounts team has latitude to construct bespoke incentive packages.
In all cases, the migration incentive must be evaluated against the total OCI commitment required to access it. A large migration credit that requires a disproportionate OCI Annual Commit — locking the organisation into above-market OCI pricing for three years — may have negative NPV despite appearing generous. Independent evaluation against AWS and Azure equivalent pricing is essential before any commitment is made.
Oracle's commercial team has significant flexibility in constructing OCI migration credit deals, and the headline terms offered at the start of a negotiation are rarely Oracle's best position. Effective OCI migration credit negotiation follows several principles.
First, establish genuine competitive alternatives. Oracle's OCI commercial team responds to credible AWS and Azure pricing comparisons. Having real AWS and Azure quotes for equivalent workloads — particularly Oracle Database workloads where the BYOL comparison is directly relevant — creates genuine leverage. Oracle knows that for Oracle Database workloads, OCI BYOL economics are typically favourable, which slightly reduces competitive pressure, but for non-Oracle workloads, AWS and Azure competition is real.
Second, benchmark OCI discounts against market before accepting Oracle's initial offer. OCI Annual Commit discounts are negotiable, and organisations with significant Oracle relationships regularly achieve meaningful discounts off OCI list. The appropriate discount level depends on commit size and term — seek independent benchmarking data before accepting Oracle's initial pricing. Our Oracle pricing benchmark guide covers how to benchmark Oracle commercial terms effectively.
Third, negotiate the overage and underage provisions carefully. OCI Annual Commit deals that penalise underspend — requiring payment for unused credits — carry real commercial risk for organisations whose OCI migration timeline is uncertain. Negotiating credit carryover, overage protection, and exit provisions is as important as negotiating the headline discount and credit amount. For broader Oracle negotiation strategy, see our Oracle negotiation firm rankings.
The most common OCI migration credit trap is accepting a migration credit deal without independently verifying OCI pricing competitiveness. Oracle's commercial team will present migration credits as free money — they are not. Migration credits require an OCI Annual Commit at Oracle's pricing, which must be independently benchmarked. Credits applied to an overpriced commitment represent zero real value.
A second trap is failing to model the BYOL licence availability. BYOL on OCI requires active Oracle Premier Support on the contributing licences. Organisations that are evaluating third-party Oracle support (see our third-party Oracle support guide) must understand that third-party support and OCI BYOL are mutually exclusive — the same licences cannot be on third-party support and used for BYOL simultaneously. This is an important factor in comparing the two strategies.
A third trap is underestimating OCI migration complexity and committing to an Annual Commit that the organisation cannot ramp into on the planned timeline. OCI Annual Commit underspend provisions can require payment for consumed credits regardless of whether the OCI services were used — creating stranded spend. Conservative Annual Commit sizing with credit carryover provisions is preferable to aggressive committing on an uncertain migration timeline.
Any OCI migration credit deal should be evaluated against three questions before commitment: Is OCI pricing competitive for the specific workloads being migrated, after BYOL and Annual Commit discounts? Does the total OCI Annual Commit level match a realistic migration roadmap, given the organisation's actual cloud adoption velocity? And what is the NPV of the migration credit value versus the total OCI commitment cost over the commit term?
These questions require independent analysis — not Oracle's modelling, which will naturally present OCI favourably. Oracle advisory firms with OCI commercial expertise, including those ranked in our Oracle negotiation firm rankings, can provide independent OCI deal evaluation and negotiation support. The IT contract negotiation buyer's guide covers how to structure and procure this kind of specialist advisory support. Download our free negotiation playbook for frameworks applicable to Oracle cloud commercial negotiations.
Oracle's migration credit deals can represent genuine value — but only if OCI pricing is competitive for your workloads and the Annual Commit matches your real migration trajectory. Independent advisory ensures you commit to the right deal.