EBS to Fusion Migration Licensing

Introduction: The Complexity of EBS to Fusion Migration Licensing

Oracle E-Business Suite (EBS) to Fusion Cloud migrations represent one of the most complex enterprise software transitions in the modern technology landscape. While the business case for cloud adoption is compelling—scalability, reduced on-premises infrastructure, continuous updates, and modern capabilities—the licensing implications are often overlooked or drastically underestimated during project planning. Organizations frequently discover that their total cost of ownership during the migration period is 150–200% higher than baseline, driven almost entirely by licensing decisions made in the first 90 days of the project.

This comprehensive guide provides strategic guidance on navigating the licensing landscape of an EBS-to-Fusion migration. We cover dual-run cost traps, subscription model mechanics, module mapping, negotiation strategies timed to Oracle's fiscal calendar, compliance risks, and how independent advisory can protect your organization from costly mistakes.

Why Migration Licensing Is Fundamentally Complex

The Perpetual License vs. Subscription Model Problem

The root of migration complexity lies in a simple truth: Oracle EBS perpetual licenses and Oracle Fusion Cloud subscriptions are two fundamentally different pricing models. EBS operates on a perpetual license + annual support model. Once you purchase a perpetual license, you own it indefinitely. You pay an annual support fee (currently 22% of the net license value, increasing 8% per year) to maintain coverage. Fusion Cloud, by contrast, is purely subscription-based. You pay per user per month, with no ownership. There is no direct license conversion mechanism.

This creates an immediate problem: organizations cannot simply "convert" their EBS perpetual license investment into Fusion Cloud subscriptions at a favorable rate. Instead, they face a hard choice: keep paying support on their EBS licenses while buying Fusion Cloud subscriptions (the dual-run scenario), or abandon their perpetual licenses and migrate entirely to cloud subscriptions (which may require renegotiating support and license termination terms).

No Direct Conversion, No Trade-In Credits

Oracle has no formal trade-in or credit program for perpetual EBS licenses toward Fusion Cloud subscriptions. Some organizations negotiate informal credits as part of a broader cloud transformation contract, but this requires skilled negotiation and is never guaranteed. The absence of a formal conversion mechanism means every organization entering an EBS-to-Fusion migration faces the same challenge: they must plan for overlapping costs during the transition period.

The Dual-Run Cost Trap

During migration, organizations run EBS and Fusion Cloud simultaneously. This parallel operation—necessary for testing, cutover validation, and data reconciliation—means you are paying for both systems at the same time. EBS support continues at 22% annually (with the 8% uplift), while Fusion Cloud subscription costs accumulate on top. For a typical large enterprise, this overlap period can run 18–36 months, resulting in combined costs that can exceed 200% of your pre-migration support baseline. Many organizations are shocked to discover that the licensing bill during migration actually exceeds the combined annual spend on both systems separately.

The Dual-Run Cost Trap: Anatomy and Mitigation

How Dual-Run Costs Accumulate

Let us walk through a realistic scenario. Assume an organization has $5 million in net perpetual EBS licenses. Annual EBS support is currently 22% of net license value, or $1.1 million. This organization enters migration to Fusion Cloud. For the first 18 months of migration (typical), they run both systems:

EBS support continues: $1.1 million per year (with 8% annual increases in years 2 and 3)
Fusion Cloud subscriptions begin: assume 500 named users at $625/user/month (list price) = $3.75 million per year
Combined annual cost during dual-run: approximately $4.85 million per year
Total dual-run cost over 18 months: approximately $7.3 million

Compare this to the pre-migration baseline: $1.1 million per year for EBS only. In the year after migration (when EBS is cut off), annual costs drop to $3.75 million for Fusion Cloud. However, the 18-month overlap period has cost the organization an additional $6.2 million above the pre-migration baseline—a 560% increase in licensing spend during transition.

Shortening Dual-Run: Phased Cutover vs. Big Bang

The primary lever for managing dual-run costs is timeline compression. A big-bang cutover (migrate all modules on a single date) minimizes dual-run duration but maximizes risk and implementation costs. A phased cutover (migrate modules sequentially, with EBS support continuing only for active modules) extends the timeline but allows for more controlled cutoff and potential cost reductions.

Many organizations pursuing a phased approach attempt to negotiate module-by-module EBS support termination. For example, if you migrate Finance and Procurement in month 12 and then HR in month 18, you could theoretically terminate support for those modules as they are decommissioned. However, Oracle often requires continued support for full installations even as modules are retired, limiting cost savings. Negotiating module-level support termination is critical—it can reduce dual-run costs by 30–50%—but it must be explicitly agreed in writing during the initial contract negotiation.

Shelving Rights and Support Suspension

During migration, many organizations pursue shelving rights: a formal agreement with Oracle to suspend or reduce EBS support fees for a defined period (typically 12–24 months). Shelving is not automatic. It requires explicit negotiation, typically as part of the overall migration contract. Shelving can reduce dual-run support costs by 40–70%, depending on the arrangement. However, shelving periods are finite, and support fees resume at the end of the agreement—often at a higher rate due to the 8% annual uplift applied retroactively.

Negotiating shelving rights requires understanding Oracle's motivation. Oracle is primarily interested in your Fusion Cloud commitment, not in reducing EBS support revenue. Shelving is most attractive to Oracle when it is traded for a multi-year Fusion Cloud subscription commitment (3–5 years) and higher user counts. Combining a 5-year Fusion Cloud contract with shelving rights for the first 24 months of migration is a common middle ground that satisfies both parties.

EBS License Treatment During and After Migration

Shelving Rights: Strategic Suspension of Support Fees

Shelving rights allow you to formally suspend EBS support fees for a negotiated period, typically 12–24 months. During the shelving period, you retain the perpetual license and keep systems running, but Oracle does not charge annual support. This is particularly valuable for migration scenarios where parallel systems are running but the original EBS systems are in maintenance mode.

The mechanics of shelving are critical: shelving agreements must clearly define which products and modules are shelved, the start and end dates, and what happens when shelving expires. Most shelving agreements require you to either re-enable support or terminate the licenses. Some organizations negotiate a post-shelving support resumption at a reduced rate (e.g., 15% instead of 22%), but this is uncommon and requires specific leverage.

CSI (Customer Support Identifier) and License Continuity

Every Oracle license is tied to a Customer Support Identifier (CSI), which tracks support status, contract terms, and fee obligations. During migration, your CSI status changes as modules are decommissioned or migrated. It is critical to understand how migration affects your CSI: if modules are dropped without proper termination, Oracle may continue charging support fees for systems that no longer exist in your environment. Conversely, if you terminate support prematurely, you lose license portability and face reinstatement penalties if you need to resume support later.

CSI management is often handled by procurement or IT operations teams with limited licensing expertise. We strongly recommend engaging independent licensing advisors to audit your CSI records before and after migration cutover events. Many organizations discover post-migration that they have been charged support for "phantom" systems that were decommissioned years earlier.

What Happens to Perpetual Licenses After Migration

After EBS is decommissioned, you face a choice: keep the perpetual licenses in your environment (or on contract for potential future use) or formally terminate them and remove them from your contract. Organizations often view perpetual licenses as "stranded assets" and want to terminate support to reduce costs. However, terminating perpetual licenses creates problems if your Fusion Cloud implementation fails or you need to revert to EBS for any reason.

Strategic best practice: after Fusion Cloud cutover, maintain perpetual EBS licenses in a shelved or reduced-support state for 12–24 months. This provides a fallback option at minimal cost ($0 support fees if shelved, 15–22% if in limited support) and protects against unexpected cutover complications. After 12–24 months of successful Fusion Cloud operation, formally terminate the perpetual licenses and remove them from your support contract.

Migration Cloud Contract (MCC) Terms

Oracle offers a Migration Cloud Contract (MCC) framework designed specifically for EBS-to-Fusion migrations. The MCC typically includes shelving rights for EBS, discounted Fusion Cloud subscription pricing in exchange for multi-year commitment, and defined support transition terms. However, the MCC is not a standard product—each agreement is custom-negotiated. Key MCC provisions to understand include:

Shelving duration and which modules/products are covered
Fusion Cloud pricing tiers (typically 30–50% discount off list if you commit to 3+ years)
Dual-run support caps (capping total annual costs to prevent runaway bills)
Module-level support termination (allowing selective support reduction as modules are retired)
Price protection (capping future year increases at 4–5% annually instead of Oracle's standard 8%)
Minimum user counts and expansion pricing for new users

Oracle Fusion Cloud Subscription Model: Pricing, Metrics, and Contracts

Named User and Hosted Employee Metrics

Fusion Cloud subscriptions are priced on two primary user metrics: Named User (Hosted Named User, or HNU) and Hosted Employee. Named User licenses are tied to specific individuals and allow concurrent access. Hosted Employee licenses are available to any employee in your organization but are counted as named individuals. The distinction matters for cost modeling: if you have 1,000 employees, you may license only 600 named users if you expect only 60% concurrent access, but if the subscription is sold as "Hosted Employee," you must license all 1,000 employees regardless of usage.

Oracle has been gradually shifting toward Hosted Employee metrics for Fusion Cloud, particularly for HCM (Human Capital Management) and SCM (Supply Chain Management) modules. This metric change increases the user count baseline, which directly increases subscription cost. During migration planning, clarify with Oracle which metric you are licensing under and confirm whether that metric can be adjusted based on actual business requirements.

Per-User-Per-Month Pricing and Module Structure

Oracle Fusion Cloud ERP modules are sold as separate subscription products, each with its own per-user-per-month (PUPM) pricing. The major modules include:

Oracle Financials Cloud: Covers GL, AP, AR, fixed assets, and accounting consolidation. List price approximately $625/user/month (varies by configuration).
Oracle HCM Cloud: Covers payroll, HR, talent management, and workforce planning. List price approximately $625/user/month.
Oracle SCM Cloud: Covers procurement, inventory, order management, and warehouse management. List price approximately $500/user/month.
Oracle Project Management Cloud: Covers project portfolio, project costing, and resource management. List price approximately $625/user/month.

List prices are heavily discounted in practice. Negotiated pricing typically ranges from 35–55% off list price for 3-year contracts, increasing to 45–60% off list for 5-year commitments. Multi-module implementations often receive bundled pricing discounts of an additional 10–15%.

Minimum User Counts and Annual Thresholds

Fusion Cloud subscriptions typically carry minimum user counts and annual minimum spend thresholds. For example, Oracle may require a minimum of 250 named users for any Fusion Cloud finance implementation, resulting in a minimum annual spend of approximately $1.875 million (250 users x $625/month x 12 months). If your actual user population is below the minimum, you still pay for the minimum number of licenses.

Minimum user counts are negotiable, particularly for smaller implementations or during the first 12 months of migration. We recommend negotiating minimum user counts that reflect your actual intended user base, with provisions for user count adjustments at annual reviews (adding or removing users without penalty).

Contract Terms, Price Protection, and Annual Increases

Fusion Cloud subscriptions are sold on 3, 4, or 5-year initial terms. Shorter terms (1–2 years) are available but carry a significant price premium (typically 25–35% higher per-user-per-month rate). The term length directly affects negotiated pricing: a 5-year commitment unlocks maximum discounts (45–60% off list), while a 3-year commitment typically yields 35–50% discounts.

Annual price increases during the initial contract term are negotiable. Oracle's standard policy allows for annual list price increases (which have historically been 3–5% per year but can spike higher in certain product categories). Negotiated contracts often include price caps—for example, "annual price increases will not exceed 4% or CPI + 2%, whichever is lower." Price caps are critical to budget predictability over a 5-year commitment.

Subscription Fees Do Not Compound Like Support Fees

A crucial distinction from EBS: Fusion Cloud subscription fees do not compound annually like EBS support fees (which increase 8% per year). You negotiate a price per user per month for the contract term, and that price remains fixed subject to the annual increase cap. This predictability is valuable for financial planning, but it also means your subscription costs will be substantially higher than your pre-migration EBS support costs. For many organizations, Fusion Cloud annual costs are 40–80% higher than EBS support costs they were paying immediately before migration, even after substantial negotiated discounts.

Module Mapping: EBS to Fusion Cloud Product Alignment

One-to-One Mapping Is Rare; Splits and Merges Are Common

One of the critical surprises in EBS-to-Fusion migration is that EBS modules do not map neatly to Fusion Cloud products. Some EBS modules split across multiple Fusion Cloud products. Others merge. Some EBS functionality has no Fusion Cloud equivalent and must be retired or replaced with third-party solutions.

Oracle Financials: EBS GL, AP, AR, and fixed assets map to Oracle Financials Cloud. This is relatively straightforward. However, Fusion Financials has a different underlying architecture, and accounting process flows may need to be redesigned.

Oracle HRMS: EBS HRMS (with its legacy payroll, benefits, and employee data structures) maps to Oracle HCM Cloud. However, HCM Cloud uses different data models, role-based access controls, and process flows. Legacy HRMS customizations rarely translate directly.

Oracle Supply Chain: EBS Supply Chain Management (Inventory, Order Entry, Purchasing, Receiving) maps to Fusion SCM Cloud. Order-to-Cash and Procure-to-Pay processes are rebuilt in Fusion, and custom workflows typically require re-implementation.

Oracle Projects: EBS Projects module maps to Fusion Project Management Cloud, but Fusion Project Management is a smaller, more narrowly scoped product than EBS Projects. Organizations with complex project accounting often find that Fusion Project Management does not meet their needs and must layer additional solutions on top.

EBS Modules with No Fusion Cloud Equivalent

Specific EBS modules have no direct Fusion Cloud counterpart. Oracle Manufacturing (Discrete Manufacturing, Process Manufacturing) is not available in Fusion Cloud as a discrete product. Organizations requiring manufacturing capabilities in the cloud must use third-party solutions or pursue a hybrid approach (Fusion Cloud for financials, third-party or legacy EBS for manufacturing).

Oracle Service and Maintenance (Field Service, Field Maintenance) has limited equivalents in Fusion Cloud. Oracle Field Service Cloud exists but is a narrow solution designed for specific use cases. Organizations with complex field service operations should evaluate third-party alternatives early in migration planning.

Oracle CRM (Sales, Service, Marketing) is not part of Fusion ERP. Oracle has a separate Fusion CRM product (which is less mature than Salesforce CRM), but it is not bundled with Fusion ERP and requires separate licensing and implementation.

Customization Challenges: Legacy Code Cannot Be Migrated

EBS customizations—forms, reports, workflows, data models—are built on Oracle Forms and Reports, PL/SQL, and database objects specific to the EBS schema. Fusion Cloud is built on a completely different technology stack: FSCM (Fusion Security Context Model), JavaScript, and REST APIs. Legacy EBS customizations cannot be migrated; they must be rebuilt as Fusion Cloud extensions using the Fusion extensibility framework.

This is one of the largest hidden costs in EBS-to-Fusion migration. Organizations typically discover during migration that their customization portfolio is 3–5x larger than they realized, and re-implementing all customizations in Fusion adds 30–50% to total implementation cost. Strategic approach: during migration planning, conduct a detailed customization inventory, classify each customization by business criticality, and make a deliberate choice: rebuild in Fusion (high cost, high capability), retire the customization (lowest cost, may require process change), or use third-party solutions to bridge gaps.

Negotiation Strategy: Timing, Leverage, and Contract Structure

Oracle's Fiscal Calendar: Maximizing Negotiating Leverage

Oracle's fiscal year ends on May 31. Oracle's fiscal Q4 (March–May) is the final quarter of each fiscal year. Sales teams face intense pressure to close contracts before May 31 to meet annual quotas and recognize revenue. This creates a predictable window of maximum negotiating leverage: March through May of any given year.

If you are planning an EBS-to-Fusion migration, plan your contract negotiations to occur during Oracle's Q4 (March–May). During this window, Oracle sales teams have maximum flexibility on pricing, terms, and incentives. If you negotiate outside this window (e.g., in June–August), you are negotiating in a low-pressure environment, and Oracle's opening position will be more aggressive.

Additionally, Oracle fiscal Q4 is when Oracle announces price increases for the following fiscal year (typically effective June 1). If you finalize a contract before May 31, you lock in the current fiscal year's pricing. If negotiations stretch into June or later, you will be quoted on the new fiscal year's pricing, which includes increases of 3–8% across product lines.

Migration Commitment as Negotiating Leverage

Your migration commitment is valuable to Oracle. Oracle measures success partly by the number of organizations migrating from EBS to Fusion. A credible commitment to migrate 500+ named users to Fusion Cloud creates negotiating leverage. However, you must convince Oracle that you are genuinely committed, not simply exploring options.

Effective leverage signals include:

A published migration project plan with defined cutover dates (18–36 months from contract signing)
Executive sponsorship and budget approval for Fusion implementation
Named system integrators already engaged (SAP, Deloitte, Accenture, etc.)
A demonstration of current EBS environment size (user count, modules, contract value)
Stated willingness to expand to cloud-native products (e.g., Fusion HCM, Fusion Procurement, future products) beyond EBS parity

Conversely, Oracle will discount your leverage if you appear to be exploring options without firm commitment. Phrases like "we are evaluating cloud alternatives" or "we have not finalized our technology choice" signal to Oracle that your commitment is uncertain, and they will price defensively.

Multi-Year Commitments Unlock 30–50% Discounts

Fusion Cloud pricing is heavily volume and term-sensitive. List price (often cited as $625–$750 per user per month depending on module) rarely reflects actual negotiated rates. Organizations with credible multi-year commitments (3–5 years) typically achieve 35–55% discounts off list price. Five-year commitments can unlock 45–60% discounts, particularly for large implementations (500+ users) with multiple modules.

Example: a 500-user Fusion Financials Cloud implementation at list price ($625/user/month) would cost $3.75 million per year. With a 50% discount (achievable on a 5-year commitment), the cost drops to $1.875 million per year, or $9.375 million for the 5-year term. The discount difference is substantial—$9.375 million saved over the 5-year contract term—which justifies engaging skilled negotiators.

Extended Dual-Run Pricing Protections

Critical negotiation point: secure explicit pricing protection for the dual-run period. Ideally, negotiate a "dual-run cap" on total annual costs. For example: "During the migration period (months 1–24), Oracle support and Fusion Cloud subscription costs combined will not exceed $X annually." This cap prevents runaway bills as Fusion Cloud user counts expand and EBS support fees increase.

Alternative approach: negotiate a "transition discount" on Fusion Cloud pricing specifically for the first 12–24 months of the migration period. For example, "Fusion Cloud pricing will be discounted 15% below the standard negotiated rate during months 1–24 of migration, reverting to standard rate thereafter." This directly addresses the dual-run cost reality and reduces peak costs.

Price Caps and Future-Year Increase Limitations

In a 5-year Fusion Cloud subscription, you will experience annual price increases for at least 4 years (if you lock price in year 1, you still face increases in years 2–5). Standard Oracle increase policy allows increases up to the list price increase percentage (historically 3–8% per year). However, negotiated contracts can include price caps.

Recommended approach: negotiate annual price increases capped at "lesser of 4% or CPI + 2%." This limits exposure to unexpected spikes and ties increases to economic inflation. For example, if annual CPI is 2%, your increase is capped at 4%. If CPI is 4%, your increase is capped at 6%.

Never Sign Without Independent Review

Oracle licensing contracts are complex, heavily templated, and often contain unfavorable default terms. Critical sections to review include:

Metrics definition: Confirm whether you are licensed on Named User, Hosted Employee, or another metric. Ensure the metric matches your business model.
User count minimums: Ensure minimum user counts reflect your actual expected usage, not Oracle's suggested minimums.
Annual increase methodology: Confirm price caps and tie increases to CPI or a fixed percentage, not to list price increases.
Shelving terms (if applicable): Ensure shelving rights are explicit, with defined start/end dates and clear procedures for support resumption.
Termination rights: Understand the cost of contract termination if your migration is delayed or derailed.
Module scope: Ensure all modules you expect to use are listed explicitly. Addition of unlisted modules later will trigger new negotiation and higher pricing.

Engaging independent licensing advisors (not affiliated with Oracle, SAP, or system integrators) for contract review typically costs $20,000–$50,000 but often saves $500,000–$2 million in negotiated pricing and prevented terms miscalculations. This is one of the highest ROI investments in migration planning.

Licensing Compliance Risks During Migration

Test and Parallel Environments Expand License Scope

During EBS-to-Fusion migration, you build parallel testing environments: user acceptance testing (UAT), integration testing, training environments, and data validation systems. Each environment requires EBS licensing if it contains production or production-like data. Many organizations underestimate the licensing implications of parallel environments and discover mid-migration that they have license shortfalls.

Example: you have 500 named users licensed on EBS. During migration, you create five parallel environments: Production (where current business operations continue), UAT (500 users), Integration Test (250 users), Training (300 users), and Data Validation (100 users). This expands your licensed user count from 500 to 1,650 users, a 230% increase. If you fail to license these additional users explicitly, you face potential audit findings and true-up charges.

Recommendation: during migration planning, model all parallel environments and compute the expanded user count. Negotiate additional EBS licenses explicitly, or seek shelving arrangements that allow test environments to run unlicensed for defined periods. Similarly, plan Fusion Cloud test and UAT environments upfront and ensure you have sufficient user licenses allocated to testing (not just production).

Oracle LMS Audit Frequency During Migration

Oracle Legal and Licensing Services (LMS) audits target organizations in transition states. A migration environment with parallel systems, expanded test infrastructure, and changing deployment models is a high-risk audit target. Oracle views migrations as opportunities to discover license shortfalls and extract true-up fees.

Best practice: conduct your own internal compliance audit before migration begins. Catalog all EBS installations, confirm license counts and product entitlements, and identify any license gaps. Address gaps proactively through shelving, license purchases, or environment rationalization before Oracle initiates an audit.

Sandbox and Test Environment Licensing

Fusion Cloud sandbox and test environments have separate licensing considerations. If you are using Oracle's managed cloud sandboxes for configuration and testing, those sandboxes typically do not require separate named user licenses. However, if you create customer-managed Fusion Cloud test environments or if you populate sandboxes with production data, licensing implications vary by configuration. Clarify sandbox licensing with Oracle upfront to avoid unexpected charges or audit findings.

Total Cost of Migration: Hidden Costs and ROI Timeline

Subscription Costs 40–80% Higher Than Pre-Migration Support

The starting assumption: Fusion Cloud subscription costs will be 40–80% higher than EBS support costs paid immediately before migration. This is structural, not negotiable away. Why? EBS support is a maintenance-only proposition: you pay 22% annually to keep a system running with minimal enhancements. Fusion Cloud is a feature-rich, continuously updated product with infrastructure, multi-tenancy, security, and regular feature releases included in the subscription. The value proposition is higher, and the cost reflects that.

Example: pre-migration EBS support costs are $1.2 million annually. Post-migration Fusion Cloud annual costs (after 50% negotiated discount off list price) are $2.0–$2.1 million annually. This 67–75% increase is typical. However, the Fusion Cloud subscription includes cloud infrastructure, platform updates, and new feature releases that were not available in EBS.

Implementation Costs: 200–400% of First-Year Subscription Value

Implementation costs for EBS-to-Fusion migrations are substantial. A typical implementation cost breakdown includes:

System integration services: $3–7 million for large implementations (200+ consulting days)
Data migration and ETL development: $500,000–$2 million
Customization and extension development: $1–3 million (if you have legacy customizations to rebuild)
Integration to legacy systems: $300,000–$1.5 million (interfaces to non-Oracle systems)
Training and change management: $400,000–$1.2 million
Infrastructure and hosting (if on-premises deployment): $500,000–$2 million

Total implementation cost for a large migration typically ranges from $6–15 million, with an average around $8–10 million. For a $2 million annual Fusion Cloud subscription, this represents 4–7x the annual subscription cost, consistent with the 200–400% rule of thumb.

Re-Implementation of Customizations: The Hidden 30–50% Cost Driver

One of the largest surprises in EBS-to-Fusion migration is the scope of customization re-implementation. Many organizations conduct their initial assessment and estimate that customizations represent 5–10% of the total implementation cost. However, after detailed design, the actual customization scope often expands to 30–50% of total implementation costs.

This occurs because organizations discover during design that their EBS customizations are more extensive than initially recognized, and rebuilding them in Fusion requires architectural rework. Additionally, Fusion Cloud's extensibility model (the Force.com platform for extensions) requires skilled developers, and hiring or contracting experienced Fusion Cloud extension developers is expensive.

ROI Timeline: 5–7 Years to Break Even

Given the cost structure, a typical EBS-to-Fusion migration does not achieve positive ROI (cost recovery) for 5–7 years post-cutover. This includes:

Years 1–3: Negative ROI. Fusion Cloud annual costs ($2 million in our example) exceed EBS support costs ($1.2 million) by $800,000 per year. Total implementation cost ($10 million) is not yet recovered.
Years 4–7: Gradual breakeven. As the system matures and the organization realizes benefits (reduced IT infrastructure costs, faster reporting, reduced FTE requirements for system administration), total cost of ownership improves. By year 6–7, cumulative savings often exceed cumulative added costs.
Year 8+: Positive ROI. Post-breakeven, Fusion Cloud becomes cheaper than maintaining EBS (which would require continued support at 22% annually with 8% annual increases, plus significant IT infrastructure costs).

This 5–7 year ROI timeline assumes a well-executed migration with contained implementation costs and realistic benefit realization. Poorly executed migrations (delays, cost overruns, limited benefits realization) can extend the ROI timeline to 8–10 years, at which point the business case may no longer be compelling.

Alternative Strategies: Staying on EBS or Hybrid Approaches

Staying on EBS: Cost of Extended Support Beyond December 2031

Oracle premier support for EBS 12.2 ends December 31, 2031. Organizations not migrating to Fusion by that date will face a choice: migrate to Fusion, stay on EBS with extended support, or pursue third-party support. Extended support for EBS (available through Oracle Extended Support, or third-party vendors) is significantly more expensive than premier support.

Cost comparison: EBS 12.2 current support at 22% of license value will increase to 30–35% or higher under extended support (if available from Oracle) or third-party support. Additionally, extended support typically includes reduced SLAs (response times) and limited access to Oracle resources. For a $5 million license base, the difference between 22% ($1.1 million/year) and 35% ($1.75 million/year) is $650,000 annually, or $6.5 million over a 10-year extended support period.

Third-Party Support: 50% Cost Reduction, Full Feature Limitation

Third-party support providers (like Rimini Street, Viasat, and others) offer EBS support at 40–50% of Oracle's rates, but with important limitations: no new features or enhancements, no access to Oracle's latest patches, and limited integration with Oracle's ecosystem of cloud products.

From a licensing perspective, switching to third-party support is straightforward: you terminate Oracle support, negotiate a support termination fee (typically 0–15% of annual support cost if you are not in violation), and engage the third-party provider. The licensing arrangement remains unchanged—you still own the perpetual licenses, just with different support vendor.

Strategic approach: third-party support is cost-effective for organizations planning to stay on EBS for another 5–10 years while evaluating cloud alternatives. If you do eventually migrate to Fusion, third-party support keeps your annual EBS cost manageable (reducing the cost delta between EBS and Fusion), and you can maintain shelved licenses at low cost during the migration period.

Hybrid Approach: Migrate Selectively, Retain EBS for Stable Modules

Some organizations pursue a hybrid strategy: migrate selected modules to Fusion Cloud (e.g., Finance, HCM, Procurement) while retaining EBS for stable, mature modules with few business changes (e.g., Projects, Manufacturing, if applicable). This approach reduces migration scope and cost while achieving many cloud benefits.

Licensing implications of a hybrid approach:

Retain EBS licenses and support for modules you are keeping, potentially at reduced cost if you negotiate module-level support (available for some products).
Purchase Fusion Cloud licenses for modules you are migrating.
Maintain integrations between EBS and Fusion, which adds ongoing integration management cost.
Accept long-term maintenance burden of running two systems indefinitely (not a transitional state).

Hybrid approaches are attractive on paper but often result in higher long-term costs due to integration complexity and the burden of maintaining two systems. However, for organizations with specialized modules (Manufacturing, Projects) that have no Fusion equivalent, a hybrid approach may be the most realistic option.

How Redress Compliance Protects Your Organization

Independent License Position Assessment

Before entering migration negotiations with Oracle, understanding your current license position is critical. Redress conducts detailed assessments of EBS license entitlements, support status, and potential compliance gaps. We identify legacy licenses that may have been forgotten, overlapping licenses that can be consolidated, and gaps that need to be addressed proactively.

This assessment typically uncovers 10–20% variance between what an organization believes it owns and what it actually owns. Addressing these variances before migration negotiation prevents Oracle from discovering gaps during contract discussions (which would undermine your negotiating position).

Shelving Rights Negotiation

Negotiating shelving rights requires detailed knowledge of what Oracle will accept and how to structure the arrangement for mutual benefit. We provide detailed shelving term recommendations based on your migration timeline and dual-run cost modeling, and we lead negotiations with Oracle to secure favorable shelving arrangements.

Dual-Run Cost Modeling

We build detailed financial models of your migration scenario, showing month-by-month costs during the dual-run period, identifying peak cost months, and modeling the impact of different scenarios (phased cutover vs. big-bang, shelving arrangements, module-by-module support termination). These models inform your business case and guide contract negotiations.

Audit Defense During Migration

During migration, you are an audit risk. We work with your team to ensure your parallel environments and test infrastructure are licensed appropriately, document your licensing position, and prepare defensively for Oracle audit activity. If Oracle initiates an audit, we represent your interests and negotiate audit settlements.

Contract Review and Red-Lining

Our licensing attorneys review all migration contracts, Oracle's terms, and proposed terms. We identify unfavorable provisions, propose amendments, and guide negotiations toward terms that protect your interests. This is particularly important for metrics definition, user count minimums, price cap mechanisms, and termination rights.

Conclusion: Strategic Guidance for Migration Success

Oracle EBS to Fusion Cloud migration is one of the most complex enterprise software transitions you will undertake. The licensing implications are substantial, often representing the difference between a successful business case and a failed migration financially. Key takeaways:

Dual-run costs are real and substantial. Expect 150–200% cost peaks during the overlap period. Budget and plan for this.
Timing your negotiation to Oracle's Q4 (March–May) maximizes your leverage. Plan contract discussions accordingly.
Multi-year commitments unlock substantial discounts. A 5-year commitment at 50% off list price is a realistic target for large implementations.
Shelving rights reduce dual-run costs significantly. Negotiate shelving explicitly as part of your overall migration contract.
Perpetual EBS licenses have residual value. Plan for post-migration retention or phased termination, not immediate cutoff.
Implementation costs dwarf subscription costs. The 200–400% rule of thumb is typical. Budget accordingly and phase implementation to manage cash flow.
Customization scope expands during migration. Conduct a detailed customization inventory early and make strategic choices about rebuild vs. retire vs. replace.
ROI takes 5–7 years. Ensure executive leadership understands the long-term financial commitment before green-lighting the project.
Independent advisory is high ROI. Engaging experienced licensing advisors early in planning typically saves multiples of the advisory cost.

The Oracle EBS to Fusion Cloud transition is a strategic undertaking with significant financial, operational, and organizational implications. Approach it with rigorous planning, skilled negotiation, and independent advisory to maximize your return on investment and minimize unpleasant surprises.

Oracle EBS to Fusion Cloud Migration Licensing Guide