Oracle is in the process of moving its on premises applications customer base (E Business Suite, PeopleSoft, JD Edwards, Siebel, Hyperion, Agile PLM) to Oracle Fusion Cloud through a multi year migration cycle that picks up pace in 2026 and 2027. The strategic intent is clear: Oracle wants Fusion Cloud bookings, and the on premises applications support stream is in managed decline. The customer side question is rarely "should we migrate" but rather "when, on what terms, and through which path."
Three migration patterns exist: lift and shift (limited customization, fastest path), re implementation (greenfield Fusion Cloud, longest engagement), and hybrid (mixed legacy and Fusion deployment over an extended transition window). Each carries different commercial mechanics, different cloud credit math, and different impact on existing Oracle ULAs.
This pillar sets out the on premises portfolio, the Fusion Cloud destination products, the three transition pathways, the cloud migration credit framework, and the eleven move buyer side playbook for managing the Fusion Cloud transition as the largest Oracle commercial event most enterprises will face this decade. For surrounding context read the Oracle services practice, the Oracle knowledge hub, the Oracle CIO playbook, and the Oracle ULA decision framework.
Five things every Oracle applications customer should know
- Oracle E Business Suite premier support extends through 2034, but Oracle is steering to Fusion Cloud now
- Three migration paths exist: lift and shift, re implementation, hybrid
- Cloud migration credits typically run 15 to 40 percent of first year Fusion Cloud subscription
- Existing Oracle ULAs require careful exit timing; Fusion Cloud transition can complicate certification
- Third party support is a credible alternative for customers extending on premises beyond Oracle's preferred timeline
The Oracle on premises applications portfolio
Oracle's on premises applications stack covers four principal product families:
| Product family | Use case | Premier support timeline |
|---|
| Oracle E Business Suite (EBS) | ERP, manufacturing, finance, supply chain | Through 2034 (extended) |
| Oracle PeopleSoft | HCM, financials, public sector | Through 2034 (PS9.2 extended) |
| Oracle JD Edwards EnterpriseOne | ERP for distribution, manufacturing, construction | Through 2033 |
| Oracle Siebel CRM | CRM, sales force automation | Through 2032 |
Oracle's published support timelines remain generous on paper. The commercial reality is different: Oracle account teams steer customers toward Fusion Cloud at every renewal touchpoint, support pricing escalators trend upward more aggressively on the on premises base, and new investment in on premises product development has effectively stopped. Customers running EBS, PeopleSoft, JD Edwards, or Siebel face an unspoken Oracle preference for migration well ahead of formal end of support dates.
The Oracle Fusion Cloud destination
Oracle Fusion Cloud Applications spans five product families:
- Fusion Cloud ERP: Successor to E Business Suite Financials, JD Edwards, and PeopleSoft Financials
- Fusion Cloud HCM: Successor to PeopleSoft HCM, competing with Workday HCM
- Fusion Cloud SCM: Successor to JD Edwards manufacturing/distribution and EBS Supply Chain
- Fusion Cloud CX: Successor to Siebel CRM
- Fusion Cloud EPM: Successor to Hyperion (Enterprise Performance Management)
Fusion Cloud is licensed per user per month, with pricing varying by module and user role. Indicative ranges: Fusion Cloud ERP at $175 to $250 per user per month, Fusion Cloud HCM at $50 to $150 per worker per year (against the broader workforce, not finance user count), Fusion Cloud SCM at $200 to $400 per user per month for power users.
The three transition pathways
| Pathway | Timeline | Best fit when |
|---|
| Lift and shift | 12 to 18 months | Limited customization on legacy; preserve current process |
| Re implementation | 24 to 36 months | Heavy legacy customization; greenfield Fusion adoption |
| Hybrid | 36 to 60 months | Multi entity estates; phased rollout by business unit or geography |
Oracle Fusion Cloud migration credits
Oracle offers cloud migration credits to customers transitioning from on premises to Fusion Cloud. Three credit types matter at procurement:
- Migration credits. Offset first year Fusion Cloud subscription cost, typically 15 to 40 percent of year one.
- Proof of concept credits. Fund initial Fusion Cloud pilot deployments at no charge.
- Marketing development funds (MDF). Co fund customer success programs, integration partner work, and reference activities.
The buyer side move is to negotiate cloud migration credits explicitly at signing, calendar credit expiration dates separately from the master subscription, and document credit utilization quarterly to avoid forfeiture.
Support reduction at transition
The Oracle Fusion Cloud transition triggers a structural support cost reduction opportunity. Customers running on premises EBS, PeopleSoft, JD Edwards, or Siebel typically pay 22 percent of original license fee in annual support. As workloads migrate to Fusion Cloud, the corresponding on premises support entitlements can be retired. Three structural patterns matter:
- Retire support on retired licenses promptly. Do not continue paying support on shelfware.
- Evaluate third party support for the on premises tail. Rimini Street or Spinnaker Support during the transition window. Third party support runs typically 50 percent below Oracle premier support.
- Document support retirement against ULA certification carefully. Critical if a ULA is in flight.
The Oracle ULA impact
Customers running Oracle Unlimited License Agreements (ULAs) face structural complexity at Fusion Cloud transition. ULAs typically cover specific Oracle Database products and certain options. Fusion Cloud Applications run on Oracle Cloud Infrastructure with embedded Database licensing; the customer's existing ULA may or may not certify into the Fusion Cloud deployment depending on contract language. The buyer side move is to engage ULA certification specialists 12 to 18 months ahead of any major Fusion Cloud transition to confirm certification path, document deployment scope, and avoid the structural trap of ULA certification colliding with active Fusion migration.
Six Fusion Cloud transition traps
- Cloud migration credits without expiration tracking. Credits routinely forfeit due to calendar drift.
- On premises support retention overlap. Continuing to pay support on retired licenses.
- ULA certification timing collision. Active ULA running during major Fusion migration.
- Re implementation cost underestimation. Greenfield Fusion implementations routinely 2x to 3x initial budget.
- Third party support not evaluated. Tail on premises estate continuing on Oracle premier support unnecessarily.
- Renewal escalator default. Fusion Cloud subscription escalators default 5 to 8 percent annually; negotiate to CPI plus 3 percent.
Fusion Cloud renewal cycle
Fusion Cloud Applications run on three or five year subscription terms with annual billing. The structural renewal lever is the user count escalation: Fusion Cloud bills against contracted user count, not active user count, and Oracle expects user count growth at every renewal. The buyer side move is to negotiate forward user count flexibility at signing, including true down rights where the customer's actual user count is lower than the contract baseline at renewal.
The audit framework during transition
Oracle audits typically pause during active Fusion Cloud transition periods on the assumption that audit conversations would derail the migration commercial relationship. This is not a guarantee, however. Customers should maintain audit defense posture (deployment documentation, options enablement evidence, partitioning rationale) through the transition window. Read the Oracle audit response playbook for the full audit defense framework.
The eleven move buyer side playbook
- Inventory the on premises Oracle applications estate. EBS, PeopleSoft, JD Edwards, Siebel, Hyperion deployments.
- Decide migration pathway intentionally. Lift and shift, re implementation, or hybrid based on customization level.
- Negotiate cloud migration credits at signing. 15 to 40 percent of year one Fusion Cloud subscription.
- Calendar credit expiration dates. Avoid forfeiture through tracking discipline.
- Retire on premises support promptly. Do not continue paying on retired licenses.
- Evaluate third party support for tail estate. Rimini or Spinnaker for the on premises window.
- Audit ULA certification timing. Avoid ULA certification colliding with Fusion migration.
- Negotiate Fusion Cloud user count flexibility. True down rights at renewal.
- Cap Fusion Cloud subscription escalator. CPI plus 3 percent maximum.
- Document deployment baseline. Establish baseline for next renewal negotiation.
- Run continuous Oracle vendor management. Fusion transition is the largest event in a continuous workstream.
The framework is set out in detail across the Oracle services practice, the Oracle knowledge hub, the Oracle CIO playbook, the Oracle third party support transition service, the Oracle ULA framework, and the broader Oracle cluster.
How we engage
- Oracle Fusion Cloud transition scoping. Six week engagement that scopes the Oracle Fusion Cloud transition framework, anchors the customer's actual Oracle Fusion Cloud transition deployment framework, and identifies the immediate commercial moves at the next Oracle Fusion Cloud transition renewal cycle. Vendor Shield.
- Oracle Fusion Cloud transition negotiation. Contract negotiation engagement that handles the Oracle Fusion Cloud transition framework, the user framework, the contracting framework, and the broader Oracle Fusion Cloud transition renewal conversation across the renewal cycle. renewal program.
- Oracle Fusion Cloud transition audit defense. Audit defense engagement that handles the Oracle Fusion Cloud transition audit framework, the compliance framework, and the broader Oracle Fusion Cloud transition audit response framework. audit defense kits.
- Vendor Shield. Always on multi vendor management posture that covers the Oracle Fusion Cloud transition framework alongside the broader enterprise software estate. Vendor Shield.
- Run the assessment. The software spend assessment sizes the Oracle Fusion Cloud transition framework against the customer's actual Oracle Fusion Cloud transition deployment framework.
- Cross vendor benchmarking. The benchmarking practice benchmarks the Oracle Fusion Cloud transition framework against the broader market framework.
