The Oracle E-Business Suite negotiation guide.

A buyer side pillar article on negotiating Oracle E-Business Suite renewals, support uplift, module rationalisation, and the migration decision between staying on premise and moving to Fusion Cloud or a third party ERP.

Oracle E-Business Suite remains one of the most widely deployed enterprise resource planning suites in the world, with thousands of customers running EBS Financials, Supply Chain, Manufacturing, and Human Resources modules on premise. Oracle's product roadmap commits premier support for EBS 12.2 through at least 2034, which removes the forced migration argument that was used in renewal conversations from 2018 to 2022. The result is a different negotiation. Customers are renewing existing EBS perpetual licence support, rationalising unused modules, considering migration to Oracle Fusion Cloud, and increasingly considering third party support providers.

This pillar article presents the buyer side framework for EBS negotiations in 2026. It covers the support uplift conversation, the unused module rationalisation opportunity, the Fusion Cloud migration cost arithmetic, the third party support alternative, and the contract clauses that govern each of these decisions. Across our EBS engagements the median support saving against Oracle's first renewal position is 24 percent, achieved through module rationalisation, support cap negotiation, and structured competitive alternatives.

What Oracle EBS actually is in 2026.

Oracle E-Business Suite is Oracle's flagship on premise ERP suite, originally assembled from the 1990s acquisitions of Oracle Applications and post 2000 development. The current supported release is EBS 12.2, with continuous innovation releases delivered through the 12.2 codebase. Oracle has committed premier support for EBS 12.2 through 2034 and has extended that commitment in successive product roadmap updates.

EBS is licensed by module under perpetual licences. The main module families are Financials, Supply Chain Management, Manufacturing, Human Resources, Procurement, and Project Management. Each family contains multiple individual licensed modules, often with named user metrics and occasionally with processor or revenue based metrics. Annual support is 22 percent of the net licence value, applied per module, with annual support uplift bounded by the cap clause in the original contract.

The product is mature, stable, and customised heavily at most large customers. Migration costs are large because the customisations carry forward poorly into Fusion Cloud and require redesign rather than lift and shift. This dynamic shapes every EBS negotiation. The cost of leaving Oracle is high, which gives Oracle leverage. The buyer side framework starts with understanding that leverage and then countering it.

The support uplift conversation.

Most EBS customers have been on the same Oracle support contract for ten years or more. The annual support invoice arrives, the uplift is applied, the invoice is paid. Few customers actively negotiate EBS support each year. That passivity is expensive.

Three negotiation moves are available on EBS support each renewal. First, the cap clause review. Most EBS contracts have an annual support uplift cap, typically expressed as a fixed percentage or as the Oracle price list increase, whichever is lower. Verifying that the applied uplift matches the contracted cap recovers material money on long running contracts where the wrong cap has been applied for years.

Second, the module rationalisation opportunity. Most EBS estates have modules that were licensed years ago, have low or zero current usage, and continue to incur 22 percent annual support. Identifying and dropping unused modules reduces the support base permanently. This is the largest single saving available on most EBS renewals.

Third, the structured competitive alternative. Bringing a third party support provider quote into the renewal conversation, or a credible Fusion Cloud migration cost, anchors the negotiation against the cost of leaving Oracle support. The discount that is then available on Oracle support is meaningful. For the full treatment see our renewal negotiation service.

Unused module rationalisation.

EBS estates are typically licensed broader than they are deployed. The pattern is consistent across customers. A module is purchased to support a planned project that did not complete. A module was bundled into an enterprise deal and never deployed. A module supported a business line that has been divested or restructured. The licence remains on the contract, the support is paid annually, and the module is not used.

Identifying unused modules requires usage analysis across the EBS estate. The data sources are deployed schemas in the EBS database, named user listings in the application, and business interviews with the application owners. A structured review across the support boundary typically identifies 10 to 25 percent of contracted modules that are candidates for support drop or licence retirement.

Dropping support on a subset of modules is contractually possible but requires careful execution. The drop must respect the matching service levels clause, the technology product dependency clause, and the geographic deployment clause. Done correctly the support base reduces permanently and the saving compounds over the post drop years. Done incorrectly the matching service levels clause forces support reinstatement at penalty rates. For the structured approach see our article on support reinstatement fees.

Fusion Cloud migration arithmetic.

Oracle's preferred end state for EBS customers is Fusion Cloud Applications. The Oracle account team will routinely propose Fusion migration as the answer to any EBS renewal conversation. The buyer side framework requires real cost arithmetic on the migration before the answer is yes or no.

Fusion Cloud is subscription priced, with annual fees that are typically higher than the EBS annual support spend on a like for like module basis. The migration project itself is multi year and multi million dollar at most large customers, with system integrator fees that often exceed the annual licence cost by a factor of three to five. The total cost of migration over the first five years is generally higher than the cost of remaining on EBS over the same period, before any productivity benefit is considered.

Fusion makes commercial sense in three specific cases. Where the EBS customisation footprint is small and a clean reimplementation is achievable at moderate cost. Where the customer is also moving to OCI or another cloud and wants to consolidate the application estate. Where Oracle is offering migration incentives that materially offset the first two years of subscription cost. None of those cases is the default. Most EBS customers should defer the Fusion conversation until 2030 at the earliest, when the EBS 2034 support commitment becomes a nearer term consideration.

For deal structure see our Apps Unlimited deal page, which is the typical instrument Oracle proposes for the Fusion conversion.

Third party support as leverage.

Rimini Street, Spinnaker Support, and Support Revolution provide third party support for EBS at substantially lower cost than Oracle, typically half the Oracle support rate or less. Customers move to third party support to reduce annual cost, to access support on older EBS releases Oracle has effectively deprioritised, or to free up budget for migration to another ERP.

Third party support has commercial trade offs. Oracle no longer provides patches, security updates, or tax legislation updates to the customer. The third party provider provides those services from their own engineering capacity. Most customers running EBS on a stable release with minimal regulatory change can run on third party support indefinitely. Customers in industries with heavy regulatory change should validate the third party provider tax update coverage before switching.

Bringing a third party support quote into the Oracle renewal conversation is a structured negotiating tactic. The credible alternative anchors the discount Oracle is willing to offer. Customers who go through the quote process and use it as leverage typically achieve 15 to 30 percent reduction on Oracle support without actually switching providers. For the full negotiation framework see the contract review service.

Module specific pricing patterns.

EBS modules have specific pricing patterns that recur across customers and matter at renewal. Financials modules are typically named user licensed with high user counts. The named user count rarely matches the actual active user count, especially in long running deployments where users have left the organisation. Reconciling named user lists against active employees often surfaces material licence reductions.

Manufacturing and Supply Chain modules are licensed by named user at the operational level but often have processor based components for shop floor systems. The metric switch happens at deployment points that are not always obvious. Reviewing the metric on each module against actual deployment is a routine source of saving.

Human Resources modules are sometimes licensed on a revenue or headcount basis under older contract structures. Where the revenue or headcount basis is favourable to the customer the calculation should be confirmed against current company metrics. Where it is unfavourable the renewal is an opportunity to move to a named user metric. See our article on EBS HRMS module pricing for the detail.

The migration versus stay decision.

The single most consequential decision in EBS strategy is whether to migrate, when, and to what. The three plausible end states are Fusion Cloud, a non Oracle ERP such as SAP S/4HANA or Workday, or continuing on EBS through the 2034 support commitment with periodic re evaluation. Each path has cost, risk, and operational implications across a multi year horizon.

The decision framework should weigh five inputs. The total cost of ownership over a ten year horizon for each path, including migration cost, run cost, and Oracle support exit cost. The risk of staying on a maturing product set versus the risk of a multi year migration project. The strategic alignment with the organisation's broader cloud and digital transformation roadmap. The internal capacity to execute a migration project. The supplier concentration risk of moving more or less of the application portfolio onto Oracle.

For most EBS customers the right answer in 2026 is to stay, rationalise, renew on improved commercial terms, and re evaluate the migration question every two years. The 2034 support horizon allows that posture. The Fusion conversation that Oracle pushes hardest is typically not the conversation the buyer should have first. See our article on EBS migration versus stay decision for the structured comparison.

Frequently asked questions.