The Licensing Dimension of Oracle EBS Cloud Migration

Oracle EBS support costs increase at 8% per year without fail. An organisation paying $2M annually in 2020 will pay approximately $2.94M for the same coverage in 2026 — a 47% increase for unchanged software. That cost pressure is driving EBS-to-cloud migration decisions across every industry, but the transition itself creates hidden licensing exposure that consistently exceeds the cost of the migration project, the conversation in most project steering committees centres on technical complexity, data migration, customisation redevelopment, and change management. Licensing is typically treated as an afterthought — something Oracle's account team will "sort out" during the commercial conversation. This is a mistake with material financial consequences.

The licensing workstream of an Oracle EBS cloud migration has three distinct phases, each with its own risks: the pre-migration period (during which EBS support costs continue to escalate), the transition period (during which dual-run costs accumulate), and the post-migration period (during which EBS perpetual licences may have residual value that is often surrendered unnecessarily). Each phase requires active management to avoid leaving significant money on the table or creating compliance exposure.

A FTSE 100 retailer began migrating Oracle EBS to Fusion Cloud without addressing the dual-run licensing period. Oracle identified 22 months of overlapping licence obligations. The initial claim was $5.6M. Working with our Oracle licensing advisory specialists, the final settlement reached $740,000 — a saving of $4.86M. Our engagement fee was under 2% of the exposure.

Why EBS Licences Do Not Transfer to Oracle Cloud Subscriptions

One of the most common misunderstandings about Oracle EBS cloud migration is that existing EBS perpetual licences can be applied to Oracle Cloud subscriptions. They cannot. Oracle's EBS perpetual licences are on-premises software licences — they entitle the holder to run specific EBS application modules on their own hardware infrastructure indefinitely. Oracle Fusion Cloud Applications are subscription services — an entirely different commercial model with no direct licence equivalence.

This means that moving to Oracle Fusion Cloud requires purchasing new subscription contracts, not converting old licences. The EBS perpetual licences remain valid (the organisation can continue running EBS) but they create no contractual entitlement to Oracle Cloud services. Oracle may offer commercial incentives during migration negotiations — in the form of credits or reduced subscription pricing — but these are the result of negotiation, not licence portability.

"Moving to Oracle Fusion Cloud does not mean your EBS licences are 'used up' or converted. You retain perpetual rights to run EBS on-premises. Understanding this is critical to your negotiation position."

The Dual-Run Problem: Paying Twice for the Same Functionality

In practice, most Oracle EBS to Oracle Cloud migrations take between 12 and 24 months from project initiation to decommission. During that period, the organisation pays for both its existing EBS support contracts and its new Oracle Cloud subscriptions — often for the same business functions. For a large EBS deployment with an annual support bill of several million dollars, a 24-month dual-run period can mean an additional $4–8 million in cloud subscription costs on top of EBS support that is already running at 22% of licence value, increasing at 8% per year.

The strategies for managing dual-run costs are not complicated, but they require advance planning and leverage that can only be established before the migration project begins:

  • Time your cloud negotiation against your EBS support renewal date. Oracle's fiscal year ends May 31, with their most aggressive sales push happening in the March–May Q4 window. If your EBS support renews in April, Oracle is under intense pressure to close cloud deals. This creates negotiating leverage that disappears once the renewal is signed.
  • Negotiate a cloud credit for EBS support pre-payment. Some organisations negotiate a lump-sum credit towards cloud subscriptions in exchange for committing to a multi-year cloud term at renewal. The credit is typically 25–50% of annual EBS support value — meaningful but not automatic.
  • Secure a support reduction schedule tied to decommission milestones. Negotiate a contractual right to reduce EBS support costs as modules are decommissioned during the migration, rather than carrying full EBS support until the last module is retired.

Migration as an Audit Trigger

Oracle's sales and audit teams work more closely than most customers appreciate. When Oracle's account team becomes aware that an organisation is evaluating a cloud migration, Oracle's LMS (Licence Management Services) team frequently initiates an audit review of the existing EBS deployment in the same period. The rationale, from Oracle's perspective, is straightforward: a customer under audit pressure is more motivated to settle by purchasing cloud subscriptions.

Common EBS compliance findings that surface during migration-adjacent audits include: users who have been given access to EBS modules they are not licensed for, processor licensing gaps in the underlying Oracle Database infrastructure supporting EBS, middleware licensing issues where EBS customisations have triggered full-use WebLogic obligations, and support gaps where licences acquired through third parties do not match Oracle's CSI records.

The practical implication is that before initiating formal cloud migration discussions with Oracle's account team, organisations should conduct an internal EBS licence review to understand their current compliance position. Addressing compliance gaps proactively — ideally before Oracle requests an audit — is almost always cheaper than addressing them under audit pressure.

Planning an Oracle EBS to cloud migration?

Our advisors manage the licensing workstream — from pre-migration compliance review through cloud contract negotiation and dual-run cost management.
Talk to an Advisor

Oracle EBS on OCI: The Lift-and-Shift Alternative

Not all EBS customers are ready to migrate to Oracle Fusion Cloud. For organisations with significant EBS customisations, complex integrations, or limited appetite for the business change involved in a Fusion migration, Oracle Cloud Infrastructure (OCI) provides an alternative: lift-and-shift migration of EBS to OCI without replacing the application.

Running EBS on OCI has several licensing advantages compared to running it on other cloud providers such as AWS or Azure. On OCI, Oracle allows Bring Your Own Licence (BYOL) with sub-capacity OCPU licensing — meaning you can licence individual OCPUs rather than entire physical hosts. On AWS and Azure, Oracle requires you to licence the full virtual machine host, which in many configurations is significantly more expensive per processor equivalent.

The trade-off is commercial dependency: running EBS on OCI creates a tighter relationship with Oracle that can make future negotiations more complex. Organisations should model both the licensing cost and the negotiating leverage implications before committing to OCI as the long-term EBS platform.

EBS Support and the 8% Annual Increase

One of the most important financial drivers pushing EBS customers towards cloud migration is the annual 8% increase in Oracle support fees. Annual support (Software Update Licence and Support, or SULS) is priced at 22% of the net licence value and increases at 8% per year. For an organisation that paid $2 million in EBS support in 2020, the same support contract would cost approximately $2.94 million in 2026 — an increase of nearly 50% over six years, for the same software.

Oracle's position is that the 8% annual increase is contractual and non-negotiable within an existing support term. In practice, at renewal, organisations with leverage — particularly those actively evaluating cloud migration — can negotiate support fee caps, multi-year price locks, or credits that partially offset the escalation. But this requires a structured negotiation approach, not simply accepting the renewal invoice.

What Happens to EBS Licences After Cloud Migration

A critical and often overlooked question is: what rights do you retain to your EBS perpetual licences after migrating to Oracle Fusion Cloud? The answer depends on the terms negotiated in the cloud migration agreement. In some cases, Oracle's migration agreements include surrender provisions — the customer implicitly or explicitly gives up their EBS perpetual licence rights as part of the cloud commitment. In other cases, the perpetual licences are retained and could be used to run EBS in future or transferred within a corporate group.

Before signing any Oracle cloud migration agreement, organisations should have the contract reviewed by an independent Oracle licensing specialist to ensure that perpetual licence rights are explicitly preserved if desired. Once these rights are surrendered, they cannot be recovered — and they represent a tangible asset that may have future value, either for continued EBS use in subsidiary entities, for third-party support arrangements, or as negotiating leverage in future Oracle discussions.

Key Negotiation Principles for EBS Cloud Migration

The following principles govern the most successful Oracle EBS cloud migration commercial negotiations that Redress Compliance advisors have supported:

  • Never start cloud discussions during a renewal without a full cost model. Oracle's Q4 pressure (March–May) benefits the customer who is prepared — and benefits Oracle if the customer is not.
  • Quantify your dual-run exposure before entering negotiations. Knowing your exact 18-month dual-run cost gives you a concrete number to drive cloud subscription and credit discussions.
  • Retain an independent adviser for the commercial workstream. Oracle's account team and your project management office are not aligned in their interests during a cloud migration negotiation. Independent advisory is the equaliser.
  • Preserve perpetual licence rights contractually. Never surrender EBS perpetual licences without explicit written confirmation of what you receive in return — and independent advice on whether that trade is commercially rational.
  • Conduct an EBS compliance review before audit exposure arises. The worst time to discover an EBS compliance gap is during a migration negotiation. Know your position before Oracle knows it.

Frequently Asked Questions

Can Oracle force me to migrate from EBS to Fusion Cloud?

No. Oracle EBS perpetual licences include the right to continue running EBS on-premises indefinitely, subject to maintaining support. Oracle cannot contractually require you to migrate to Fusion Cloud. However, Oracle may limit future EBS support commitments, making migration economically preferable over time.

Will Oracle give me credit for my EBS licences when I move to Fusion Cloud?

Oracle does not have a published policy of automatic credit for EBS licences on Fusion Cloud subscription purchases. Credits are commercially negotiated and are not guaranteed. Organisations with strong leverage — particularly those in Oracle's fiscal Q4 renewal window — can negotiate credits typically representing 25–50% of annual EBS support value.

Does migrating to OCI affect my EBS licence?

Migrating EBS to OCI is a deployment change, not a licence change. Your existing EBS perpetual licences remain valid for use on OCI under BYOL terms. The licensing advantage of OCI over AWS or Azure is the ability to licence individual OCPUs rather than full host processors.