Oracle E-Business Suite Premier Support runs to December 2034 under the 2023 extension, removing the 2030 end-of-support pressure that customers feared. Fusion migration is now a commercial decision rather than a forced deadline. The economics still favour migration for most enterprise EBS customers because Oracle bundles 25 to 40 percent conversion credit into Fusion deals signed before EBS support events. The migration cost ranges from $200K for a 500-user mid-market conversion to $20M+ for global enterprise. This guide quantifies the cost, the conversion credit treatment, and the operational mistakes that destroy migration value.
The EBS support timeline through 2034
Oracle's EBS support timeline received two extensions between 2019 and 2023. The current schedule maintains Premier Support on EBS 12.2 through December 2033 and Sustaining Support indefinitely. Premier Support includes regulatory updates (tax tables, statutory reporting), new operating system certifications, security patches, and bug fixes. Sustaining Support covers existing patches and known fixes but adds no new development.
The implication for migration timing is significant. Customers who feared a 2030 forced migration now have until 2033 to plan and execute a Fusion transition under Oracle support, and beyond 2033 under third-party support providers like Rimini Street, Spinnaker, Origina, and Support Revolution. The commercial migration trigger is no longer end-of-support but Oracle's conversion credit programme, which incentivises migrations during specific commercial windows.
Fusion migration cost model
Fusion migration cost has three components: implementation services (60 to 70 percent of total), Fusion subscription Year 1 (15 to 25 percent), and the EBS sunset cost during parallel run (10 to 20 percent). Implementation cost depends on the migration pattern, the module scope, the country count for HCM and Payroll, and the data complexity of the existing EBS estate.
| Customer profile | Module scope | Implementation cost | Year 1 Fusion subscription | Total Year 1 migration cost |
|---|---|---|---|---|
| Mid-market (500 to 1,500 users) | Financials, Procurement | $500K to $1.5M | $300K to $900K | $1.0M to $2.8M |
| Mid-enterprise (1,500 to 5,000 users) | ERP plus HCM Core | $2.0M to $5.5M | $1.2M to $3.5M | $3.5M to $10.0M |
| Enterprise (5,000 to 15,000 users) | ERP, HCM, SCM | $6.0M to $14.0M | $3.0M to $8.5M | $10.0M to $25.0M |
| Global enterprise (15,000+ users) | ERP, HCM, SCM, CX, multi-country payroll | $15.0M to $40.0M | $7.0M to $20.0M | $25.0M to $65.0M |
The numbers above assume a 12 to 24 month implementation. Compressed timelines below 12 months require premium implementation rates of 30 to 50 percent above the base, and extended timelines beyond 24 months typically experience 15 to 25 percent budget overruns. The realistic median for enterprise migrations in 2026 is 18 months from contract to go-live.
Conversion credit treatment
Oracle's conversion credit programme converts existing EBS perpetual licence value into Fusion subscription credit. The conversion formula is not published but the practical outcome for enterprise customers is roughly 25 to 40 percent credit on Year 1 Fusion subscription, with declining credit through Year 3 and no credit from Year 4 onward.
The credit calculation considers the customer's existing EBS net licence value (purchase price net of discount, not list price), the active support payment history (continuous EBS support is required for conversion credit eligibility), and the Fusion module mapping (EBS Financials credit applies to Fusion Financials, EBS HCM credit applies to Fusion HCM, and so on). A customer with $8M net EBS licence value and continuous support produces roughly $2M to $3.2M in conversion credit toward Year 1 Fusion subscription.
The conversion credit timing trap: conversion credit is highest when negotiated with the original Fusion contract signature and lowest when negotiated after the fact. Customers who sign a Fusion contract first and then attempt to apply conversion credit at the next renewal typically receive 30 to 50 percent of the credit they would have received pre-signature. Conversion credit is a signature-event lever, not an ongoing entitlement.
The four migration patterns
Enterprise EBS to Fusion migrations follow one of four patterns. Big bang migrates the entire EBS estate to Fusion on a single cutover date, typically over a 12 to 18 month implementation. Big bang produces the cleanest end-state and the highest implementation cost concentrated in a short window. Risk is concentrated in the cutover weekend.
Phased by module migrates EBS modules to Fusion in sequence: Financials first, then Procurement, then HCM, then SCM. Phased reduces risk per phase but extends parallel-run cost (running both EBS and Fusion simultaneously) for 18 to 36 months. Total cost is typically 10 to 20 percent higher than big bang due to extended parallel-run.
Phased by geography migrates EBS to Fusion country by country or region by region. Common for global enterprises where regulatory complexity varies. Each region performs a mini big bang. Total programme runs 24 to 48 months.
Hybrid coexistence retains EBS for specific functions (Manufacturing, Order Management) while migrating other functions (Financials, HCM) to Fusion. Long-term coexistence pattern, common for customers with deep EBS Manufacturing customisation. Integration complexity is significant.
Common mistakes that destroy conversion value
Three mistakes destroy more migration value than any commercial issue. The first is allowing EBS support to lapse before signing the Fusion conversion contract. Conversion credit requires continuous EBS support history. A 90-day support lapse can reduce conversion credit by 40 to 60 percent because Oracle reframes the conversion as a new customer acquisition rather than a credit-eligible migration.
The second is signing Fusion before negotiating the conversion credit explicitly. Oracle's standard Fusion proposal does not include conversion credit unless the customer requests it during the proposal phase. Customers who sign Fusion as a stand-alone deal and later try to claim conversion credit at renewal receive significantly reduced amounts.
The third is failing to lock the EBS-to-Fusion module mapping in writing at contract signature. Oracle's standard contract language allows the conversion credit to be reapplied at Oracle's discretion if the customer's Fusion deployment scope changes. Buyers should require contract language specifying the credit dollar amount, the application schedule (which years receive credit), and a "no clawback" clause for legitimate scope adjustments.
The EBS parallel run cost
EBS continues to incur support fees during parallel run. A customer paying $1.2M per year in EBS support continues to pay $1.2M throughout the 12 to 36 month parallel-run window, even after Fusion subscription begins. Total parallel-run support cost is typically $1.5M to $3.5M for mid-enterprise customers. The cost is unavoidable but should be modelled into the migration business case rather than discovered after signing.
Some customers attempt to reduce EBS support cost during parallel run by transitioning EBS to third-party support for the final phase of the migration. This produces a 50 percent saving on EBS support fees during parallel run but triggers Oracle's strong resistance on Fusion discount realisation. The math rarely works in favour of third-party support during active migration. Third-party support is better deferred until the migration completes and EBS becomes a residual estate.
The 18 to 24 month conversion calendar
The conversion calendar that produces the best commercial outcome follows a roughly 18 to 24 month structure. Months 1 to 3: independent baseline of the EBS estate, deployment census, conversion credit modelling, and competitive Fusion proposal solicitation against SAP S/4HANA or Workday HCM where applicable.
Months 4 to 6: Oracle Fusion proposal negotiation with explicit conversion credit, multi-year price protection, and implementation partner selection. Sign the Fusion contract at the end of this phase.
Months 7 to 18: implementation phase including data migration, configuration, testing, and parallel-run preparation. Maintain EBS support throughout.
Months 19 to 24: cutover, hypercare, and EBS decommissioning. Cancel EBS support 60 to 90 days after stable Fusion operation, with a documented data archive that preserves audit trail through statutory retention windows.
For the broader Fusion commercial framework, see Fusion pricing 2026. For Oracle Cloud Infrastructure that hosts the Fusion environment, see OCI pricing 2026. For Oracle renewal preparation, see Oracle renewal strategy, Oracle licensing costs 2026, and the complete Oracle licensing guide. For an engagement on a specific EBS to Fusion conversion, see software licensing advisory or cloud contract negotiation or the Oracle vendor hub.