The PULA Trap: Why "Unlimited" Is Anything But

A Perpetual Unlimited License Agreement grants an organisation the right to deploy a defined set of Oracle products without per-unit licence counting. Oracle markets PULAs as the solution to licence compliance anxiety — a flat commercial relationship that replaces the complexity of processor and named user counting with a single annual support fee. For a period, usually the first three to five years, that narrative holds.

What Oracle does not make prominent is the long-term cost structure. PULA support fees escalate at 3–4% annually with no ceiling. There is no renegotiation clause, no natural renewal point from which the organisation can fundamentally restructure the commercial relationship, and Oracle has contractual authority to reject any proposed exit. Organisations that signed a PULA in 2016 and accepted Oracle's standard terms are now paying support fees 40–50% higher in real terms than at signing — with no reduction in usage that justifies the increase.

"The PULA eliminates licence counting anxiety and replaces it with something Oracle considers more valuable: a guaranteed, escalating revenue stream from which the customer has no contractual escape route."

What This Guide Covers

The Oracle PULA Exit Guide provides the commercial intelligence and strategic framework that organisations need to evaluate their PULA position honestly and, where appropriate, execute a structured exit. It draws on our direct experience advising enterprises through PULA renegotiations, cloud migrations used as exit vehicles, and support restructuring programmes.

  • The four structural exit strategies — cloud migration, negotiated conversion, support renegotiation, and term resetting — with an honest assessment of what each delivers and what each costs
  • How to model the true 10-year cost of staying in a PULA versus the cost of a structured exit, including settlement costs Oracle will demand
  • Oracle's seven documented tactics to prevent PULA exits — from inflated deployment counts to retroactive support demands — and how to neutralise each
  • The optimal exit window: why years 3–7 post-signing typically offer the best leverage, and why leverage declines sharply after year 10
  • How to use Oracle Cloud Infrastructure adoption as a genuine exit mechanism rather than a new form of lock-in
  • Negotiation scripts and commercial precedents from PULA exits where organisations recovered £4M–£8M in annual support obligations
  • Post-exit governance: how to prevent Oracle from reinstating equivalent obligations through product renewal or cloud service expansion

Considering a PULA exit or upcoming renewal?

We've advised on PULA restructuring engagements across multiple sectors — let us model your options.
Request a PULA Review →

Oracle's Exit Prevention Playbook

Oracle's account teams are experienced at preventing PULA exits and have a well-established playbook. Understanding the tactics in advance is essential to negotiating from a position of genuine strength rather than responding reactively to Oracle's moves.

The most common tactic is deployment count inflation. Oracle's team will assert that the organisation is running significantly more product deployments than it believes, increasing the notional value of any exit settlement and reducing the organisation's apparent leverage. A second tactic is backward-looking support demands: Oracle will calculate what support fees would have been charged on an individual-product basis during the PULA term and present this as a settlement obligation — despite the PULA contractually covering this period.

The guide provides a detailed counter-analysis framework for each tactic, allowing your legal and procurement teams to enter exit negotiations with a prepared, evidence-based position rather than accepting Oracle's opening numbers. Organisations that engage independent advisors at this stage consistently recover 20–40% more value from exit settlements than those that negotiate directly with Oracle without specialist support.

Who Should Download This Guide

This guide is written for CFOs, IT procurement directors, and Oracle relationship owners at organisations currently holding a PULA — particularly those approaching the five-year mark or later, where the cost-versus-value equation is most likely to have deteriorated. It is also relevant to organisations being presented with a new PULA as part of an Oracle renewal or cloud migration discussion, where the guide provides the counterweight analysis Oracle's commercial team will not provide. Download is free and instant.