Oracle applications span five major lines: E-Business Suite, JD Edwards EnterpriseOne, PeopleSoft, Siebel and the Fusion SaaS portfolio. The Admodum read on the legacy on-premises estate, the Fusion migration path, the licensing metrics and the renewal posture across each line.
E-Business Suite (EBS) is the long-running Oracle applications platform that grew out of the original Oracle Applications product family. EBS licenses primarily on the Application User metric (a named individual with access rights to one or more modules) and the Module construct (the licensed product line: Financials, HR, Supply Chain, Manufacturing, Order Management, Procurement and others).
The Application User definition counts every named individual with rights to use the modules; the count includes employees, contractors and external users (suppliers, customers) with portal access. The buyer-side discipline at the renewal moment is to read the Application User population against the actual named-user master and to reconcile inactive accounts. EBS Premier Support continues through at least 2034 under the most recent Oracle commitments; the on-premises horizon is therefore long enough that EBS estates are not under forced migration pressure.
The wider editorial sits at the Oracle pillar and the engagement at the Oracle practice.
JD Edwards EnterpriseOne and PeopleSoft are the two other major Oracle applications lines acquired in the mid-2000s (JD Edwards via the PeopleSoft acquisition, PeopleSoft directly). Both lines remain in active Premier Support. JD Edwards licenses on Module and Enterprise / Standard Edition constructs; PeopleSoft licenses on Module and User metric (varying by module).
Oracle has reset the on-premises horizon for both products multiple times. Premier Support for current releases continues, and the publisher continues to ship platform updates. The migration conversation runs from JD Edwards to Fusion Cloud ERP (the natural target for finance and supply chain) and from PeopleSoft to Fusion Cloud HCM or ERP depending on the in-scope modules. The economics of the migration sit in section v.
Siebel CRM is the Oracle customer-relationship-management line, acquired in 2006. Siebel licenses on Concurrent User (the number of simultaneous active sessions) and Named User Plus (named individuals with access rights). The Concurrent User metric is a Siebel-specific construct distinct from the database Named User Plus metric on the technology side (see the Named User Plus metric).
Siebel remains in active Premier Support, and the publisher continues to ship innovation packs (IPs). The natural migration target is Fusion CX (Service, Sales, Marketing) and, for service-heavy use cases, Oracle Service Center. Many Siebel estates remain on-premises by deliberate buyer-side choice (customisation depth, integration density, residual investment); the buyer-side discipline is to read the Siebel renewal alongside the Fusion CX commercial position even where migration is not planned.
Fusion SaaS is the Oracle next-generation applications portfolio: Fusion Cloud ERP (Financials, Procurement, Project Management), Fusion Cloud HCM (Core HR, Talent, Payroll, Time and Labour, Learning), Fusion Cloud SCM (Supply Chain, Manufacturing, Order Management), Fusion Cloud CX (Service, Sales, Marketing, Commerce) and the Fusion Analytics and AI overlay.
Fusion licenses on per-user per-module subscription. The unit price varies by module and the contract typically commits a minimum user count over a multi-year term. The buyer-side discipline at sign is to read the module bundling carefully: some modules are bundled (Financials with Procurement), some are priced separately, and some modules carry per-transaction add-on charges (advanced AI features in particular). The wider read on the Fusion subscription model sits at the Fusion SaaS spoke.
The publisher prices the migration journey from on-premises EBS, JDE, PeopleSoft and Siebel to Fusion SaaS. The pricing typically takes one of three forms: a migration credit against the residual perpetual position (with a discount on the Fusion subscription), a bridge agreement allowing parallel on-premises and Fusion use during the transition, or a clean Fusion subscription with the on-premises position dropped at term-end.
The buyer-side discipline is to evaluate the migration on the total cost of the journey, not on the destination headline subscription rate. The journey often includes a multi-year parallel-run period, a residual on-premises support cost, customisation rewrite, integration re-build, training and change management. The aggregate migration cost frequently materially exceeds the headline subscription figure. The deeper read on the renewal sequencing sits at the Oracle renewal cycle.
What the buyer holds across the applications portfolio: a long on-premises horizon under Premier Support, a published Fusion SaaS destination, a migration conversation that the publisher initiates and prices, and a buyer-side decision tree on whether and when to migrate each application line.
What the buyer does not hold by default: a forced migration timeline. The publisher offers migration; the publisher does not (under current commitments) terminate Premier Support on the legacy lines. The buyer-side optionality is real, and the renewal-table conversation should reflect that optionality rather than treat migration as a foregone conclusion.
The wider editorial sits in the Oracle licensing pillar. The aggregated reading list sits in the Oracle knowledge hub. The engagement entry point sits in the Oracle practice; active renewals route to the renewal programme. The senior advisor sits at contact.
A senior Admodum Oracle advisor will read your applications portfolio against your Fusion conversation on a private call. Renewals route to the Renewal Programme; active audits route to the Audit Defence programme.