Moving Oracle E Business Suite or PeopleSoft to Fusion Cloud is a commercial reset, not just a technical one. The licensing model, the cost base, and the support credits all change. Plan the contract before the migration.
A move from Oracle E Business Suite or PeopleSoft to Fusion Cloud resets licensing, cost, and support. The buyer side job is to lock the commercial terms before the project starts.
Fusion Cloud is a subscription, which converts a one time license base into recurring revenue. Oracle also retires the cost of supporting old on premise releases. The Oracle Fusion ERP page frames the destination.
The pitch is modern features and lower maintenance. Both can be real. The commercial terms decide whether the move pays off for you.
Behind the pitch sits support economics. Oracle would rather bank a recurring subscription than renew shrinking maintenance on releases it plans to sunset. Reading that motive helps you value the credit it offers to move you.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Your annual on premise support spend can become a credit toward the Fusion subscription. Oracle calls this support reward or a similar program. The credit value is negotiable and often understated in the first proposal.
Document your current support spend precisely and require the credit to reflect it. Check the terms against the Oracle lifetime support policy.
What changes in the move to Fusion
| Dimension | On premise | Fusion Cloud |
|---|---|---|
| License | Perpetual | Subscription |
| Metric | Named users or processors | Hosted users or employees |
| Support | Annual maintenance | Included in subscription |
| Upgrades | Project based | Quarterly, mandatory |
Document every support line before you talk numbers. Pull your latest support renewal, list each product and its fee, and total it. That figure, not an Oracle estimate, is the floor for your credit.
The subscription is only part of the cost. Implementation, data migration, integration, and ongoing change all add up, a point Oracle understates in its Fusion ERP applications overview. Model the full multi year cost, not the first year headline.
Build the case over five years, not one. The subscription recurs, implementation is front loaded, and change never stops. A one year view flatters the cloud and hides the renewal exposure that arrives later.
Fusion prices by hosted users and module. Map your real user population to the right tiers, and confirm the metric definitions in the Oracle Applications documentation before you sign.
Anchor your model to published list. Oracle's Fusion Cloud Service global price list shows metrics like Hosted Named User near 625 dollars per user per month for Procurement, and Hosted Employee at 8 dollars per month for HCM Base. Your discount off list is the real negotiation.
There is no automatic swap. Oracle retires nothing on your perpetual licenses and sells you a fresh Fusion subscription instead. Any credit for the support you stop paying is a separate, negotiated line.
Your E Business Suite and PeopleSoft licenses stay on the shelf after cutover. You can keep them dormant, keep paying support, or let the stream lapse. The subscription is a new contract with its own metric and term.
That separation is the leverage point. Because the two contracts are distinct, the value of any credit is a negotiation, not a formula. Treat the perpetual estate as a bargaining asset you are choosing to surrender.
Anchor the credit to your documented annual support fee, not to a percentage Oracle proposes first. The full maintenance number on the EBS and PeopleSoft estate is the reference point every conversation should return to.
Do not confuse this credit with Oracle Support Rewards, which returns 25 percent of OCI consumption against technology support and 33 percent for Unlimited License Agreement customers. That program touches database and middleware support, not the applications subscription.
| Perpetual asset | Position after go live | Oracle usual offer | Buyer side move |
|---|---|---|---|
| E Business Suite applications | Dormant, support optional | Subscription credit vs support spend | Tie credit to full documented fee |
| PeopleSoft modules | Dormant, support optional | Trade in against Fusion HCM | Keep support live until go live |
| Oracle Database under the apps | Still licensed and needed | Move to OCI, earn Support Rewards | Plan the database as its own track |
| Custom extensions | Not portable to Fusion | Rebuild as extensions or PaaS | Scope rebuild cost before signing |
Get the dormant license position in writing. If you might reactivate EBS for a divested unit or a slow region, confirm the perpetual licenses remain valid and that support can be reinstated on defined terms.
You stop paying maintenance, and you also stop receiving patches, tax and regulatory updates, and the right to open technology tickets on that estate. Model that loss before you cancel anything.
The good news is there is no support cliff forcing your hand. E Business Suite 12.2 carries Premier Support through at least 2036, per the Oracle support extension notice. PeopleSoft holds a rolling ten year support commitment.
That runway is quiet leverage. Because no deadline is pushing you off on premise, you can migrate on your own schedule and keep the credit conversation calm rather than rushed by a renewal date.
Cancel support only when the workload is fully live on Fusion. Early cancellation forfeits patches you may still need if the cutover slips a quarter. Keep the stream until the last user has moved.
Reinstating a lapsed stream is costly. Oracle can charge back the skipped fees plus a reinstatement penalty to restore support. Never lapse a stream you might need to revive if the project stalls.
Third party support is a middle path. If you want to stop paying Oracle maintenance before Fusion is live, a third party provider can keep the estate patched during the migration window.
Weigh the regulatory risk by module. Payroll and tax engines need frequent legislative updates, so losing patches there bites first. Rank your estate by update sensitivity before you choose what to drop and when.
Usually yes, for a defined window. While the old system runs in parallel with Fusion, you carry on premise support and the new subscription at once. Budget the overlap as a real line, not a rounding error.
The overlap is the hidden cost of a phased rollout. A ledger by ledger or region by region migration can run twelve to twenty four months, and support does not stop until the final unit cuts over.
Every month between signature and first production use is subscription you bought and did not use. Align the start date to go live, not to signing.
Negotiate a ramped subscription so you pay for Fusion capacity as you activate it, not all of it on day one. Oracle resists this, yet staged activation is a standard concession on large transitions.
Ask for the subscription start date to align with the go live of the first production module, not contract signature. Every idle month between signing and first use is money spent on nothing.
Map the overlap month by month. A schedule showing when each module goes live, and when its old support can stop, turns a vague fear of double paying into a bounded, negotiable number.
Four levers move real money: subscription discount depth, the support credit, ramped billing, and a renewal uplift cap. All four are available at first signature and rarely afterward.
Oracle runs cloud migration offers that bundle credits and implementation funding. Program names change often, so write any incentive into the ordering document rather than trusting a brochure or a verbal promise from the account team.
| Incentive | What Oracle offers | Buyer side counter |
|---|---|---|
| Subscription discount | Percentage off list price | Hold discount across the full term |
| Support credit | Credit vs current maintenance | Anchor to full documented spend |
| Ramped billing | Rare unless requested | Pay as modules go live |
| Renewal uplift cap | Often omitted | Cap tied to a published index |
| Implementation funding | Credit toward Oracle Consulting | Prefer cash discount, keep freedom |
Treat professional services credits with care. A large implementation credit that must be spent with Oracle Consulting can steer scope you never wanted. A clean discount on the subscription is worth more than a restricted credit.
Timing is its own incentive. Oracle discounts deepen near quarter and fiscal year end, when the account team needs the booking. Align your signature with that pressure rather than against it.
Put every incentive in the ordering document. A credit promised in a slide has no contractual weight, and account teams rotate. If it is not in the signed order, assume it does not exist.
Plan eighteen to thirty months for a full EBS or PeopleSoft move, with a licensing checkpoint at every phase. The commercial work comes first, before any technical design begins.
Compressing this timeline is where cost leaks. Rushing the commercial reset to hit a project date is how buyers sign without a renewal cap or an accurate credit. Sequence the contract ahead of the build.
Put a checkpoint at contract signature, at first go live, at the end of the dual run, and at first renewal. Each is a moment where a metric, a credit, or an uplift can be locked or lost.
| Phase | Typical duration | Licensing checkpoint |
|---|---|---|
| Commercial reset | Before the project | Credit, discount, renewal cap |
| Design and build | 6 to 12 months | Confirm module and user scope |
| Parallel dual run | 3 to 9 months | Manage double support overlap |
| Cutover and go live | 1 to 3 months | Start subscription, plan support exit |
| Post go live | Ongoing | Renewal cap and true up review |
Hold a licensing review before each phase gate. The renewal checkpoint matters most, because an uncapped subscription can reset toward list once the migration momentum is gone and switching looks hard.
Name an owner for the licensing track. Migrations are run by delivery leads focused on go live dates, so the commercial checkpoints slip unless one person is accountable for the contract at every gate.
Two traps recur. Lifting old processes into the cloud unchanged, and signing a subscription with no renewal cap. Both carry old cost and old risk into the new model.
A third trap is scope creep during design. Every module added mid project is a new subscription line at weak leverage. Freeze scope in the contract and treat additions as formal change requests, priced up front.
Negotiate a renewal uplift cap in the first contract. Without it, the subscription resets at list at renewal. Tie any increase to a published index and bound it in writing.
The common advice is to lift and shift Oracle E Business Suite or PeopleSoft into Fusion quickly to capture cloud savings. We disagree. In roughly 20 to 30 Fusion transitions we advised, lift and shift carried old customizations and old cost into the subscription, and true cost ran 1.5 to 2.5 times the headline once change effort was counted. The buyer side move is to lock the support credit, model the full multi year cost, and cap the renewal uplift before the project starts, then redesign processes rather than replicate them. The migration is a commercial reset, and the best terms are available only before you commit.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The move to Fusion is a commercial reset before it is a technical one. The best terms are on the table before the project starts, not at the first renewal.
Fusion Cloud is a subscription, which turns a one time license base into recurring revenue and retires the cost of supporting old on premise releases. Modern features are real, but the commercial terms decide the value.
Yes. Your annual support spend can become a credit toward the Fusion subscription. The credit value is negotiable and is often understated in the first proposal, so document your spend precisely.
More than the subscription. Implementation, data migration, integration, and ongoing change push true cost to 1.5 to 2.5 times the headline in our reviews. Model the full multi year figure.
No. Lifting old processes unchanged carries old cost and old risk into the subscription. Redesign for Fusion rather than replicate, or the move underdelivers.
By hosted users and module. Map your real user population to the correct tiers and confirm the metric definitions in the Oracle documentation before signing.
Negotiate a renewal uplift cap in the first contract, tied to a published index. Without it, the subscription can reset at list at renewal.
Plan it separately. The database often has its own licensing and cost profile that the applications move does not resolve on its own.
Before the project starts. The migration is a commercial reset, and the strongest terms, including the credit and the renewal cap, are available only at the first signature.
It offsets technology support, not the Fusion subscription. Support Rewards returns 25 percent of OCI spend, or 33 percent for Unlimited License Agreement customers, as credit against database and middleware support bills.
No. E Business Suite 12.2 has Premier Support through at least 2036 and PeopleSoft holds a rolling ten year commitment. You can migrate on your own timeline without a support cliff.
Oracle ULA exit moves, support credit protection, and the buyer side moves across the Oracle Database, applications, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Engage independent buyer side Oracle advisors. We do not resell. We sit on your side of the table.
Open the Oracle Practice page
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →