The Fusion Cloud proposal on your desk probably compares one number to another: a subscription against your EBS support bill. That comparison leaves out most of the money. This post builds both sides over five years, line by line, so you can check the math against your own contract.

The short answer

  • Staying on EBS 12.2 isn't forced to end. Oracle has committed Premier Support through at least 2037, so the question is cost, not a deadline.
  • For a smaller organization, our illustrative five-year cost of moving to Fusion comes to roughly $4.9M–$11M once you add EBS support during the project and update testing. Staying costs about $5.5M–$6.1M.
  • Conversion credits can narrow the gap, but advisors say they're negotiated, not offered, and timing decides how much you get.

Start with the deadline that isn't there

Oracle's March 2026 announcement extends Premier Support for E-Business Suite 12.2 through at least 2037. It also notes a pattern of adding a year as each year passes. Nothing forces you onto Fusion on a fixed date. That gives you time to decide on cost and fit, and it strengthens your hand in the negotiation.

The cost of staying on EBS

Support is the core line. Oracle Licensing Experts, a consultancy that sells support-reduction services, puts it at 22% of net license value a year, often rising 3–5% annually.

Take the illustrative company we use on our site: about 500 users and $5M in net license value. Support is $5M × 22% = $1.1M a year.

  • Flat for five years: $1.1M × 5 = $5.5M.
  • Rising 3% a year: $1.1M + $1.13M + $1.17M + $1.20M + $1.24M = about $5.84M.
  • Rising 5% a year: $1.1M + $1.16M + $1.21M + $1.27M + $1.34M = about $6.08M.

You also pay for hosting, DBAs, and the people who keep EBS running. Those are already in your budget, so count them on both sides or neither. Some of them carry on during a Fusion project anyway.

The cost of moving to Fusion, line by line

Implementation

ERP Research, a pricing-research site, estimates $1.5M–$4M for organizations under 500 employees, with 12–18 months for a reimplementation. The same source breaks a typical budget down: system integrator fees 55–65%, internal project team 10–15%, data migration 10–15%, and contingency 15–20%. It also warns that remediating customizations can add 30–50% of implementation cost. That's the line that grows when your EBS has been heavily tailored.

Subscription

ERP Research puts five-year Fusion software at $2M–$5M for the same size band. Ask your Oracle rep two questions. When does billing start relative to go-live? And what happens to price at the first renewal?

Parallel running

EBS support doesn't stop when you sign. You keep paying it until you switch off, and the proposal rarely shows it. At $1.1M a year, 12–18 months of overlap costs $1.1M–$1.65M.

Testing quarterly updates

Fusion updates aren't optional. Oracle's quarterly update guide says updates arrive on a predefined schedule, "are required and they can't be rescheduled." Test environments get them two weeks before production. Any problems must be resolved with Oracle Support before your production date. Oracle recommends testing integrations, third-party systems, and key business flows each time.

Oracle doesn't publish what that costs you, so here's an illustrative estimate. Four updates a year, with 3 people spending 10 working days on each, is 120 person-days. At an assumed $800 loaded day rate, that's $96,000 a year. Over the 3.5 to 4 years after go-live, it comes to roughly $0.34M–$0.38M. Use your own rate and team size.

Integrations

Every interface into EBS is rebuilt or re-pointed during implementation, and then retested every quarter. Keep integration work explicit in the scope so it isn't buried in contingency.

The five-year comparison

Line itemStay on EBSMove to Fusion
EBS support$5.5M–$6.1M$1.1M–$1.65M (12–18 months of overlap)
ImplementationNone$1.5M–$4M
Fusion subscription, five yearsNone$2M–$5M
Quarterly update testingNoneAbout $0.34M–$0.38M (illustrative)
Customization remediation riskNoneUp to 30–50% of implementation, if not already scoped
Illustrative totalAbout $5.5M–$6.1MAbout $4.9M–$11M, before any conversion credit

Illustrative only. Move total = $1.5M + $2M + $1.1M + $0.34M at the low end, and $4M + $5M + $1.65M + $0.38M at the high end. Third-party planning estimates, not Oracle price lists. Remediation risk isn't added to the total.

The ranges overlap. A tightly scoped move at the low end can cost less than staying. A typical one costs more, and the subscription doesn't stop after year five.

Five-year cost: staying on EBS against moving to FusionIllustrative, $M, before any conversion credit
$0M$3M$6M$9M$12MStay on EBS supportStay on EBS support: $5.5M–$6.1M$5.5M–$6.1MMove to Fusion CloudMove to Fusion Cloud: $4.9M–$11M$4.9M–$11M

Illustrative totals from this guide. Sources: ERP Research; Oracle Licensing Experts.

View the data
PathFive-year cost
Stay on EBS support$5.5M–$6.1M
Move to Fusion Cloud$4.9M–$11M, before any conversion credit

How conversion credits work, according to advisors

Oracle doesn't publish its credit terms, so everything here comes from advisors and should be checked against your own proposal.

  • ERP Research says Oracle commonly bundles a 25–40% conversion credit into Fusion deals signed ahead of an EBS support event. It reports that some customers also negotiate "shelving" rights that stop EBS support fees on shelved licenses during the transition.
  • Atonement Licensing, which sells migration advisory, describes a similar 25–40% range. It says the credit is based on net EBS license value, requires continuous support history, applies to the early years, and ends from year four.
  • Atonement also says the credit isn't in Oracle's standard proposal unless you ask for it. It's worth more when negotiated before you sign than afterward.

Two implications. First, don't let support lapse before you negotiate, or you may shrink the credit. Second, model years four and five at full price, because that's where a front-loaded credit stops helping.

The option the proposal leaves out

Fusion and EBS aren't the only choices. You can also rebuild your operational workflows as software you own, with AI agents built in, move finance and payroll to cloud products, and switch Oracle off in 24–30 months. Our Escape Path page shows how, and our SAP worked example shows the numbers for a $200M manufacturer: about $5.8M over five years, including our fees. We offer this, so weigh our view accordingly. Either way, the decision should rest on your numbers, not a sample.

Six questions to put to the Fusion proposal

  1. When does subscription billing start, and how many months will we pay for both EBS and Fusion?
  2. What conversion credit applies, in dollars and by year, written into the contract?
  3. Can we shelve EBS licenses and stop support on them during the transition?
  4. What price protection applies at the first renewal, and after year five?
  5. Who tests each quarterly update, how many days does it take, and who pays?
  6. Which customizations are we rebuilding, and which should we retire or rebuild outside Oracle?

Where to go from here

Put your own license value, support rate, and proposal figures into the model, and compare the totals. If you'd like a second opinion, tell us what you run and what you've been quoted, and we'll tell you honestly which path pencils out. You can see how a staged approach works on our Escape Oracle page.

Sources