Contents
Key takeawaysWhat happens to your licensesOptions for the old licensesDropping legacy supportThe support creditThe double runCosts outside the subscriptionWhat we have seenContract terms to ask forWhat to do nextFAQAn Oracle Fusion Cloud migration adds a subscription and retires nothing. Your old licenses and their support run on until you act, so the commercial work lies in the support credit, the overlap and the exit.
- No license retires itself. Your E-Business Suite or PeopleSoft licenses and their support continue alongside the new Fusion subscription until you decide otherwise.
- The support credit is negotiated. It was understated in 40 to 60 percent of the first proposals we saw, so build it from your paid renewal invoices.
- Partial exits disappoint. Matching service levels and repricing on reduction mean trimming support often returns far less than the invoice suggests.
- The overlap is the budget risk. Legacy support runs at full cost until the last entity cuts over, so a phased rollout pays for two systems for well over a year.
- The start date beats most discounts. Tie billing to first production use and activate quantities by wave.
- The old system outlives go live. Seven to ten years of statutory retention usually keeps a licensed read only copy running.
- No deadline forces your hand. Oracle has extended support for both E-Business Suite 12.2 and PeopleSoft, so the transition timetable is yours to set.
When you sign for Fusion, your E-Business Suite or PeopleSoft licenses stay valid, the support on them keeps renewing, and the new subscription sits on top of both until you decide otherwise.
Oracle sells the change as a migration. For your budget it is an addition, and the overlap period, more than the subscription price, is where most transition business cases go wrong. This guide covers what to do with the old licenses, how to price the support exit and which terms to settle before you sign.
What happens to your Oracle licenses when you migrate to Fusion Cloud?
Nothing happens to them automatically. Your perpetual licenses remain yours and remain valid under the agreement you signed them under. Oracle does not take them back, and it does not credit them against the subscription unless you negotiate that in writing.
- Perpetual licenses. The right to run what you bought, on the terms of the original ordering documents.
- Annual technical support. A separate stream on those licenses that you may keep, reduce or stop.
- The Fusion subscription. A new contract with its own metrics, its own term and a renewal price that tends to rise.
Each of the three changes on its own timetable. Signing the third does not settle the first two.
That last point is the most common transition mistake we see. There is no exchange rate between an E-Business Suite license and a Fusion subscription. What exists is a negotiation over what Oracle will give you for walking away from an annual support payment it collects today.
Why the operating model changes as well as the price
With perpetual licenses you own the software and pay predictable support to keep it patched. With Fusion you rent a service, and if you stop paying, the system stops. That shift matters for exit planning, for budget cycles and for how hard you push on the renewal terms of the first subscription.
How to Negotiate an Oracle OCI Deal: The Discount Is Set. The Deal Is Not.
What can you do with E-Business Suite or PeopleSoft licenses you no longer use?
You have four options, and they can differ by product. Most organizations mix them: support stays on whatever still transacts, and the rest goes dormant or shifts to a third party provider.
| Option | What it costs | What you keep | When it fits |
|---|---|---|---|
| Keep Oracle support running | Full annual fee, with the usual increase | Patches, updates and ticket rights | While any unit is still transacting |
| Move to third party support | Materially less, no Oracle patches | Break fix and tax updates from the provider | Long tail archive or slow rollout |
| Drop support, keep licenses | Nothing ongoing, high reinstatement risk | The perpetual right to run what you have | A frozen archive you will never patch |
| Terminate the licenses | Nothing, and it is irreversible | Only whatever Oracle credited you for it | Only as a priced concession in the new deal |
Why termination should be sold, never given away
Termination is the one option with no way back. It is also the only one on the list Oracle actively wants, which tells you it has a price. If Oracle asks for it, it belongs in the Fusion negotiation as a concession with a number attached, effective at your exit date rather than at signature.
Whatever you decide, get the dormant position confirmed in writing. You may need the old system again for a divested unit or a slow region. The record should say the perpetual licenses remain valid and on what terms support can return.
When does third party support fit a Fusion transition?
The case is unusually strong during a transition, because the provider only has to cover the tail of the rollout. We cover the providers, the contract points and the risks in the Oracle third party support guide, and PeopleSoft specifics in PeopleSoft support by a third party.
Is there a support deadline forcing you off E-Business Suite or PeopleSoft?
No. In March 2026 Oracle extended Premier Support for E-Business Suite 12.2 through at least 2037, one year beyond the 2036 date it had committed to before. The same month it extended its rolling ten year support commitment for PeopleSoft through at least 2037.
Confirm the dates for your exact releases in Oracle's Lifetime Support Policy. For most customers on current releases, though, the timetable is yours to set. The best commercial terms on the old licenses are available while Oracle still wants the new signature, and a deadline you invent for yourself gives that away.
What if your technology licenses sit under a ULA?
Sequence the certification against the migration. Certifying partway through, when some databases have been retired and the Fusion side has not yet replaced them, produces the worst possible count. The Oracle ULA guide explains how certification counts are taken and why timing matters.
Oracle Fusion SaaS Guide
Fusion metrics, legacy license options and the support credit, in one download.
Get the white paper →Does dropping Oracle support on the old applications save the full invoice?
Rarely. Two rules in Oracle's technical support policies mean the saving you model from a partial exit is seldom the saving you get. Read both before you cancel a single line.
- Matching service levels. Every license in a license set must sit at the same support level. A license set is all your licenses of one program, including its options, so you cannot support half your Purchasing users and leave the other half unsupported. To cut support on part of a set you have to terminate those licenses.
- Repricing after a reduction. When you terminate a subset of licenses on one order, Oracle reprices support on the remainder at current list support minus the applicable standard discount. The new fee cannot exceed what you paid before for the whole order, and cannot fall below what you paid before for the licenses you keep.
A worked example of a partial exit
Say one order covers 2,000 users of an E-Business Suite module and carries $400,000 a year in support. Wave one of the rollout takes half the users to Fusion, so you terminate 1,000 of them and expect to save $200,000. Assume list support minus the standard discount on the remaining 1,000 comes to $330,000.
| Scenario | Annual support after the change | Annual saving |
|---|---|---|
| Today, 2,000 users supported | $400,000 | None |
| Partial exit, as budgeted | $200,000 | $200,000 |
| Partial exit, after repricing | $330,000 | $70,000 |
| Full exit of the license set | $0 | $400,000 |
The repriced figure sits between the floor of $200,000 and the cap of $400,000, so the rules allow it. A partial exit is often worth far less than it looks and a full exit worth more. Model both before you choose a rollout sequence, because the sequence decides which one you end up with.
Reinstatement is priced back, with a penalty
If support lapses and you later want it back, Oracle charges a reinstatement fee of 150 percent of the last annual support fee, prorated back to the lapse date. The normal fee for the new period comes on top. In the example above, a 12 month lapse on the $400,000 order would cost $600,000 before any forward support.
The rule we apply in every transition is simple. Never lapse a support stream you might need again within two years. The guide to dropping Oracle support and reinstatement covers the edge cases.
Why we advise against trimming support wave by wave
The usual advice is to reduce legacy support gradually, cutting each ledger or country as it goes live on Fusion. We disagree. Matching service levels and repricing mean each small cut returns little, while every cut adds contract changes and reinstatement risk.
In practice legacy support stays at full cost throughout the overlap anyway. Treat the support exit as one event at the end of the program, with a fixed date. Spend your negotiating effort on the credit and the subscription start date instead.
How do you negotiate the Oracle support credit in a Fusion deal?
Build it from the documented annual support fee on the applications you are leaving, and put the invoices on the table. The credit is a negotiated number with no formula behind it, and it was understated in 40 to 60 percent of the first proposals we reviewed.
Be clear about what the credit is. It is Oracle paying to replace the annual support stream it is about to lose. It is not a valuation of your perpetual licenses, and it has nothing to do with Oracle Support Rewards.
Why Oracle Support Rewards does not help here
Support Rewards accrue on Oracle Cloud Infrastructure consumption, at 25 cents per dollar, or 33 cents for customers with an unlimited license agreement. They apply only to technology program support invoices, so they never touch an E-Business Suite or PeopleSoft support bill. The Oracle Support Rewards guide covers where they do pay off.
How to build the credit number
- Pull the last two renewal notices for every support identifier (CSI) that covers the applications you are leaving.
- List each product, its license quantity and its annual fee on one sheet.
- Total it, and reconcile the total to what accounts payable actually paid.
- Make that total the reference figure every conversation returns to, in writing.
In our files the credit rose when buyers produced the actual renewal invoices. Oracle's team can argue with an estimate, but it has little room to dispute fees its own invoices show you paid.
What the Oracle account team will say, and what to say back
| What you will hear | What to say back |
|---|---|
| "The support credit follows a standard calculation." | "Then send us the calculation in writing. Until then we are working from our documented fee, which is on this sheet." |
| "The discount only holds if the subscription starts at signature." | "Discount and start date are separate terms. Price it both ways and we will compare the totals over the term." |
| "Keep support on the old system as long as you need, and we will sort it out later." | "We want the dormant position and the terms for returning to support in this ordering document, while the Fusion deal is still open." |
| "Terminating the old licenses is a standard part of moving to Fusion." | "Termination is permanent. If Oracle wants it, it is a priced concession in this deal and takes effect on our exit date." |
| "Support Rewards will offset the transition cost." | "Our Fusion spend earns none, and rewards cannot be applied to applications support. That does not belong in this discussion." |
How long does the double run last on a Fusion migration, and how do you shorten it?
On a phased rollout it lasts 12 to 24 months, and it is the largest single surprise in transition budgets. Going live ledger by ledger or country by country means the last legal entity cuts over long after the first, and legacy support runs at full cost until it does.
| Period | Legacy support | Fusion subscription | What to negotiate |
|---|---|---|---|
| Months 1 to 6, build | 100 percent | Should be zero | Start date tied to first production use |
| Months 7 to 12, wave one live | 100 percent | Wave one quantities only | Activation by wave, not all on day one |
| Months 13 to 18, waves two and three | 100 percent | Rising toward full | Support credit weighted to this window |
| Month 19 onward | Archive only, or zero | Full | Clean exit from the whole support set |
Five terms that shorten the overlap
- Subscription start at first production use. Write the trigger into the ordering document: billing starts when the first module goes live.
- Quantities activated by wave. Pay only for the population actually live on Fusion.
- A shorter tail. Move the smallest and slowest entities first rather than last, so the final cutover is not held up by a region with 40 users.
- Credit weighted to the overlap. Put the support credit into the months when you carry both cost bases.
- A hard exit date. Set the date legacy support ends and plan the archive around it.
Negotiate the start date first. It is the cheapest concession Oracle can make and the one with the largest cash effect, worth more than most discount arguments, yet it rarely comes up before the paperwork is drafted. Each month billed before first production use pays for an empty tenancy.
The six subscription terms you cannot fix after signing are covered in the ERP Cloud negotiation playbook, and the metrics in the Cloud ERP pricing guide.
A worked example of the start date and the credit
Take a hypothetical program with legacy support of $1.2 million a year ($100,000 a month) and a full Fusion subscription of $1.8 million a year ($150,000 a month). Wave one goes live in month 7 with 30 percent of users, and 70 percent are live from month 13.
| Cost line | Subscription billed from signature | Billed from first use, activated by wave |
|---|---|---|
| Fusion, months 1 to 6 | $900,000 | $0 |
| Fusion, months 7 to 12 | $900,000 | $270,000 |
| Fusion, months 13 to 18 | $900,000 | $630,000 |
| Legacy support, months 1 to 18 | $1,800,000 | $1,800,000 |
| Total cash out | $4,500,000 | $2,700,000 |
Timing matters for the credit too. A $480,000 credit spread evenly across a five year term is $96,000 a year, so only $144,000 lands in the 18 months when you pay for both systems. Weighted into months 7 to 18, all of it arrives when cash is tightest, and the total Oracle pays does not change.
What does an Oracle Fusion Cloud migration cost outside the subscription?
Usually more than the subscription itself, and almost all of it sits in customization, integration and testing. Model five years rather than one. Implementation spend is front loaded, but change never stops, because Fusion takes quarterly updates that every extension has to survive.
Custom code does not migrate. Every extension, form personalization, custom report, workflow rule and interface needs its own decision: retire it, replace it with configuration, or rebuild it outside the application.
- Custom forms become configuration or an extension outside the core, retested every quarter.
- Custom reports are rebuilt one by one on the delivered tooling, and a mature E-Business Suite instance often has hundreds.
- Workflow and approval rules are reimplemented in the delivered engine, which amounts to a process redesign.
- Database level interfaces are rebuilt against the Fusion integration layer.
Compile that inventory before design starts. Teams that compile it afterward find the rebuild scope halfway through the build, when it can only be handled as a change request at the systems integrator's rates. For module level detail, see how the general ledger licensing shifts from EBS to Financials Cloud.
Why the old system outlives go live
Finance, tax and audit rules commonly require 7 to 10 years of transaction history, while a Fusion migration usually carries only a limited number of years of open items. So a read only copy of the old application has to live on. A running instance is a deployed instance, and it still consumes licenses, including the Oracle Database underneath it.
- Decide early whether history lives in Fusion, in a read only legacy instance or in a dedicated archive.
- Price the archive option including the people who know how to query it.
- Confirm the read only licensing position with Oracle in writing.
- Agree with audit and tax in advance what evidence they will accept.
The Fusion side of the contract, from metrics to renewal caps, is mapped in the Fusion SaaS renewal playbook.
What have we seen in recent Oracle Fusion transitions?
Across 20 to 30 transitions from E-Business Suite or PeopleSoft to Fusion that I worked on in 2024 and 2025, the old licenses were treated as an afterthought. Four patterns came back again and again.
- No owner. No one owned the legacy licenses once the program started, so support renewals kept paying themselves automatically.
- Late inventory. The customization inventory was compiled after design started, which is how integration rebuild became an unbudgeted change request.
- A copy that would not die. Teams that planned to switch the old system off within months of go live were still running a read only copy 3 years later, and no budget had been set aside for it.
- A low first offer. The support credit in Oracle's first proposal was below what the invoices supported, as described above.
The best terms on the old licenses are available only while Oracle still wants the new signature.
How to decide the position of each asset
| Asset | Position during the transition |
|---|---|
| E-Business Suite applications | Dormant after cutover, support optional, credit tied to the full documented fee |
| PeopleSoft modules | Supported until the final cutover |
| Oracle Database under the applications | Still licensed and often still needed, so planned as its own track |
| Middleware | Inventoried for what the remaining interfaces still use |
| Custom extensions | Scoped for rebuild before signing |
On premises exposure is technical, and you can fix it by changing the deployment. Subscription exposure is contractual, and you can fix it only by paying or negotiating. CIOs most often underestimate the second. If middleware stays in use during the migration, read our note on middleware audits during migration.
Which applications can lose support first?
Rank each application by how fast it degrades without patches. Payroll and statutory reporting degrade fastest, because legislative updates arrive on a statutory calendar, so they stay supported until the last day.
Core financials and analytics degrade slowest, which makes them the first candidates to drop. Drop a whole product at once, so the exit covers its full license set and escapes the repricing that trimming users wave by wave runs into.
Which contract terms should you ask for before you sign Fusion?
Settle the old licenses in the same paper as the new subscription. Once the Fusion order is signed, Oracle has little reason to revisit them.
- Billing trigger. Subscription fees start at first production use of the first module, defined in the ordering document.
- Ramped quantities. Activation schedules by wave, with dates and counts, so you are not billed for users still on the old system.
- Stated credit. The support credit as a dollar amount, the support identifiers it relates to, and a payment schedule weighted to the overlap.
- Dormant license confirmation. A letter confirming the perpetual licenses remain valid, including read only use for retention.
- Return to support. Agreed terms, ideally a waived or capped reinstatement fee, if a divested unit or slow region needs the old system back.
- Renewal cap. A limit on the Fusion price increase at the first renewal, since the subscription price only rises from there.
What to do next
- Day one. Name an owner for the legacy licenses and support, because unowned renewals pay themselves for the whole double run.
- Before the first proposal. Pull the last two renewal notices per support identifier, total the documented fee, and make it the reference figure for the credit.
- Before choosing a rollout sequence. Model a full support exit against a partial one, using the license set and repricing rules.
- During negotiation. Tie the subscription start to first production use, activate quantities by wave and weight the credit toward the overlap months.
- Before design starts. Compile the customization inventory and decide where statutory history will live.
- Before signing. Get the dormant license position, read only archive rights and support return terms in writing. Our Oracle practice can run the transition commercials with you.
Frequently asked questions
What happens to your Oracle perpetual licenses when you move to Fusion?
They stay exactly as they are. The licenses remain perpetual and valid, and their support keeps renewing unless you act. Any credit against the subscription has to be negotiated and written into the Fusion order, and any termination of the old licenses should be priced inside that same deal rather than offered as a courtesy.
Does dropping on premises Oracle support save the full invoice?
Rarely. Terminating part of an order reprices the licenses left on it, and matching service levels stop you supporting only part of a license set. The saving comes closest to the invoice when you exit a whole license set at once, which is why the timing of the exit matters more than its size.
How long does the double run overlap last on a Fusion transition?
Usually 12 to 24 months when you go live in waves. A single cutover shortens it, but it puts every entity's go live on one date, a risk many multi country programs will not take. Budget both cost bases for the whole window and treat any earlier legacy saving as upside.
How do you protect the Oracle support credit in a Fusion deal?
Put it in the same ordering document as the subscription. State the dollar amount, the support identifiers it relates to and the months in which it is paid. A credit promised in an email or a presentation is easy to dispute later, and it carries no weight once the Fusion order is signed.
Do you still need licenses for the old Oracle system after go live?
Yes, as long as any instance runs, even read only, and that includes the Oracle Database and middleware beneath it. Some buyers extract history into a separate archive so the instance can be shut down. That ends the license need, but audit and tax have to accept the archive as evidence first.
Is there a deadline forcing a move off E-Business Suite or PeopleSoft?
No. Oracle's support commitments for both run through at least 2037, so the timing is a commercial and operational choice. A transition planned without an artificial deadline leaves you room to set the start date, the credit and the legacy exit date on your terms.
Does Oracle Fusion Cloud spend earn Oracle Support Rewards?
No. Oracle lists Cloud Applications such as Fusion Cloud ERP as ineligible, since rewards accrue only on OCI consumption. Even rewards earned on OCI apply only to technology program support invoices, so they cannot reduce the applications support you keep paying on the old system during the overlap.