Oracle EBS cloud migration licensing turns on one distinction Oracle blurs: a lift-and-shift to OCI is a Bring Your Own License move that keeps every perpetual EBS and database license, while a Fusion Cloud ERP migration is a re-implementation that trades those licenses for a subscription. Because Premier Support for EBS 12.2 now runs to at least 2037, there is no licensing deadline forcing either move in 2026. Pick the path on data-center pressure and transformation need — then protect it with a contracted conversion credit and a clean license count, not Oracle's blended cloud quote.
The most expensive mistake in an EBS cloud program is letting Oracle present "go to cloud" as a single yes/no. Lift-and-shift and Fusion sit at opposite ends of cost, risk, and timeline, and conflating them can swing a five-year number by tens of millions. This guide separates the two, prices each on a buyer-side basis, and every support, pricing, and policy figure below carries a source and a date.
Key takeaways
- Oracle extended EBS 12.2 Premier Support through at least 2037 — the ninth consecutive annual extension under Continuous Innovation, announced April 2026 — so there is no support-cliff reason to migrate in 2026 (Oracle E-Business Suite blog, 2026).
- A lift-and-shift to OCI is a BYOL move that needs no new application licenses — existing perpetual EBS modules and the Oracle Database Enterprise Edition or SE2 underneath them carry across; you license the OCPUs you provision, nothing more.
- A Fusion Cloud ERP migration replaces ownership with a subscription — it is a re-implementation, not an upgrade, and should be costed as a multi-year program, not a like-for-like cloud move.
- A Fusion conversion credit cuts year-one subscription cost 25–40%, but only when negotiated before signature, while staying on EBS is still a credible alternative (industry cost models, 2026).
- Across 600+ Oracle engagements, the parallel-run window — paying EBS support and the Fusion subscription at once — is the single most under-budgeted line in an EBS-to-Fusion business case (Oracle Licensing Experts engagement data, 2026).
Recommendations by role
An EBS cloud decision is proposed by Oracle as one cloud move, paid for by finance over years, defended by the application and DBA teams, and won or lost on whether the licensing path is chosen before the platform is. Here is what each owner does first.
CIO / Head of ERP Strategy
- Force the split: decide lift-and-shift versus Fusion as two separate business cases, never as a single "move to cloud" sign-off.
- Use the 2037 Premier Support runway as bargaining power — you are not under a deadline, and Oracle knows it.
- If Fusion is genuinely needed, scope it as a multi-year transformation with its own funding, not an infrastructure refresh.
VP Procurement / Vendor Management Deal
- Negotiate the Fusion conversion credit into the ordering document before signature — 25–40% off year one is on the table only while EBS is your fallback.
- Refuse a blended "cloud" quote; demand subscription, implementation, and parallel-run costs as separate, named lines.
- Cap the Fusion renewal uplift at signing so the conversion credit is not clawed back at the first renewal.
SAM / ITAM & DBA Control
- Inventory EBS Application Users and database options before any move so you carry across a clean, right-sized count, not a peak.
- Drop unused database options — Partitioning, Diagnostics Pack, Advanced Compression — before licensing them again on OCI.
- Size OCI in OCPUs to actual workload; over-provisioned cores are a BYOL Processor cost that recurs every year.
CFO / Finance Cost
- Budget the full Fusion program — implementation at 60–70%, subscription, and parallel run — not Oracle's headline subscription figure.
- Model a lift-and-shift as a low-cost option that preserves licenses and buys time, then compare it honestly to the Fusion total.
- Hold the conversion credit and renewal cap as contractual line items finance can audit, not verbal commitments.
The Oracle EBS cloud migration framework: seven questions that decide your cost
What does "move EBS to the cloud" actually mean?
It means two completely different things, and Oracle benefits when you do not separate them. A lift-and-shift re-hosts the same E-Business Suite software and its database onto Oracle Cloud Infrastructure under BYOL — same code, same customizations, same licenses, different infrastructure. A Fusion Cloud ERP migration retires EBS entirely and re-implements your processes on a separate subscription product. One is an infrastructure project measured in months; the other is a transformation measured in years. Treat them as one decision and you will either over-buy Fusion or under-scope the program that replaces a 20-year-old ERP.
If an Oracle proposal uses "cloud migration" to mean Fusion without ever pricing the lift-and-shift alternative, that omission is the tactic. The cheapest credible path is the one Oracle has the least incentive to put in writing.
Lift-and-shift keeps your licenses and buys time. Fusion replaces them with a subscription. Letting Oracle merge the two into one "cloud" decision is how the cost runs away.
Is there a support deadline forcing an EBS move in 2026?
No. In April 2026 Oracle extended Premier Support for E-Business Suite 12.2 through at least 2037 — its ninth consecutive annual extension since the 2018 Continuous Innovation commitment (Oracle E-Business Suite blog, 2026). EBS 12.2 customers remain in full Premier Support, receiving patches, security fixes, and regulatory updates, with no extended-support surcharge. The "your ERP is going end-of-life" pressure that once drove cloud decisions simply does not apply. You are choosing on business merit, not a countdown, and that runway is itself bargaining power.
Across our EBS engagements, customers who believed they faced a near-term support cliff were quoted Fusion programs 30–40% larger than those who knew Premier Support ran to 2037 and negotiated from a no-deadline position (Oracle Licensing Experts benchmark, 2026). The deadline you assume sets the price you pay.
What does a lift-and-shift to OCI cost in licenses?
In application licenses, nothing new. A true lift-and-shift applies your existing perpetual EBS module licenses and the Oracle Database Enterprise Edition or Standard Edition 2 licenses underneath them to OCI on BYOL, so you do not repurchase the software you already own. The cost shifts to infrastructure: OCI compute is metered in OCPUs, and your database Processor licenses must cover the cores you provision. The two real exposures are over-provisioning OCPUs and carrying across database options — Partitioning, Diagnostics Pack, Advanced Compression — that must be licensed on OCI exactly as on-premise.
Run an options and OCPU audit before the cutover, not after. Every option you can prove is unused, and every core you do not provision, is a Processor license you stop paying 22% support on for the life of the platform.
What does a Fusion Cloud ERP migration really cost?
Far more than the subscription line implies. An EBS-to-Fusion Cloud ERP migration ranges from roughly $200,000 for a 500-user mid-market conversion to $20 million or more for a global enterprise, and the shape of the cost is consistent: implementation services are 60–70% of the total, the year-one Fusion subscription is 15–25%, and running EBS in parallel during the transition is 10–20% (industry cost models, 2026). The subscription Oracle leads with is the smallest of the three numbers. The program cost — system integrator, data migration, re-training, parallel run — is where the budget actually goes.
"Show me total five-year cost: subscription, implementation, and the months we run EBS and Fusion in parallel — as three separate lines." A Fusion business case built only on the subscription is missing two-thirds of the spend.
How does a Fusion conversion credit work, and when is it real?
A conversion credit is the discount Oracle grants on a Fusion subscription to recognise the EBS licenses and support you relinquish by moving. Negotiated before signature, it commonly cuts year-one Fusion cost by 25–40% (industry cost models, 2026). The credit is leverage-dependent: it exists only while staying on EBS is a credible alternative Oracle has to beat, and it must be written into the ordering document. Raised after you have publicly committed to Fusion, it shrinks — Oracle no longer has to win a decision you have already made for it.
Keep the lift-and-shift quote live on the table through the entire Fusion negotiation. The conversion credit is priced to the alternative Oracle can see; remove the alternative and you remove the credit.
What happens to my database stack and options on OCI?
EBS always sits on a separately licensed Oracle Database, and that stack is the part most often mis-licensed in a cloud move. On a lift-and-shift, your Database EE or SE2 licenses are BYOL-eligible on OCI, but every database option in use travels with the workload and must be separately licensed there. The classic trap is options enabled by EBS or a DBA years ago — Partitioning, Tuning Pack, Advanced Compression — that nobody removed, now re-licensed on OCI by default. A pre-migration options scan converts that silent cost into a deliberate decision.
"Customer's existing perpetual Database Enterprise Edition and option licenses are authorized for Bring Your Own License use on Oracle Cloud Infrastructure for the migrated E-Business Suite environment, with Processor quantities counted on the OCPUs provisioned, and no additional license fee for the re-hosting of previously licensed programs."
How do you keep leverage across an EBS cloud program?
You keep it by refusing the single-decision frame and by never surrendering the EBS fallback before you have to. Cost the lift-and-shift first, because it is cheap, fast, and license-preserving, and it sets the floor every Fusion quote must beat. Watch the 2026 tactic: Oracle increasingly bundles Fusion AI and analytics features into the migration pitch to justify the subscription, so pin down exactly which capabilities are included in your rate and which trigger new charges. Settle any open EBS or database compliance questions before you negotiate the move, not during — an unresolved options finding in the middle of a Fusion deal is the leverage Oracle most wants. The buyer who holds a credible lift-and-shift, a clean license count, and a 2037 support runway negotiates the cloud move on their terms.
Sequence it: compliance clean-up, then lift-and-shift pricing, then Fusion with a contracted conversion credit. Reverse that order and you negotiate the biggest spend from the weakest position.
Which EBS cloud path fits your situation?
Lift-and-shift to OCI on BYOL
Lowest cost, lowest risk. Licenses carry across, customizations survive, Premier Support runs to 2037. Buys a decade of runway while you decide whether transformation is ever justified.
Fusion Cloud ERP with conversion credit
Justified when the business needs genuinely new capability. Cost it as a multi-year program; protect it with a 25–40% conversion credit and a renewal cap contracted before signature.
OCI Cloud@Customer / Exadata Cloud@Customer
A middle path: OCI economics inside your own data center. Preserves BYOL and residency, but verify option and OCPU counts — the licensing mechanics mirror OCI, not on-premise.
Stay on EBS 12.2 under Premier Support
Entirely defensible. With support to 2037 and no hardware crisis, doing nothing is a valid, low-cost option — and a strong negotiating stance for whenever you do move.
There is no single right path — only the one that matches your hardware timeline, transformation need, and data-residency rules. The common error is treating Fusion as the default when a lift-and-shift, or staying put, is cheaper and lower-risk.
Lift-and-shift versus Fusion: a five-year cost shape
Strengths and cautions of each EBS cloud path
| Path | Strength | Caution |
|---|---|---|
| Lift-and-shift to OCI (BYOL) | No new application licenses; keeps customizations; fast; preserves the 2037 support runway | Database options and OCPU counts must be right-sized, or carried-over cost recurs every year |
| Fusion Cloud ERP | Modern, vendor-maintained ERP with new capability; ends infrastructure ownership | Implementation is 60–70% of cost; subscription compounds at renewal; parallel run is routinely under-budgeted |
| Cloud@Customer | OCI economics with data residency; BYOL preserved on-site | Licensing mirrors OCI, not on-premise; verify option coverage and contract terms carefully |
| Stay on EBS 12.2 | Zero migration cost; full Premier Support to at least 2037; maximum negotiating leverage retained | Aging hardware and skills must still be managed; defers rather than removes the eventual decision |
Acronyms and key terms
- E-Business Suite (EBS)
- Oracle's on-premise enterprise application suite — Financials, Procurement, HR, Supply Chain, Manufacturing — licensed perpetually by module and user.
- Lift-and-Shift
- Re-hosting the existing EBS application and its database onto OCI without changing the software, under Bring Your Own License.
- BYOL
- Bring Your Own License — applying perpetual on-premise Oracle licenses to OCI instead of buying new cloud entitlements.
- Fusion Cloud ERP
- Oracle's subscription-based, re-implemented cloud ERP product; a destination platform, not an upgrade of EBS.
- Conversion Credit
- A negotiated discount on a Fusion subscription recognising the EBS licenses and support relinquished, typically cutting year-one cost 25–40%.
- OCPU
- Oracle Compute Processing Unit — the core-counting unit on OCI; database BYOL must cover the OCPUs provisioned.
- Premier Support
- Oracle's full support tier — patches, security and regulatory updates — extended for EBS 12.2 through at least 2037.
- Application User
- The named-user metric for EBS modules; every individual authorized to use a licensed module, including self-service users, requires a license.
- Parallel Run
- The period during a Fusion migration when EBS and Fusion operate simultaneously, generating duplicate support and subscription cost.
- Cloud@Customer
- Oracle OCI or Exadata infrastructure deployed in the customer's own data center, an option for EBS workloads with data-residency constraints.
- Database Option
- Separately licensed EE features — Partitioning, Diagnostics Pack, Advanced Compression — that must be licensed on OCI as they were on-premise.
- Sustaining Support
- Oracle's lowest support tier — no new fixes, patches, or regulatory updates; reached only after Extended Support ends.
Oracle EBS cloud migration FAQ
Does lift-and-shift of Oracle EBS to OCI need new licenses?
No. Lift-and-shift of Oracle E-Business Suite to Oracle Cloud Infrastructure is a Bring Your Own License move: your existing perpetual EBS application licenses and the separate Oracle Database licenses underneath them continue to apply, so you do not buy new entitlements to run the same software on OCI. What changes is the infrastructure and the metering of the database tier, where OCI compute is counted in OCPUs and you must license the cores you provision. The traps are the database options that travel with the workload and the temptation to over-provision OCPUs, not the EBS application licenses themselves.
How long is Oracle E-Business Suite supported?
Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2037, the ninth consecutive annual extension under its Continuous Innovation model, announced in April 2026. That means EBS 12.2 customers stay in full Premier Support — patches, security fixes, and regulatory updates — without an extended-support surcharge for the foreseeable future. There is no licensing reason to rush an EBS cloud migration in 2026; the support cliff that once forced the decision has been pushed more than a decade out.
What is the difference between EBS lift-and-shift and Fusion migration?
An EBS lift-and-shift moves the same E-Business Suite software onto OCI under BYOL, keeping your perpetual licenses, your customizations, and your support stream intact. A Fusion Cloud ERP migration is a re-implementation onto a different, subscription-based product: you stop using EBS, rebuild processes in Fusion, and pay a per-user annual subscription instead of owning the license. Lift-and-shift is an infrastructure decision measured in months; Fusion is a transformation program measured in years, and the two should never be presented as a single cloud choice.
How much does an Oracle EBS to Fusion migration cost?
An Oracle EBS to Fusion Cloud ERP migration ranges from roughly $200,000 for a 500-user mid-market conversion to $20 million or more for a global enterprise. The cost has three parts: implementation services, which are 60 to 70 percent of the total; the Fusion subscription in year one, 15 to 25 percent; and the cost of running EBS in parallel during the transition, 10 to 20 percent. Implementation, not the subscription, is the dominant number, and it is the part Oracle's headline subscription quote does not show.
What is an Oracle Fusion conversion credit?
A conversion credit is a discount Oracle applies to a Fusion Cloud subscription in recognition of the EBS licenses and support you are giving up when you move. Negotiated before signature, a conversion credit commonly reduces year-one Fusion cost by 25 to 40 percent. It is only available while you still hold the leverage of staying on EBS, and it must be written into the ordering document; raised after you have committed to Fusion, it is worth far less because Oracle no longer has to win the decision.
Can I keep my Oracle Database licenses when I move EBS to OCI?
Yes. The Oracle Database Enterprise Edition or Standard Edition 2 licenses underneath E-Business Suite are BYOL-eligible on OCI, so a lift-and-shift carries them across without repurchase. The two things to verify are core counting — OCI meters in OCPUs and you must hold enough Processor licenses for the cores you run — and database options such as Partitioning, Diagnostics Pack, or Advanced Compression, which must be separately licensed on OCI exactly as they were on-premise. Dropping an unused option before the move is a clean way to cut the carried-over cost.
Should I move Oracle EBS to the cloud in 2026?
There is no licensing emergency forcing an EBS cloud migration in 2026, because Premier Support for EBS 12.2 now runs to at least 2037. The right move depends on data-center pressure and transformation goals, not a support deadline. If hardware is end-of-life, a lift-and-shift to OCI on BYOL buys time cheaply while preserving licenses. If the business genuinely needs new ERP capability, a Fusion re-platform is justified — but it should be costed as a multi-year program with a negotiated conversion credit, never sold as a like-for-like cloud upgrade.
Methodology & sources
The support-lifecycle dates, licensing mechanics, and migration cost shapes in this guide are drawn from Oracle's published 2026 lifecycle and price-list documentation and from Oracle Licensing Experts engagement data across 600+ Oracle negotiations and audits. Proprietary figures are labelled "Oracle Licensing Experts benchmark, 2026" or "OLE model, 2026" and reflect outcomes from buyer-side advisory work; they are directional ranges, not guarantees. Oracle revises its lifetime-support policy and price list periodically — always confirm the current support date and figure against the live Oracle documentation for your region before building a business case. For deeper detail, see our Oracle EBS licensing guide and Oracle Fusion Cloud applications guide, and our buyer-side Oracle license optimization and contract negotiation services.
- Oracle Corporation, EBS 12.2 Premier Support Extended Through At Least 2037, April 2026 — the ninth annual Continuous Innovation extension of EBS Premier Support.
- Oracle Corporation, Oracle Lifetime Support Policy: Oracle Applications, 2026 — Premier, Extended, and Sustaining Support definitions and EBS timelines.
- Oracle Corporation, EBS Cloud Migration — Oracle's lift-and-shift to OCI and re-platform paths for E-Business Suite.
- Oracle Corporation, Oracle E-Business Suite Applications Global Price List, 2026 — module list pricing and the named-user metric carried into any BYOL move.
- Oracle Licensing Experts engagement data, 2026 — lift-and-shift versus Fusion cost shapes, conversion-credit ranges, and parallel-run budgeting across 600+ engagements.
Download this guide as a PDF
Take the full Oracle EBS Cloud Migration Licensing guide into your next planning session — the lift-and-shift versus Fusion split, the 2037 support runway, the conversion-credit math, and the database-option traps in one printable brief. We also model your specific EBS estate against both paths on request.
Request the PDF & an EBS cloud review →Keep reading
Free weekly Oracle briefing
EBS lifecycle alerts, OCI BYOL intelligence, and Fusion negotiation tactics — from former Oracle insiders.
Choose your EBS cloud path before Oracle chooses it for you
Get an independent, buyer-side review of your Oracle EBS cloud options — the lift-and-shift that preserves your licenses, the Fusion conversion credit Oracle will not volunteer, and the database-option exposure that follows the workload. In one anonymized engagement we held a Fortune 500 manufacturer's EBS licenses intact through an OCI move and cut its first Fusion quote by $4.1M. We have advised on $1.8B of Oracle spend and cut costs an average of 38%.