Moving from Oracle E-Business Suite to Oracle Fusion Cloud completely changes your licensing model. You go from owning perpetual licences to renting subscription services. These two models do not directly convert into each other. There is no simple licence swap that turns your on-prem EBS licences into cloud subscriptions. Instead, migrating to the cloud means adding a new subscription model on top of your existing licences. Understanding how the old and new models coexist during the transition is critical to protecting your IT budget.
This guide is part of our Oracle EBS licensing coverage. See also: Oracle EBS Licensing Guide | EBS Cost Optimisation & Negotiation | Complete EBS Module List | EBS Licensing Basics | EBS Licensing Overview
Moving from Oracle E-Business Suite to Oracle Fusion Cloud Applications completely changes your licensing model. You go from owning perpetual licences to renting subscription services. These two models do not directly convert into each other.
| Category | EBS Licence (On-Prem) | Oracle Cloud SaaS (Fusion ERP) |
|---|---|---|
| Type | Perpetual. One-time purchase (owned). | Subscription. Recurring fee (rented). |
| Support | Annual support fees (~22% of licence price) | Included in subscription price |
| Reuse | Stays tied to on-premises usage only | Cannot use on-prem licences to offset SaaS costs |
| Upgrade rights | Only with active support | Automatic upgrades included |
| Cost model | CapEx (licence) + yearly OpEx (support) | Pure OpEx (recurring subscription) |
EBS licences do not convert to Cloud subscriptions. You own your EBS licences forever. You rent your Cloud subscription separately. The real question is how to minimise the overlap and maximise credits during transition. For a full breakdown of EBS licensing models, see our Oracle EBS Licensing Guide.
Oracle offers "credit-style" incentives to entice EBS customers to move to the cloud. While you cannot directly swap a perpetual licence for a SaaS subscription, you can negotiate financial credits based on your existing investment, essentially converting your past and ongoing support fees into cloud discounts.
| Programme / Incentive | How It Works | Customer Benefit |
|---|---|---|
| Support fee credit | Ongoing EBS support spend used as credit against Cloud subscription fees | Avoids double-paying. Lowers cloud cost. |
| Multi-year commitment | Commit to 3 to 5 years of SaaS upfront for larger discounts | Bigger discount percentages and price lock-in |
| EBS transition credit | Oracle assesses your EBS licences and support history for a one-time cloud discount | Leverages existing investments for cloud savings |
| Shelving clause | Oracle pauses on-prem support billing for a defined period during migration | Significant cost relief during dual-run |
| Custom deal incentives | Free extra months, modules, flexible payment terms | Tailored savings based on your situation |
Oracle's credits and incentives are never automatic. They must be negotiated. The more leverage you have (competing cloud bids, quarter-end timing, large support base), the better credits you can secure. For negotiation strategies, see our EBS Cost Optimisation and Negotiation Guide.
Most organisations cannot switch from EBS to Cloud overnight. There will be a period, typically 6 to 18 months, when you run both systems side by side. This dual-run period is the most overlooked cost driver in a cloud migration because you are paying for two systems while maintaining integration between them.
| Cost Component | Overlap Impact | Mitigation Strategy |
|---|---|---|
| EBS support fees | Continue at full rate during dual-run | Plan when to terminate or shelve support. Avoid paying longer than necessary. |
| SaaS subscription | New recurring cost starts immediately | Negotiate subscription start date tied to go-live milestone. |
| Staffing and training | Temporary increase: supporting two systems | Cross-train teams to reduce duplication. |
| Integrations | Added cost to connect EBS and Cloud | Budget for integration tools. Decommission ASAP after cutover. |
| Data migration | One-time project cost overlapping with support fees | Treat as part of implementation budget. |
A Fortune 500 financial services company was projecting an 18-month EBS-to-Cloud overlap costing $3.8M. We negotiated a shelving clause on EBS support for 12 months and aligned the Cloud subscription start date to the first production go-live, reducing the overlap window to 8 months and total dual-run costs to $2.6M.
For understanding what triggers full technology licences during transition, see Customised Database Technology: Oracle EBS Licence Triggers.
A common misconception is that every EBS module has a one-to-one equivalent in Oracle Fusion Cloud. In reality, Fusion Cloud modules are not identical to EBS modules. The cloud suite is organised differently. Some EBS modules are split into multiple cloud services, some features are bundled together, and a few legacy functionalities may not exist in the cloud at all.
| EBS Module | Nearest Cloud Equivalent | Mapping Notes |
|---|---|---|
| Accounts Payable (AP) | Payables Cloud | Direct mapping of core functionality |
| Accounts Receivable (AR) | Receivables Cloud | Direct mapping. Core finance features align. |
| Purchasing | Procurement Cloud (incl. Self-Service) | EBS Purchasing maps to several cloud apps including supplier management and sourcing |
| Human Resources (Core HR) | Oracle HCM Cloud (Core HR) | Core HR maps but Cloud HCM is a full suite. Recruiting, talent, etc. are separate modules. |
| Payroll | Cloud Payroll | Comparable functionally but different technology. May be separate subscription. |
| Projects (Project Accounting) | Project Management Cloud | Check sub-modules. Some features differ. |
| Order Management | Order Management Cloud | Cloud is more integrated with supply chain. Some customisations may not transfer. |
| Inventory | Inventory Management Cloud | Core functions map. Warehouse management may require additional modules. |
Do not assume your cloud subscription covers exactly what your EBS licences did. Read the service descriptions carefully and understand user counts, transaction limits, or any new metrics. A naming similarity does not mean exact functional equivalence. For a complete module list, see our Complete Oracle EBS Application Module List.
A major goal during the transition is to avoid paying twice for the same capability. While some overlap is inevitable during dual-run, unmanaged double licensing can silently add hundreds of thousands of dollars to your migration costs.
| Scenario | Cost Impact | Avoidance Strategy |
|---|---|---|
| Full overlap: EBS Financials and Cloud Financials live at same time | High. Paying twice for ERP finance enterprise-wide. | Plan a swift cutover. Negotiate support credit during overlap. |
| Staggered HR/HCM: EBS HR still in use while Cloud HCM rolls out gradually | High. HR involves many users and critical data. | Migrate HR in shortest feasible timeframe. Avoid parallel core HR. |
| Procurement overlap: EBS Purchasing running while Cloud Procurement is piloted | Moderate. Procurement user base is typically smaller. | Limit pilot to subset. Expand only at full cutover. |
| Partial module migration: Some modules move to cloud, others stay on-prem | Mixed. May permanently pay for both. | Only subscribe to cloud modules you need. Optimise for hybrid state. |
A multinational manufacturer was rolling out Oracle Cloud ERP module by module across 14 regions. Without intervention, the uncoordinated rollout would have run parallel EBS and Cloud Financials for 24 months across half its subsidiaries. We restructured the rollout sequence, aligned EBS support termination dates with cloud go-live milestones per region, and negotiated pro-rated support renewals, reducing effective overlap to 6 months.
Deciding what to do about Oracle Support on EBS during migration is one of the highest-stakes financial decisions. Oracle's annual support fees run at approximately 22% of the licence price per year. If your migration takes 18 months, that is a significant sum on top of your new cloud subscription.
| Strategy | Pros | Cons / Risks |
|---|---|---|
| Keep full Oracle support | Full access to patches, upgrades, and Oracle help during transition | Highest cost. Paying in full even as you plan to leave. |
| Third-party support | 50%+ cost reduction. Often better support for customisations. | No new Oracle patches. Oracle may not honour licence reinstatement. |
| Partial support (segmented) | Savings on modules you drop while keeping critical coverage | Very tricky to execute. Oracle contract rules may prevent it. |
| Terminate support entirely | Immediate and complete cost savings | High risk. No Oracle help if critical issue arises. |
| Negotiated concessions | Saves some money. Shows Oracle you are serious about moving. | Oracle may only concede small discounts or freeze. |
Your support strategy should match your migration timeline and risk appetite. If you are running a 6-month migration, keep full support and negotiate a cap on increases. If you are looking at 18+ months, third-party support can free up budget for the implementation itself.
Migrating from EBS to Oracle Cloud is one of the best opportunities you will ever have to negotiate with Oracle. Oracle wants the cloud subscription revenue and needs to report a successful cloud transition, giving you leverage to ask for better terms.
| Leverage Point | Why It Gives You Power | Typical Oracle Response |
|---|---|---|
| Support renewal month | Oracle fears you might drop support and walk away | Offers cloud credits or discounts equivalent to support spend |
| Identified shelfware | Signals you know you are overpaying for unused licences | May propose converting unused licences into cloud usage |
| Competing cloud proposals | Threat of losing the deal to SAP, Workday, etc. | Accelerates discounting. May add free modules or longer trials. |
| Multi-year commitment | Guarantees Oracle a longer revenue stream | Higher discount tiers and fixed pricing over the term |
| Quarter-end urgency | Sales reps need deals closed to hit targets | More flexible on price and terms as deadline approaches |
A global retail organisation with $2.8M in annual EBS support spend was evaluating both Oracle Fusion Cloud and SAP S/4HANA. By timing the negotiation to Oracle's Q4 fiscal year-end, presenting a genuine competitive bid from SAP, and committing to a 4-year cloud subscription, we secured a 38% discount off list cloud pricing, a full 12-month support shelving clause, and $600K in transition credits, totalling $4.2M in savings over the contract term.
For more negotiation tactics, see our Oracle Contract Negotiation Service and Top 15 Oracle Negotiation Tactics.
Eventually, you will be fully operational on Oracle Cloud and ready to retire E-Business Suite. Shutting down EBS is not just pressing the off switch. You need a clean licensing exit plan to ensure Oracle has no basis to claim you are still using the software.
| Exit Task | Required? | Why It Matters |
|---|---|---|
| Disable production logins | Yes. Critical. | Prevents any further use of EBS. Fundamental step to stop usage. |
| Shut down non-production environments | Yes | Dev, test, backup instances are potential sources of hidden usage. |
| Archive and document licences | Yes | Records of licence counts and retirement date protect you in future audits. |
| Terminate support contract | Yes (eventually) | Stops ongoing fees. Typically requires 30 days' written notice before renewal. |
| Retire custom integrations | Yes | Connectors, data warehouse feeds, reporting links must be redirected or shut off. |
| Archive audit logs | Recommended | Demonstrates system is no longer actively used if questioned later. |
Also read: Oracle EBS Licensing Basics to understand foundational rules during exit planning. For restricted-use database and WebLogic licence implications, see Customised Database Technology: Oracle EBS.
1. Assuming EBS licences convert to Cloud. They do not. You are starting a completely new subscription model. Budgets that assume a "swap" are always wrong.
2. Running the dual-run longer than planned. Every extra month of parallel operation costs you both the EBS support fee and the Cloud subscription. Timeline slippage is the single biggest cost inflator.
3. Not negotiating support credits. Oracle's credit programmes exist specifically for transitions. They are never offered automatically. Organisations that do not ask leave millions on the table.
4. Buying cloud modules before retiring EBS equivalents. Subscribing to Cloud Financials 12 months before EBS Financials is retired means paying for both. Time your cloud purchases to your actual cutover plan.
5. Ignoring module mapping differences. Assuming a naming similarity between EBS and Cloud modules means functional equivalence leads to either over-subscribing or missing critical capabilities.
6. Failing to plan a clean EBS exit. Leaving user accounts active, non-production environments running, or integrations connected after migration creates audit exposure and hidden costs.
7. Negotiating during the wrong time. Approaching Oracle mid-quarter with no competitive alternatives gives you zero leverage. Timing negotiations with Oracle's fiscal year-end (May 31) and presenting genuine alternatives can yield dramatically better terms.
1. Map your entire EBS footprint before engaging Oracle. Understand every module, user type, support contract, and non-production environment. You cannot negotiate what you do not understand.
2. Build a module-by-module transition timeline. Align EBS support termination dates with cloud go-live milestones for each module. The tighter the handoff, the less you spend on overlap.
3. Negotiate as a package deal. You are simultaneously ending on-prem spend and starting cloud spend. Treat it as one negotiation. Credits, shelving clauses, subscription timing, and discount tiers should all be on the table together.
4. Evaluate third-party support as a bridge. If your migration will take 12+ months, third-party support at 50% of Oracle's fees can free up significant budget for the cloud implementation itself.
5. Lock in future pricing. Include clauses for predictable pricing on additional cloud subscriptions. Oracle rewards longer-term commitments with better rates, but only if you ask.
6. Document everything. Keep records of every licence count, support termination notice, user decommissioning date, and environment shutdown. This protects you in future audits.
7. Engage independent advisory early. Oracle's sales team is incentivised to maximise cloud revenue, not minimise your costs. Independent advisors who understand Oracle's pricing model can identify savings opportunities Oracle will never volunteer.
No. EBS perpetual licences and Oracle Cloud SaaS subscriptions are entirely separate models. Your EBS licences remain your property indefinitely, but they cannot be applied or transferred to offset cloud costs. You can, however, negotiate financial credits based on your existing EBS support spend.
EBS support fees continue at the full rate unless you actively cancel or negotiate changes. They do not automatically stop when you sign a cloud contract. You must formally terminate support (typically with 30 days' written notice before the renewal date) or negotiate a shelving clause that pauses fees during the transition.
A shelving clause is a negotiated provision where Oracle temporarily pauses your on-prem EBS support fees during the cloud migration period. This means you do not pay EBS support while implementing the cloud. Shelving clauses must be explicitly negotiated. They are never standard. They are most likely to be granted when you are committing to a significant cloud deal.
No. Fusion Cloud modules are organised differently from EBS. Some EBS modules are split into multiple cloud services (e.g., EBS Purchasing becomes several cloud procurement apps), some features are combined, and a few legacy capabilities may not exist at all. Always perform a detailed functionality and licensing gap analysis before committing to cloud subscriptions.
Most organisations experience a dual-run period of 6 to 18 months, depending on scope and module count. Larger, multi-region deployments with phased rollouts tend to run longer. Every month of dual-run means paying for both EBS support and Cloud subscriptions simultaneously.
Third-party support can reduce EBS maintenance costs by 50% or more and is worth evaluating if your migration will take 12+ months. You will not receive new Oracle patches, but you will get help with existing system issues and customisations. Be aware that switching may complicate your relationship with Oracle, potentially affecting future negotiations or licence reinstatement.
Oracle's fiscal year ends May 31, and sales representatives face the most pressure to close deals during Q4 (March to May). Timing your negotiation to coincide with quarter-end or fiscal year-end typically yields the best discounts. Presenting genuine competitive alternatives (SAP or Workday proposals) further strengthens your position.
Yes. A hybrid approach is common. Many organisations move functions like Financials or HR to the cloud while retaining specialised manufacturing modules on-prem. This creates a permanent split-licensing situation: EBS support for retained modules and Cloud subscriptions for migrated ones. Optimise your licences for this hybrid state to avoid unnecessary costs.
EBS includes restricted-use licences for Oracle Database and WebLogic, valid only for running EBS itself. When you retire EBS, these restricted-use licences also become unnecessary. If you have been using the EBS database or middleware for non-EBS purposes (custom applications, external integrations), you may need to purchase full-use licences or migrate those workloads before shutting down EBS.
Cloud subscriptions typically use metrics like "hosted named user" or "employee" counts, plus transaction-based metrics for certain services. These differ from EBS's Application User, Employee, or Revenue-based metrics. Do not assume your EBS user count directly translates to the same number of cloud subscriptions. The definitions, scopes, and minimums may differ significantly.
Our EBS licensing specialists help enterprises navigate the transition. Dual-run cost modelling, credit negotiation, shelving clauses, clean exit planning, and audit-proof documentation. Independent. Fixed-fee. No Oracle bias.
Oracle Advisory ServicesIndependent Oracle EBS-to-Cloud licensing advisory. Credit negotiation, dual-run optimisation, shelving clauses, clean exit planning. Fixed-fee. Vendor-independent.