American Airlines: $12M off Oracle support over three years.

American Airlines cut Oracle support spend by $12 million over three years by terminating unused licenses, splitting the estate between Oracle and third party support, and pricing the repurchase risk before Oracle could.

What problem did American Airlines face with Oracle support?

American Airlines carried a multimillion dollar annual Oracle support bill across database, middleware, and applications, with a meaningful share attached to licenses no longer deployed. Support renewals arrived as one roll forward number, growing at the standard uplift, with no internal map of which CSI lines funded which running systems.

The airline industry context made the bill harder to defend. Cost programs after 2020 put every recurring line under review, and Oracle support was among the largest untouched items.

• Shelfware drag: support renewed annually on licenses parked after consolidation projects.
• No roadmap link: stable systems with no upgrade plans paid the same Premier rate as active platforms.
• Uplift compounding: the annual support increase applied to the whole line, including the unused share.

Why is Oracle support so hard to reduce piecemeal?

Oracle support pricing is anchored to the original license purchase, and Oracle lifetime support policies tie ongoing fees to keeping the full license set under contract. Terminating part of a CSI can trigger repricing of what remains, which is why naive line item cuts often save nothing.

How did the support optimization strategy actually work?

The program ran in three phases over roughly nine months: inventory and entitlement mapping, termination sequencing against repricing exposure, and a support model split between Oracle and third party providers. Each phase had its own gate, and nothing was terminated until the repurchase risk on that line was priced.

How was the termination order decided?

Lines were terminated in an order that kept discounted license sets intact, because Oracle's repricing rules recalculate support on the surviving licenses at lower discount tiers when sets are broken. The order came from modeling each termination against the Oracle price list rather than from the size of the line.

Where did third party support fit?

Stable systems with no planned Oracle upgrades moved to third party support at roughly half the Oracle rate. Systems on active roadmaps, where upgrades and patches from Oracle Premier Support carried real value, stayed on Oracle support deliberately.

What results did the program deliver?

The program removed $12 million of support cost over three years against the prior baseline, with the first full year delivering roughly a third of that. No production incident was attributed to the support model change across the measurement window.

• Year one: terminations and the first support split tranche landed roughly $4M of run rate reduction.
• Years two and three: the remaining estate split plus avoided uplift compounded the rest.
• Risk outcome: zero license repurchase demands, because terminations were sequenced and documented.

What did Oracle's response look like?

Oracle account pressure concentrated on audit signaling and cloud migration offers rather than support price relief, the standard response pattern under Oracle support policies. Holding documented entitlement records and a clean deployment map kept the audit conversation short.

What can other CIOs take from this case?

The transferable lesson is sequencing. Most enterprises can find the same three savings layers, but the order of operations decides whether the savings survive Oracle's repricing and audit responses.

1. Build the deployment to entitlement map before touching any renewal.
2. Price repurchase risk per line before terminating anything.
3. Sequence terminations to keep discounted license sets whole.
4. Split support by system roadmap, not by vendor loyalty.
5. Document the entitlement position as if an audit letter arrives tomorrow.

Does this work at smaller Oracle estates?

Yes, with smaller absolute numbers. The shelfware share and the roadmap mismatch exist at almost every estate over a few million dollars of annual Oracle support; the percentages in our engagement file hold from roughly $2M of support spend upward.

Where the common advice on Oracle support optimization is wrong

The standard advice says third party support is the savings engine and you should move everything stable at once. We disagree. In roughly 30 to 40 Oracle support engagements Fredrik Filipsson worked between 2024 and 2025, the larger and safer first dollar came from terminating support on unused licenses, sequenced against repricing clauses, before any support model change. Termination savings carry no service risk and no vendor switch, and they shrink the base the third party decision is later made on. The buyer side move is to clean the entitlement base first, then split support by roadmap. Moving a dirty estate to third party support just relocates the waste.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Pull every Oracle CSI and map each line to a running system or mark it unused.
2. Model repricing exposure before terminating any support line.
3. Classify each system by roadmap: active upgrade path or stable.
4. Price third party support for the stable tier and Oracle support for the active tier.
5. Sequence terminations to protect discounted license sets.
6. Set an annual support model review tied to the renewal calendar.

White Paper · Oracle

Control Oracle Spend: The 5 Year CIO Playbook

The buyer side playbook for the CIO who controls Oracle spend across audit, ULA, Database, Java, OCI, and renewal in one five year plan. Read it free.

Read the white paper

Frequently asked questions

How much did American Airlines save on Oracle support?

The program removed $12 million of Oracle support cost over three years. The savings came from terminating support on unused licenses, splitting support by system roadmap, and moving stable systems to third party support.

Is terminating Oracle support on unused licenses safe?

Yes, when sequenced correctly. Oracle repricing clauses can recalculate support on remaining licenses if discounted sets are broken, so each termination must be modeled against the contract before it is executed.

What is the typical unused share of an Oracle support bill?

In our 2024 to 2025 engagement file, support attached to licenses with zero recorded use ran 15 to 25 percent of the total Oracle support line before cleanup.

When does third party support make sense for Oracle estates?

Third party support fits systems with no planned Oracle upgrades, where stability matters more than new versions. Active roadmap systems usually justify staying on Oracle support.

Does cutting Oracle support trigger an audit?

It raises the probability of audit signaling, which is why the entitlement map and deployment records are built before any termination. A documented position keeps the audit conversation short.

Can smaller companies replicate this approach?

Yes. The shelfware share and roadmap mismatch percentages hold from roughly $2 million of annual Oracle support upward; only the absolute savings change.