Oracle support renewal checklist. The uplift, the notice window and the clauses that set the fee.

The Oracle support renewal letter is a default, usually at 8 percent, and it executes unless you respond before the notice window closes. The saving comes from scope, contract wording and a costed alternative, in that order.

How much does Oracle raise support fees at renewal?

The renewal letter almost always quotes 8 percent. Oracle support renewal quotes sit in a 4 to 8 percent uplift band, and in the renewals we benchmarked in 2024 and 2025 the letter used the top of that band more than nine times out of ten.

Nothing in Oracle's process asks the renewal team to start lower. The letter is a default that executes on the anniversary unless you respond, so the first figure you see is the one you pay if you stay silent.

What does the uplift compound to over three years?

The percentage matters less than what it compounds to. Three annual uplifts on the same base put the default and a capped renewal far apart, and most budgets never model the gap. The table works from $1M of current annual support.

On the 8 percent path the fee reaches 126 percent of today after three uplifts. A cap written at 0 to 3 percent keeps the same base between 100 and 109 percent. That difference comes from one sentence in the ordering document, and no license changes hands to get it.

When does the Oracle support notice window close?

It closes before the anniversary, at 45, 60 or 90 days depending on the contract. The notice window is the deadline for dropping or changing support, and it is the date that matters most in the whole cycle.

Miss it and the agreement auto renews at last year's fee plus the standard uplift. After that there is nothing left to negotiate, because the renewal you wanted to change has already executed.

• Read the notice period in every support contract you hold. Windows of 45, 60 and 90 days often sit side by side in one company's contracts, so a single date for all of them is wrong.
• Put each deadline on the legal calendar. A procurement spreadsheet that is opened once a year does not protect a notice date.
• File a protective change notice when talks may run past the window. It keeps your options open while the commercial conversation continues.
• Plan backward from May 31. Oracle's fiscal year closes that day, and it is the one date in the year when Oracle wants the deal more than you do.

How do you time the renewal against Oracle's fiscal year?

Aim to have your position ready in March and April, so the decision point falls in Oracle's fourth quarter. If your anniversary sits far from May 31, you can still use the date by asking for co term and a price hold on a consolidated renewal that closes before it.

What have we seen across 60 to 80 Oracle support renewals?

The default did the pricing in almost every renewal we saw. Across the 60 to 80 Oracle support renewals I benchmarked between 2024 and 2025, the negotiation began only when the customer raised it.

A structured cycle took 20 to 30 percent off the annual run rate, and every license stayed in place. People expect a support saving to mean giving something up. In these renewals it came from three places: scope, contract wording, and a costed alternative that made the incumbent price justify itself.

Why does scope come first?

Scope is the largest saving and the least contested one. Inactive bundle modules made up 18 to 32 percent of what the customers we reviewed were paying support on. Removing them changes the base that every later percentage applies to.

A discount agreed before the cleanup is a discount on modules no one uses.

Why chasing a bigger discount is the wrong first request

The usual advice is to push the account team for a larger discount on the renewal quote. We think that is the wrong opening. A discount on the same paper leaves the inactive modules in the base and the 8 percent uplift running on top of them.

It also keeps the repricing terms that block later reductions. In our renewals the money came from changing the base and the wording first. Ask for the discount last, on a smaller and capped base.

Is leaving Oracle support the cheaper option?

Usually not. In 55 to 70 percent of cases the clean walk away was not the cheapest path, once reinstatement was priced at the policy rate on the last annual fee the customer actually paid, as set out under the forgotten clauses below.

The exit still does commercial work. A costed third party scoping on named workloads is what moved the uplift cap, so the value is in holding the option. Compare providers in our guide to Oracle third party support, and see the wider picture in Oracle support costs in 2026.

Which Oracle support contract clauses decide whether you can cut the bill?

The license set definition, the repricing rule, the support policy version and, for ULA customers, the certification count decide more than the uplift does. All four are settled before the renewal letter arrives, so read them in your ordering documents and in the Oracle Software Technical Support Policies before you plan any reduction.

The license set is the unit you can reduce

A license set is every license you hold of one program, with its options, packs and related modules. Matching service levels apply to the set, so every license in it carries the same support level. One support identifier often holds several sets, and one set can span several orders.

You cannot keep part of a set unsupported. To reduce it you terminate those licenses outright, and Oracle will ask you to sign a license termination letter. How the original orders were drawn then decides what the reduction costs, because repricing works order by order.

Repricing on reduction is what blocks the saving

When you terminate part of a set, Oracle reprices support on the remaining licenses on that order at list support price minus the standard discount. The new fee cannot exceed what you paid before for the whole order, including the licenses you drop. It also cannot fall below what you already paid for the licenses you keep.

On an order bought at a deep discount, that repricing eats most of the saving. This is how a 40 percent cut in scope arrives as a 10 percent saving in cash, and why you negotiate the reduction right and the repricing wording together.

Which version of the support policies applies?

By default, the version in force when the service is delivered. Standard Oracle license agreements provide support under the technical support policies in effect at the time the services are provided, so Oracle can revise them between renewals.

Two limits protect you. Support is delivered under the terms of your order, and a policy change may not materially reduce the service during a paid period. Where your ordering documents fix terms that a newer policy contradicts, reject a renewal letter that imports the newer wording. Our note on support policy incorporation by reference covers the drafting.

ULA support is priced from the certification count

Where products sit under an Unlimited License Agreement, the support fee after exit derives from what you certify. The total usually carries over and is spread across the certified licenses.

The certified count therefore sets the per license support price that any later reduction is repriced from. That makes the support negotiation part of your ULA certification plan, on the same timetable.

The clauses that get forgotten

• Sustaining Support. It is where a release lands at the end of its lifecycle, and the fee does not fall. It excludes new program updates, fixes, security alerts and Critical Patch Updates, so you pay the same for fewer rights.
• Reinstatement. The fee is 150 percent of the last annual fee you paid, prorated back to the lapse date, plus the fee for the new support period. It is not computed from list or from the original undiscounted price. See dropping Oracle support and reinstatement before you model any exit.
• Assignment and divestiture. The standard wording is written for Oracle. If a carve out is anywhere on the corporate plan, this clause is worth more than the uplift cap, as our guide to assignment in mergers and divestitures sets out.
• Co term and price hold. Ask for both wherever consolidating contracts works in your favor rather than Oracle's.

What will the Oracle account team say, and how should you answer?

Expect the same few lines in most renewals. Each one has a factual reply, and most of the replies come straight from the support policies or your own paper.

• "The uplift is standard and cannot change." The fee is a commercial term on an ordering document. Ask for a cap written into the renewal order, and point to any legacy 4 percent wording in your agreement.
• "If you drop those modules, the rest reprices and you save nothing." Ask for the repriced figure in writing, calculated under the policy's floor and ceiling, before you decide.
• "If you leave and come back, reinstatement will cost you far more than the renewal." Agree, and say the reinstatement charge is already in your model next to a costed third party quote.
• "The current support policies apply to every customer." Point to the terms of your order and to the rule that a policy change cannot materially reduce service in a paid period.
• "We can improve the number if you add cloud." Keep a new cloud commitment on its own order and its own business case, so the support cap is not traded for spend you did not plan.

What wording should you ask for in the renewal order?

Ask for terms that survive the whole term, attached to the fee you actually pay. A verbal promise from the account team does not bind the next renewal.

1. A cap of 3 percent or less, as a maximum for every year of the term. A cap stated for the coming year only resets at the next renewal.
2. The base defined as the fee paid in the prior term. A cap applied to list price or to an undiscounted figure does little.
3. A reduction right with capped repricing. State how the remaining licenses on the order will be priced if you terminate part of a set.
4. Co term and a price hold across the support contracts you consolidate, so one anniversary and one notice date govern them.
5. Assignment rights for affiliates and divested units, if any restructuring is possible during the term.
6. A confirmed notice period in days, written into the order, so there is no dispute about when the window closes.

How do you check what you are actually paying support on?

Start from Oracle's own records and your technical data, then compare them. The renewal quote shows what Oracle bills. Your systems show what you use.

• Support identifiers. List every support identifier in My Oracle Support and match each to its renewal quote lines.
• Ordering documents. Pull the original orders, since repricing on reduction works order by order.
• Database options and packs. Query DBA_FEATURE_USAGE_STATISTICS to see which options and management packs show real use.
• E-Business Suite modules. Compare licensed modules with the installed and active products in FND_PRODUCT_INSTALLATIONS and with actual transaction activity.
• ULA certification. Where a ULA has ended, reconcile the support fee against the certified quantities.

How does the approach differ for a small and a large Oracle customer?

A company paying a few hundred thousand dollars a year usually has one or two support identifiers and one notice date. The work is mostly the cap and the base, and it fits into a few weeks.

A company paying several million has dozens of orders, several notice windows and often a ULA history. There the license set and repricing analysis takes months, so it has to start a year out.

What should the Oracle support renewal timeline look like?

Start 12 months before the anniversary and plan every step against the notice date, since that is when the default locks in.

What to do next

1. This week. Pull the notice period from every support contract and put each 45, 60 and 90 day window on the legal calendar.
2. This month. List every bundle module and mark the inactive ones, since that correction changes every later percentage.
3. Before you talk price. Cost a third party scoping on named workloads, so your cap request has a priced alternative behind it.
4. In the renewal order. Write the cap at 0 to 3 percent as a maximum across the full term, applied to the fee actually paid in the prior term and never to list.
5. At signature. Close into Oracle's May 31 fiscal year end. Our negotiation practice runs the cycle with you and prices the alternative.

Frequently asked questions