Moving from Oracle E-Business Suite (EBS) to Oracle Fusion Cloud is one of the most consequential licensing decisions an enterprise will make. EBS licences are perpetual assets you own outright. Fusion Cloud is a SaaS subscription you rent. These two models do not convert into each other. This guide covers what happens to your perpetual licences, how Oracle’s credit programmes actually work, dual-run cost management, module mapping pitfalls, double-licensing avoidance, support strategy, negotiation leverage, and how to plan a clean licensing exit from EBS.
Oracle EBS licences are perpetual — you purchased them, and you own them indefinitely. Oracle Fusion Cloud ERP is sold as a SaaS subscription — you pay recurring fees and own nothing. These two models do not directly convert. There is no “licence swap” mechanism that transforms perpetual EBS entitlements into cloud subscriptions. Moving to the cloud means adding an entirely new subscription cost on top of your existing licence estate.
Your EBS licences remain your property regardless of whether you move to the cloud. Oracle will not take them back, buy them back, or formally retire them. However, the licences have no practical value without active support (no patches, no upgrades, no Oracle assistance), and Oracle’s support policies make it extremely expensive to reinstate support once terminated. This creates an asymmetric pressure: you own the licences, but Oracle controls whether they remain useful.
| Attribute | EBS Licence (On-Premises) | Oracle Fusion Cloud SaaS |
|---|---|---|
| Ownership model | Perpetual — one-time purchase, owned indefinitely | Subscription — recurring fee, no ownership; access terminates when subscription ends |
| Support & updates | Annual support fees (~22% of licence value); updates require active support | Included in subscription; automatic quarterly updates (mandatory) |
| Licence portability | Tied to on-premises deployment; cannot be applied to cloud subscriptions | Cannot use on-premises licences to offset SaaS costs — entirely separate model |
| Cost model | CapEx (licence purchase) + annual OpEx (support fees) | Pure OpEx (recurring subscription); typically 2–3× annual EBS support cost |
| Customisation | Full customisation of application code | Configuration only — no code customisation; extensions via PaaS (additional cost) |
| Exit flexibility | Perpetual ownership; can move to third-party support | No ownership at termination; all access ends; data extraction required |
Oracle’s sales teams often position the cloud transition as “upgrading” your EBS licences. This language is deliberately misleading. You are not upgrading — you are purchasing an entirely new product under an entirely different commercial model while your existing perpetual licences become dormant shelfware. The EBS licences you paid millions for do not reduce your Fusion Cloud cost unless you explicitly negotiate credit provisions. Without negotiation, you pay full price for the cloud subscription and continue paying EBS support until you actively terminate it.
Oracle offers several financial incentive programmes to encourage EBS-to-Cloud migration. These are positioned as “credits” for your existing investment, but in practice they are structured to maximise Oracle’s long-term subscription revenue while offering short-term relief that rarely offsets the true transition cost.
| Programme Type | How Oracle Positions It | How It Actually Works | Key Risk |
|---|---|---|---|
| Support fee credit | “We’ll credit your EBS support spend toward your cloud subscription” | Oracle applies a percentage of your current annual support fees as a discount against cloud subscription pricing — typically 50–80% of support value for Year 1 only | Credit often decreases or disappears in Years 2–3; cloud subscription price escalates while EBS support was flat or capped |
| Multi-year commitment discount | “Commit to 3–5 years and receive our best pricing” | Larger discounts (30–50% off list) in exchange for binding multi-year subscription. Annual price escalation of 3–7% typically embedded in contract. | Locked into a long-term commitment; annual increases compound; exit penalties if you want to reduce scope |
| EBS transition credit | “We’ll recognise your total EBS investment in the cloud deal” | Oracle calculates a credit based on historical EBS licence and support spend — applied as a one-time discount or free months on the cloud subscription | Credit value rarely exceeds 10–20% of total EBS investment; structured to expire within the first contract term |
| Support shelving / holiday | “We’ll pause your EBS support fees during migration” | Oracle temporarily reduces or suspends EBS support billing for 6–12 months while you implement Fusion Cloud | Shelving period is limited; if migration runs late, full support fees resume; must be explicitly negotiated |
| OCI consumption credits | “We’ll include OCI credits to run your EBS during transition” | Oracle provides Universal Cloud Credits for running EBS on OCI infrastructure during the migration period | Credits expire (typically 12 months); OCI pricing for EBS workloads may exceed on-premises infrastructure costs |
Consider a typical scenario: an organisation paying $2M/year in EBS support receives a “generous” support credit worth 70% of one year’s support ($1.4M) applied against a Fusion Cloud subscription priced at $4.5M/year. The credit reduces Year 1 to $3.1M — but Years 2–5 are $4.5M+ with 4% annual escalation. Total 5-year Fusion Cloud cost: ~$22.4M. Meanwhile, total 5-year EBS support (if they stayed on-premises) would have been ~$10.4M. The “credit” saved $1.4M once while committing the organisation to $12M+ in additional cost over 5 years. Always calculate the full multi-year comparison before accepting any credit programme.
The dual-run period — when EBS and Fusion Cloud operate simultaneously — is the most expensive and most underestimated phase of any cloud migration. Most organisations budget for 6–12 months of overlap; reality is typically 12–24 months, with some enterprises running dual systems for 36+ months across complex multi-country deployments.
| Cost Component | Typical Annual Cost | Dual-Run Impact | Mitigation Strategy |
|---|---|---|---|
| EBS annual support | $1M–$5M+ (22% of licence value) | Continues at full rate during entire dual-run period unless actively terminated or shelved | Negotiate support shelving clause; plan phased support termination by module |
| Fusion Cloud subscription | $2M–$10M+ (depends on scope and user count) | Begins at contract signature regardless of go-live date; billing does not pause for implementation delays | Negotiate subscription start date tied to go-live milestone; include delayed billing clause |
| Integration middleware | $200K–$1M (one-time + licensing) | Temporary integrations between EBS and Fusion Cloud required for data sync, master data management | Use pre-built Oracle integration tools (included in some cloud subscriptions); decommission immediately after cutover |
| IT staffing (dual support) | $300K–$1.5M (additional FTEs or contractors) | Teams must support both EBS and Cloud simultaneously — DBA, functional, security, reporting | Cross-train teams; use system integrator for Cloud support during transition; plan knowledge transfer early |
| Dual infrastructure | $100K–$500K (on-premises + cloud hosting) | On-premises hardware for EBS + cloud infrastructure costs for Fusion | Consolidate EBS to smaller infrastructure as modules are migrated; consider OCI for EBS during transition |
Oracle Fusion Cloud modules are not identical to EBS modules. Features are reorganised, split into separate cloud services, bundled differently, renamed, and in some cases eliminated entirely. A direct one-to-one module mapping does not exist — and assuming it does creates both licensing gaps (missing functionality) and cost overruns (over-subscribing to cloud modules you do not need).
| EBS Module | Fusion Cloud Equivalent | Mapping Complexity | Licensing Implication |
|---|---|---|---|
| General Ledger | Financial Cloud — GL | Relatively direct mapping | Cloud subscription metric (user-based) may differ from EBS metric |
| Accounts Payable | Payables Cloud | Direct mapping; some features reorganised | Verify that supplier portal access is included or separately subscribed |
| Accounts Receivable | Receivables Cloud | Direct mapping for core features | Advanced collections may be a separate cloud module |
| Purchasing | Procurement Cloud (multiple services) | Maps to Procurement Cloud, Self-Service Procurement, Sourcing, Supplier Qualification — potentially 4+ separate cloud services | One EBS module becomes multiple cloud subscriptions; significant cost increase if all are required |
| Order Management | Order Management Cloud | Core mapping exists; configurator may be separate | Product configurator may require additional cloud subscription |
| Core HR | HCM Cloud (suite of modules) | EBS HR maps to Core HR, but Recruiting, Talent Management, Learning, Workforce Compensation are all separate | EBS HR users need multiple HCM subscriptions; cost multiplier of 2–4× for equivalent scope |
| Payroll | Cloud Payroll | Functional mapping varies by country | Country-specific payroll localisation may require additional configuration or third-party add-ons |
| Fixed Assets | Assets Cloud | Direct mapping | Included in Financials Cloud subscription for most editions |
| Projects | Project Management Cloud / Project Financials Cloud | EBS Projects may map to 2 separate cloud services | Project Management and Project Financials are separately subscribed in some cloud editions |
| Manufacturing | Manufacturing Cloud / Supply Chain Cloud | Significant reorganisation; some EBS manufacturing features are in different cloud modules | Requires careful mapping; MRP, shop floor, quality may be separately subscribed |
The most expensive mapping surprise is in HCM and Procurement. In EBS, a single HR licence covers core HR, self-service, and basic talent functions. In Fusion Cloud, these are separate subscription modules — Core HR, Recruiting, Onboarding, Talent Management, Learning, Workforce Compensation, and more. An organisation paying $800K/year in EBS HR support can face a Fusion HCM Cloud subscription of $2M–$4M/year for equivalent functional coverage. Similarly, EBS Purchasing (one module) maps to 3–4 Procurement Cloud services. Always build a detailed module-to-cloud mapping with pricing before committing to the cloud deal.
Our field-tested strategies help enterprises navigate Oracle’s pricing models, avoid common traps, and negotiate from a position of strength.
Read Negotiation Strategies →| Double-Licensing Scenario | Cost Impact | How It Occurs | Avoidance Strategy |
|---|---|---|---|
| Full module overlap | $500K–$3M+ per year | EBS Financials and Cloud Financials running simultaneously for all users during extended dual-run | Plan swift cutover per module; negotiate support shelving for EBS modules as Cloud equivalents go live |
| HCM parallel run | $300K–$2M+ per year | EBS HR and Cloud HCM running concurrently across the full employee base; high user counts amplify cost | Migrate HR in shortest feasible window; use parallel run only for payroll validation, not ongoing operations |
| Procurement pilot overlap | $100K–$500K per year | EBS Purchasing live for most users while Cloud Procurement piloted with subset; both fully licensed | Limit pilot scope; negotiate reduced cloud subscription for pilot period; expand only at EBS cutover |
| Extended support retention | $500K–$2M+ per year | EBS support maintained “just in case” after Cloud go-live; fear of cutting over fully | Set firm support termination dates tied to Cloud stability milestones (e.g., 90 days post go-live) |
| Technology stack persistence | $200K–$1M+ per year | Oracle Database and WebLogic support continues for EBS infrastructure after all EBS modules decommissioned | Terminate technology stack support immediately when last EBS module is decommissioned; do not retain “for reporting” |
| Strategy | What It Means | Cost Impact | When to Use |
|---|---|---|---|
| Continue full Oracle support | Pay 22% annual support on all EBS licences throughout migration | Highest — full support continues until explicit termination | When migration timeline is uncertain; when active Oracle patches are needed; when regulatory requirements demand vendor support |
| Third-party support | Move EBS support to Rimini Street or similar provider at 50–60% savings | 50–60% annual savings on EBS support | When committed to migration but timeline is 18+ months; when no new Oracle patches needed; when maximising savings during transition |
| Phased support termination | Drop support module-by-module as each EBS module’s Cloud equivalent goes live | Progressive savings — each terminated module reduces annual support | When migration is phased by module; when Oracle’s contract allows partial support termination (verify — Oracle often restricts this) |
| Support shelving | Oracle pauses EBS support billing for 6–12 months during active migration | 100% savings during shelving period — but temporary | Must be explicitly negotiated as part of cloud deal; Oracle uses this as an incentive to close cloud contracts |
| Full termination | Cancel all EBS support immediately; run system “as is” until decommission | Maximum savings — but maximum risk | Only when confident in short migration timeline (<6 months); when EBS is stable and well-documented; when third-party support is available as fallback |
If you terminate Oracle support and later need to reinstate it (e.g., migration delays force you back to EBS), Oracle charges a reinstatement penalty — typically all back-dated support fees for the gap period (150% of what you would have paid) plus a 20% premium. On a $2M/year support estate, a 12-month gap followed by reinstatement costs $3M+ in penalties alone. This penalty is Oracle’s primary deterrent against support termination, and it makes the decision effectively irreversible. Factor this into any support termination strategy — and negotiate reinstatement protections if possible.
| Leverage Point | How It Works | Potential Value | Oracle’s Counter-Move |
|---|---|---|---|
| Competitive alternatives | Evaluate SAP S/4HANA, Workday, or Microsoft Dynamics as genuine alternatives; conduct RFP or proof-of-concept | 20–40% deeper discounts on Fusion Cloud when Oracle faces real competitive threat | Oracle will accelerate deal timeline and apply FUD about competitor migration costs |
| Oracle’s fiscal calendar | Time negotiations to Oracle’s quarter-end (August, November, February) or fiscal year-end (May 31) | 10–25% additional discount as Oracle sales reps push to meet targets | Oracle will push artificial urgency and “expiring” discounts |
| Existing EBS investment | Quantify total historical EBS licence + support spend; demand proportional credit against cloud subscription | $500K–$5M+ in transition credits depending on EBS estate size | Oracle offers credits that diminish after Year 1; insist on multi-year credit application |
| Support termination threat | Signal willingness to move to third-party support instead of cloud; Oracle loses annual support revenue entirely | Forces Oracle to improve cloud pricing to retain the revenue relationship | Oracle will emphasise security risks and compliance concerns about third-party support |
| Phased commitment | Propose starting with 1–2 cloud modules (e.g., Financials only) rather than full suite commitment | Reduces initial commitment risk; creates future negotiation opportunities for additional modules | Oracle prefers full suite deals; will offer lower per-module pricing for full commitment |
| Annual escalation caps | Negotiate 0–3% annual escalation caps vs Oracle’s standard 3–7% increases | $500K–$3M+ in avoided cost escalation over a 5-year contract | Oracle embeds escalation in “standard” terms; requires explicit pushback to cap |
| Exit and reduction flexibility | Negotiate right to reduce subscription scope by 15–25% at each renewal without penalty | $300K–$2M+ if business requirements change and modules can be dropped | Oracle defaults to full commitment with no reduction rights; pushback is essential |
| Exit Phase | Key Actions | Licensing Consideration | Timeline |
|---|---|---|---|
| Pre-migration assessment | Complete inventory of all EBS licences, modules, user types, and technology stack. Reconcile entitlements vs actual usage. | Identify shelfware and over-licensing before migration — eliminate unnecessary support costs immediately | 12+ months before cloud contract signature |
| Cloud deal negotiation | Negotiate credits, shelving, delayed billing, escalation caps, and exit provisions before signing cloud contract | Every concession must be in writing in the cloud ordering document — verbal promises have no contractual value | 6–12 months before planned go-live |
| Phased module migration | Migrate modules in planned waves; terminate EBS support for each module as its Cloud equivalent stabilises | Align EBS support renewal dates with Cloud go-live milestones to minimise overlap | Throughout implementation (12–24 months typically) |
| Technology stack decommission | Terminate Oracle Database, WebLogic, and middleware support when last EBS module is decommissioned | Technology stack support is often the largest overlooked cost — can exceed application support costs | Immediately after last EBS module cutover |
| Final support termination | Submit formal notice to terminate all remaining EBS support; retain perpetual licence documentation for records | Perpetual licences remain your property but have no practical value without support; retain documentation for audit defence | 90 days after Cloud stabilisation (per contractual notice requirements) |
| Audit Finding | How It Occurs | Typical Cost Impact | Prevention Strategy |
|---|---|---|---|
| Non-production EBS environments still active | Development, test, and training EBS environments remain running after production migrates to Cloud; still require licensing | $200K–$1M+ | Decommission all non-production EBS environments within 90 days of production cutover |
| Database options enabled on EBS servers | DBAs leave Diagnostics Pack, Tuning Pack, or Partitioning enabled on EBS database servers; options are detected during audit even if EBS applications are decommissioned | $300K–$2M+ | Run DBA_FEATURE_USAGE_STATISTICS before decommission; disable all options; document clean state |
| Oracle triggers audit during transition | Oracle initiates an LMS audit during the dual-run period — when compliance gaps are most likely due to changing configurations and parallel systems | $500K–$5M+ | Conduct internal compliance review before migration; resolve all gaps before Oracle can discover them |
| Customised technology triggers full-use licensing | EBS Application Technology licences (restricted-use DB/WebLogic) upgraded to full-use through customisation, third-party integrations, or non-EBS workloads on same servers | $500K–$3M+ | Verify that no non-EBS workloads run on EBS technology stack servers; isolate EBS infrastructure |
| Cloud subscription scope mismatch | Users accessing Cloud functionality beyond subscribed modules; metric mismatches between EBS named user and Cloud employee-based subscriptions | $200K–$1M+ | Validate Cloud subscription scope against actual usage within 90 days of go-live; true-up immediately |
Complete a full inventory of all EBS application licences, module entitlements, user counts by type, technology stack licences (Oracle DB, WebLogic, options), and support costs. Reconcile entitlements against actual usage. Identify shelfware and compliance gaps before Oracle does.
Map every EBS module in use to its Fusion Cloud equivalent. Identify modules that split into multiple cloud services (especially HR and Procurement). Price each cloud service independently. Calculate total Cloud subscription cost for equivalent EBS functional coverage.
Calculate 5-year and 10-year total cost of ownership for: (a) staying on EBS with current support, (b) staying on EBS with third-party support, (c) migrating to Fusion Cloud, (d) migrating to non-Oracle ERP. Include dual-run costs, implementation fees, and annual escalation in all scenarios.
Define maximum acceptable dual-run period. Budget for overlapping EBS support + Cloud subscription costs. Negotiate support shelving and delayed Cloud billing start. Build 6-month contingency buffer for implementation delays.
Negotiate credits, shelving, delayed billing, escalation caps (0–3%), exit provisions, and reduction flexibility before signing. Every concession must be in writing in the cloud ordering document. Verbal promises from Oracle sales have no contractual value.
Conduct internal compliance review before migration begins. Resolve all EBS licensing gaps proactively. Disable database options on EBS servers. Document everything — Oracle frequently audits during transition periods when compliance exposure is highest.
Our comprehensive EBS licensing guide covers all five licensing models, user types, audit triggers, and optimisation strategies for enterprises running Oracle E-Business Suite.
Read the EBS Licensing Guide →No. EBS perpetual licences and Oracle Fusion Cloud subscriptions are entirely separate licensing models. There is no direct conversion mechanism. When you migrate to Fusion Cloud, you purchase new subscription contracts. Your EBS perpetual licences remain owned but cannot be applied as credit toward cloud subscriptions automatically. Oracle may offer commercially negotiated migration credits, but these are incentives — not entitlements.
Most organisations run EBS and Fusion Cloud simultaneously for 12–24 months during migration, although complex multi-country deployments can extend to 36+ months. The dual-run period creates $1M–$5M+ in overlapping costs that most organisations underestimate by 40–60%. Phased migration, support shelving, and delayed cloud billing are the primary mitigation strategies.
No. Fusion Cloud modules are reorganised with different naming, boundaries, and scope. The most expensive surprises are in HCM (EBS HR becomes 5–7 separate cloud modules at 2–4× the cost) and Procurement (EBS Purchasing maps to 3–4 cloud services). Complete a detailed functional mapping with independent pricing before negotiating the cloud deal.
Oracle charges a reinstatement penalty — typically all back-dated support fees for the gap period (150% of what you would have paid) plus a 20% premium. On a $2M/year support estate, a 12-month gap costs $3M+ in penalties alone. This makes support termination effectively irreversible. Factor this into your strategy and negotiate reinstatement protections if possible.
Oracle offers several credit programmes including support fee credits (50–80% of Year 1 support applied as cloud discount), transition credits (10–20% of historical EBS investment), and OCI consumption credits. These are not standardised and vary based on deal size, timing, and competitive pressure. The critical issue is that credits typically apply to Year 1 only while the multi-year cloud subscription commitment far exceeds what you would have paid for EBS support.
Third-party support (Rimini Street, Spinnaker) can save 50–60% on EBS support during the transition period. This is most effective when migration will take 18+ months and you do not need new Oracle patches. It also creates negotiation leverage — signalling willingness to move to third-party support forces Oracle to improve cloud pricing to retain the revenue relationship. See our Breaking Free from Oracle Support guide.
The five most common audit findings are: (1) non-production EBS environments left active after production migrates, (2) database options (Diagnostics Pack, Tuning Pack) left enabled on EBS servers, (3) Oracle triggering an LMS audit during the dual-run period, (4) restricted-use technology licences (DB/WebLogic) being used for non-EBS workloads, and (5) cloud subscription scope mismatches. Conduct an internal compliance review before migration begins and document everything.
Redress Compliance provides independent Oracle licensing advisory for enterprises managing EBS-to-Cloud transitions. We map existing licence entitlements, validate module-to-cloud mapping, negotiate migration credits and cloud subscription pricing, manage dual-run cost exposure, plan clean licensing exits, and provide audit defence during the transition period. All engagements are fixed-fee and 100% vendor-independent.
Redress Compliance provides independent Oracle licensing advisory — fixed-fee, no vendor affiliations. Our specialists help enterprises manage EBS-to-Cloud transitions, protect perpetual licence assets, and avoid dual-run cost traps.