Work through all 20 items. Mark each as compliant (✓), non-compliant (✗), or unknown (?). Unknown items should be treated as gaps. If you identify HIGH-risk items, download our Oracle Audit Defence Kit and engage an independent specialist before taking any action.
Section 1
Understanding Your PULA Scope and Cost
01
You have confirmed the exact products and product versions covered under your PULA — including any exclusions or geographic limitations written into the agreement.
High
Expert note: PULA agreements are highly negotiated and product-specific. Many organisations operate under the assumption that a PULA covers their entire Oracle estate, only to discover during a certification event that specific product options, newer versions, or cloud deployments were excluded from the original scope. Obtain and review the full PULA order document — not just the summary — and map every Oracle product in your estate against the PULA-covered list before making any strategic decision about exit or continuation.
02
You have modelled the total 10-year cost of continuing the PULA (annual support fees + any incremental uplift) against the cost of a structured exit and conventional per-licence model.
High
Expert note: A PULA's perpetual nature means annual support fees accumulate indefinitely. At Oracle's standard 22% annual support rate with 3–5% annual uplifts, a PULA with an original licence value of £5 million generates over £1 million per year in support costs that never end unless the PULA is terminated. Model the 10-year NPV of continuation versus exit — factoring in reinstatement risk, potential Oracle pricing on exit, and the savings achievable through licence right-sizing — before committing to any decision.
03
You understand that under a PULA there is no formal certification event: the agreement continues unless either party terminates — and termination triggers a usage-count obligation.
High
Expert note: Unlike a standard ULA (which has a defined 2–3 year term and certification date), a PULA runs indefinitely. This perpetual nature creates a dangerous false sense of security: organisations assume they have unlimited deployment rights forever without managing compliance. In reality, Oracle's right to audit continues throughout the PULA term, and any termination — whether by the customer or triggered by a breach — immediately converts unlimited rights into certified fixed quantities. Understand your termination obligations before making any infrastructure change.
04
You have assessed whether your Oracle deployments have grown, stabilised, or are declining — since growth trajectories directly determine whether PULA continuation or exit is financially advantageous.
Medium
Expert note: A PULA delivers maximum value when Oracle deployment is growing rapidly, because unlimited deployment rights absorb all growth without incremental licence cost. When growth flattens or declines — as often happens post-cloud migration or after consolidation projects — the PULA continues to cost the same in annual support fees, delivering diminishing value. Model your expected Oracle footprint at a 1-year, 3-year, and 5-year horizon to determine whether the PULA remains the most cost-efficient structure.
05
You have identified all Oracle deployments that would NOT count toward PULA certification quantities — including VMware deployments in non-compliant configurations and cloud deployments on unauthorised platforms.
High
Expert note: This is the most dangerous PULA compliance trap. When a PULA terminates, Oracle certifies your usage by counting deployments that meet the PULA agreement's certification criteria. Deployments on VMware in non-hard-partition configurations, on cloud providers not listed in your PULA agreement, or using product versions not covered by the PULA will not count — leaving you with an unlicensed gap at the moment of termination. Audit every deployment against PULA certification criteria now, not at the point of termination.
PULA renewal or exit decision approaching?
Independent financial modelling and negotiation support. No Oracle affiliation.
Section 2
Exit Readiness and Certification Planning
06
If considering PULA exit (certification), you have prepared a comprehensive deployment census that accounts for every qualifying installation across all environments — production, non-production, and disaster recovery.
High
Expert note: PULA certification requires reporting every deployment that counts toward the certified quantity. Organisations typically undercount by excluding DR environments, legacy test systems, and recently commissioned deployments. Oracle will audit the certified quantity and can assert that additional deployments existed at the time of certification, creating a post-exit licence obligation. Prepare the deployment census with forensic accuracy — using Oracle's collection tools to generate the same data Oracle would collect — before committing to an exit date.
07
You have begun PULA exit planning at least 18–24 months before the intended termination date to allow time for deployment remediation, negotiation, and documentation.
High
Expert note: PULA exits are complex commercial negotiations. Oracle will typically attempt to maximise the certified quantity (and therefore the post-exit licence value and associated support fees) while the customer aims to minimise it. This negotiation is far more effective when the customer has had 18–24 months to remediate non-qualifying deployments, decommission unused systems, and prepare a defensible deployment census. Last-minute exit attempts — driven by cost pressure rather than strategic planning — almost always result in over-certification and poor commercial outcomes.
08
You have evaluated whether renewing the PULA on more favourable terms is preferable to exit — particularly if Oracle is willing to reduce the annual support fee or convert to an OCI commitment structure.
Medium
Expert note: Organisations sometimes assume exit is the only path to cost reduction, when PULA renewal on improved terms may be achievable. Oracle is increasingly willing to convert PULA support commitments into Oracle Cloud Infrastructure (OCI) credits, effectively transferring the support spend into a cloud consumption model. Depending on your OCI roadmap, this may deliver more flexibility than a conventional PULA exit. Explore both paths simultaneously and use competitive benchmarking data to anchor the renewal negotiation.
09
Your legal team has reviewed the termination provisions in your PULA — including any notice periods, minimum deployment count obligations, and post-termination audit rights — before any exit communication is made to Oracle.
High
Expert note: PULA termination clauses vary significantly by agreement vintage and negotiated terms. Some PULAs include minimum certified quantity floors that prevent the customer from certifying below a pre-agreed number of licences. Others include Oracle's right to audit for up to 36 months post-termination. If you send Oracle a termination notice without understanding these provisions, you may trigger obligations you cannot meet. Legal review of the PULA contract — by someone with Oracle licensing expertise — is mandatory before any exit conversation begins.
10
You have modelled the post-exit Oracle licence position: the number and type of licences that would be certified at exit, the resulting annual support cost, and whether that support cost is lower or higher than your current PULA support fees.
High
Expert note: Many PULA exits produce a disappointing financial outcome because the certified licence count — once Oracle has reviewed all qualifying deployments — generates a support obligation only marginally lower than the original PULA fee, while the customer loses unlimited deployment rights. Model the expected certified count conservatively (assume Oracle's maximalist interpretation), calculate the resulting support cost, and compare it to current PULA fees. If the post-exit support cost is within 20% of the PULA fee, exit economics are weak and renewal may be preferable.
Section 3
Renewal Strategy and Commercial Leverage
11
You have assessed the competitive leverage available at PULA renewal — including cloud migration plans, third-party support options, and competing vendor proposals — to improve your negotiating position.
Medium
Expert note: Oracle's PULA renewal negotiation is a commercial event where leverage determines outcome. The strongest lever is a credible alternative: a cloud migration roadmap that reduces Oracle dependency, a TPS evaluation, or a competing ERP/database proposal. Oracle will respond to demonstrated willingness to reduce or exit the Oracle estate with greater commercial flexibility than it would offer to an organisation that appears locked in. Develop and communicate a genuine 'walk away' scenario before entering any PULA renewal discussion.
12
You have considered the impact of cloud migration on your PULA value — specifically, whether migrating Oracle workloads to Oracle Cloud Infrastructure (OCI) under BYOL converts PULA deployments in a way that is commercially advantageous.
Medium
Expert note: Migrating PULA-covered workloads to OCI under BYOL can be structured to count toward PULA certification quantities in some agreement structures — effectively consuming the PULA entitlement in the cloud. If your PULA agreement allows cloud deployment and you have an OCI strategy, this approach can provide a defined pathway out of the PULA while funding cloud migration costs from the PULA's unlimited deployment rights. Confirm the specifics with your PULA agreement and independent specialist advice.
13
Non-PULA Oracle products deployed alongside PULA-covered products have been separately accounted for and are not incorrectly assumed to be covered by the PULA's unlimited deployment rights.
High
Expert note: The number one compliance error in PULA estates is deploying non-covered Oracle products under the assumption that the PULA's unlimited rights extend to those products. Oracle will identify non-PULA products during any audit and treat them as separately licenced — potentially unlicensed if no conventional licences exist. Maintain a clear separation in your licence management system between PULA-covered products and those that require conventional licences, and audit this boundary quarterly.
14
You have an independent Oracle licensing specialist engaged — separate from Oracle account management and your Oracle reseller — to provide a neutral PULA vs exit analysis.
High
Expert note: Oracle's account team will recommend PULA renewal; your reseller earns commission on Oracle revenue. Neither party provides independent advice on whether the PULA structure is in your interest. An independent Oracle licensing specialist who operates exclusively on the buyer side can model the full financial implications of exit versus renewal, identify deployments that affect certification, and represent your interests in the commercial negotiation. At Redress, we have managed PULA certification and renewal events across multiple industries and consistently achieve outcomes that self-managed negotiations do not.
Section 4
Ongoing Governance and Post-Decision Planning
15
You have confirmed whether your PULA includes a 'most favoured customer' clause or pricing cap that limits Oracle's ability to increase annual support fees year on year.
Medium
Expert note: Some PULA agreements — particularly those negotiated before 2018 — include provisions limiting annual support fee increases or tying them to specific indices. These provisions are commercially valuable and may not survive a PULA renewal negotiation. If your current PULA contains such protections, quantify their value before deciding to exit: the savings from avoiding Oracle's standard 3–5% annual uplift over a 10-year horizon may outweigh the operational benefits of exiting.
16
Oracle product deployments in your estate have been reviewed for the use of product options and packs that are not covered by the PULA — as these require separate conventional licences.
High
Expert note: Oracle product options (such as Database Partitioning, Advanced Security, Diagnostic Pack, and Tuning Pack) are commonly deployed by DBAs without awareness of the licensing implications. If these options are not explicitly covered by your PULA, they represent separately licenced products. Oracle's LMS scripts specifically detect enabled options and packs. Conduct a technical review of every Oracle Database instance to identify which options are enabled and confirm they are within PULA scope — or disable them before an audit.
17
Your PULA governance includes a quarterly deployment review that tracks whether new Oracle deployments qualify for PULA coverage and whether existing deployments remain within PULA scope.
Medium
Expert note: PULA compliance is dynamic — every new server commission, virtualisation change, or cloud deployment potentially affects the PULA coverage boundary. Without regular governance reviews, non-qualifying deployments can accumulate over months or years without detection. Establish a quarterly review that confirms all Oracle deployments against current PULA criteria, flags any changes, and documents the basis for coverage decisions. This documentation is your primary defence if Oracle challenges your PULA compliance.
18
You have evaluated the financial impact of third-party support as an alternative to Oracle Premier Support on any certified licences post-PULA exit.
Medium
Expert note: If you exit a PULA and certify a conventional licence position, the resulting annual support fees can be significantly reduced by transitioning to third-party support at 50% of Oracle's rate. Factor this potential saving into your exit model: post-exit conventional licences on TPS may deliver a total cost of ownership meaningfully lower than the PULA continuation cost. Confirm TPS eligibility for the specific products and versions that would be certified before including this saving in your financial model.
19
You understand that Oracle's right to audit continues during the PULA term and have confirmed that your current deployments are compliant with the PULA's terms — particularly around authorised cloud environments and partitioning.
High
Expert note: The PULA does not provide blanket protection against Oracle audits. Oracle can and does audit PULA customers to verify that deployments are using covered products in covered environments. A PULA deployment on a cloud provider not listed in the agreement, or using a product not covered by the PULA, creates an audit-finding risk even during the active PULA term. Maintain PULA compliance documentation as rigorously as you would for a conventional licence estate.
20
You have established a formal PULA strategy team — including IT, finance, legal, and an independent Oracle specialist — that meets at least annually to review the PULA's strategic value and progress toward any exit or renewal decision.
Medium
Expert note: PULA decisions are multi-year commercial and technical programmes, not single events. Organisations that manage PULAs effectively treat the PULA governance as an ongoing function rather than a crisis response triggered by an Oracle communication. A formal annual review — with defined financial models, deployment census updates, and a clear decision framework — ensures that when Oracle approaches for a renewal discussion, you have the data and leverage to negotiate on your own terms rather than Oracle's timeline.
"Every PULA exit we have managed reveals the same pattern: organisations underestimate the deployment count, overestimate the leverage, and enter negotiations unprepared. The outcome is determined 18 months before the termination date — not at the negotiating table." — Morten Andersen, Redress Compliance
Interpreting Your Assessment Score
Count fully compliant items. Unknown answers should be treated as gaps for scoring purposes.
17–20
Strong Position
Controls mature. Schedule annual review to maintain as your estate evolves.
12–16
Moderate Exposure
Material gaps identified. Prioritise HIGH-risk items immediately and commission an independent review within 90 days.
0–11
High Exposure
Significant risk present. Do not engage Oracle commercially until independent specialists have assessed your position. Contact Redress immediately.
The PULA Decision in 2026: Exit, Renew, or Transform
Oracle PULAs were designed to lock enterprise customers into long-term support fee obligations in exchange for deployment flexibility. In 2026, that calculus has shifted: cloud migration reduces Oracle on-premises deployments, OCI provides an alternative consumption model, and third-party support provides cost relief post-exit. The organisations that achieve the best PULA outcomes are those that plan their exit or renewal strategy years in advance — building the deployment census, modelling the financial outcomes, and developing genuine commercial leverage before Oracle initiates the renewal conversation.
At Redress Compliance, we have managed PULA certification and renewal events across financial services, manufacturing, retail, and energy sectors. The single most important factor in achieving a good outcome is starting the process early — ideally 18–24 months before the intended termination date. If your PULA is within that window, contact us now to begin the independent assessment.