The EBS to Fusion Migration Is Not a Lift-and-Shift — It Is a Commercial Renegotiation With Oracle
Oracle E-Business Suite (EBS) is one of Oracle's longest-running on-premises ERP platforms. Oracle Fusion Cloud (now marketed as Oracle Cloud ERP and Oracle Cloud HCM) is its cloud-native replacement. Oracle's official position is that EBS customers should migrate to Fusion — and Oracle's account teams actively push this transition through a combination of product roadmap messaging ("EBS will not receive new features") and migration incentive offers ("we'll give you credits for migrating"). The commercial reality is considerably more complex. Migrating from EBS to Fusion involves replacing a perpetual licence and annual support model with a subscription model — a fundamental change in how Oracle costs are recognised and paid — and the total cost of migration typically exceeds Oracle's initial commercial framing by a factor of 2–3×. This guide provides the commercial analysis organisations need to evaluate the EBS-to-Fusion decision objectively, negotiate the migration deal fairly, and structure the timeline to maximise leverage. For Oracle Fusion ERP module pricing in detail, see our companion Oracle Fusion Cloud ERP Pricing Guide. For EBS migration advisory, our Oracle advisory team provides independent commercial analysis independent of Oracle's account team framing.
EBS Licensing Economics: What You Have and What It Costs You
Oracle EBS is licensed on a perpetual basis — organisations paid a one-time licence fee and pay ongoing annual support at 22% of net licence fees. For a typical mid-sized EBS estate (Financials, Procurement, Supply Chain, HR), perpetual licence fees paid may range from $2M to $15M, with annual support of $440k to $3.3M. The support cost compounds with Oracle's annual price increases (3–5%/year). The operational model requires a DBA team, server infrastructure, operating system management, and ongoing customisation maintenance — costs Oracle frequently does not include in its migration business case materials.
Oracle's EBS product roadmap commits to "Sustaining Support" until at least 2030 for Release 12.2 — meaning EBS will continue to receive security patches and break/fix support but will not receive new features, new country localizations, or new regulatory updates beyond what Oracle deems critical. This is Oracle's primary commercial pressure point: "your EBS investment is essentially frozen." The question for commercial analysis is whether the features and regulatory updates that Fusion provides justify the subscription cost premium over continuing EBS.
What Migrating to Fusion Actually Costs: The Full Commercial Picture
Oracle's Fusion Cloud pricing is subscription-based, charged per user per month (or per employee for HCM). The migration involves replacing perpetual licences (sunk cost, already paid) with an ongoing subscription. The commercial factors that Oracle's migration pitch frequently understates:
| Cost Component | Oracle's Migration Framing | Full Commercial Reality |
|---|---|---|
| Fusion subscription cost | "Start at $X/user/month" | Full module stack for EBS feature parity is typically 3–5× the starter module price; user count scope is often underestimated |
| EBS perpetual licence value | "We'll give you migration credits" | Migration credits are typically 25–50% of remaining support cost, not licence value — perpetual licences have no buyback value |
| Implementation services | Oracle lists indicative partner rates | EBS-to-Fusion implementations average 18–36 months and $2M–$12M+ in SI fees for mid-to-large organisations |
| Customisation migration | "Fusion is best-practice, reconfigure not rewrite" | EBS customisations (RICE objects, custom workflows, integrations) require significant re-engineering — budget 25–40% of SI cost |
| Data migration | Oracle provides migration tools | Data cleansing, transformation, and validation for a mature EBS estate typically requires 6–12 months of specialist effort |
| Parallel running period | Not mentioned | Most organisations run EBS and Fusion in parallel for 3–6 months during cutover, incurring both subscription and support costs simultaneously |
| Training and change management | Oracle provides learning subscriptions | Fusion's interface and process differences from EBS require structured retraining — typically $200k–$1M+ depending on user population |
The perpetual licence trap: EBS perpetual licences have no resale value and no credit value in Oracle's migration programme beyond a small discount on Fusion subscription cost. If an organisation paid $5M in EBS licence fees 10 years ago, that $5M is a sunk cost that does not offset the Fusion subscription cost in any meaningful way. Oracle's migration credits — offered as "we'll apply your support payments toward Fusion" — are typically structured as a discount on the first 1–2 years of Fusion subscription, not as recognition of perpetual licence value. The migration decision must be evaluated based on going-forward costs, not on recovering historical EBS licence investment.
How to Negotiate the EBS-to-Fusion Migration Deal
The EBS-to-Fusion migration negotiation is one of Oracle's highest-priority commercial conversations — Oracle has aggressive internal targets for cloud revenue, and EBS-to-Fusion migrations are the single largest source of Oracle cloud subscription growth. This priority creates genuine negotiation leverage for EBS customers:
Time the negotiation to Oracle's fiscal year end. Oracle's fiscal year ends May 31. Q4 (March–May) is when Oracle's cloud sales teams have the most flexibility on Fusion subscription pricing, migration credits, and implementation funding. Entering the Fusion migration conversation in Q4 with a committed timeline is the highest-leverage commercial position.
Negotiate support cost reduction for the EBS estate during migration. The transition period — from Fusion project start to EBS decommission — typically spans 2–3 years. Oracle should discount EBS support during the migration period as part of the overall migration deal. A 20–35% EBS support reduction for the duration of the transition is achievable when the Fusion migration commitment is credible and the total deal value is significant.
Anchor the Fusion subscription at total contract value, not per-user rate. Oracle's Fusion list prices are published per user per month, but negotiated deals are structured on total contract value. A 3-year Fusion subscription commitment at $3M total value will be discounted differently (and more aggressively) than the same users at list rate for one year at a time. Commit to a 3-year term with year-over-year growth baked in to maximise the discount Oracle will apply.
Require implementation funding as part of the migration deal. Oracle has Cloud Lift implementation funding — Oracle-funded implementation services for qualifying Fusion migrations. The amount of Oracle-funded implementation support available depends on the Fusion subscription value and Oracle's cloud revenue priority for your account. This funding is negotiated, not automatically offered — it must be specifically requested and sized as part of the overall migration commercial package. For EBS-to-Fusion migration advisory and Oracle negotiation support, our Oracle advisory team provides independent commercial analysis and manages the Oracle negotiation. Book an EBS migration advisory session to start the evaluation.
Get Independent Oracle EBS-to-Fusion Migration Advisory
Our Oracle advisory team provides independent commercial analysis of EBS vs Fusion going-forward costs, benchmarks Fusion subscription pricing against current market deals, models the full migration cost including implementation and parallel running, and manages the Oracle negotiation to maximise migration credits and implementation funding.
Book an EBS Migration Advisory Session →