Post-Divestiture Oracle Re-Papering: $12.2M Saved Across Parent and Divested Entity

The Situation: A Divestiture That Left Oracle on Both Sides of the Cut

A US industrial group divested a $1.1B revenue division to a strategic buyer. The transition services agreement was 12 months. The Oracle estate inside the divested division — Oracle Database EE, Oracle Fusion HCM, WebLogic Enterprise Edition, and a Java SE Universal Subscription line — had to be re-papered into a standalone Oracle contract on the carved-out entity's paper before the TSA cut-over. This is the kind of post-divestiture Oracle re-papering scenario where Oracle's account team holds maximum leverage: the buyer needs Oracle to run the business on day one of separation, and the seller cannot afford the deal to slip because of an Oracle contracting delay. Oracle's playbook is built for this moment.

The opening Oracle quote for the standalone agreement on the divested entity was $19.6M over five years, with a 0% migration credit, no BYOL portability, and a change-of-control clause that would have re-triggered on the next M&A event. Oracle's argument was that the divested entity was a "new customer," that the parent's existing Order Forms did not transfer, and that the Oracle ULA in force at the parent could not be apportioned. Each of those positions was challengeable. The combined buyer and seller engaged us — under a joint engagement letter — to re-paper the Oracle position on terms the divested entity could actually live with after separation.

Why Divestiture-Stage Oracle Negotiations Are Different

The Oracle re-papering window in a divestiture is short, the leverage is unbalanced, and the standard Oracle playbook is designed to extract a separation premium. The defendable buyer-side position turns on three things. First, the apportionment of the parent's existing Oracle entitlement — Oracle will argue it does not transfer; the OMA itself usually says otherwise once read forensically. Second, the carved-out entity's transitional support requirements — Oracle's standard "new customer" pricing assumes a clean-sheet rebuild; the buyer-side challenge is to anchor the new agreement on actual usage, not catalogue pricing. Third, the change-of-control language Oracle inserts into the standalone contract — left untouched, it makes the next divestiture (or sale of the divested entity) materially more expensive. We were brought in to defend all three.

Our Approach: Six Months, Three-Party Negotiation

1. Forensic Entitlement Apportionment

   The parent's Oracle ULA covered Database EE, RAC, Partitioning, Advanced Compression and Diagnostics Pack. The forensic deployment record showed the divested entity had been using 23% of the certified count at the time of separation. We argued — and Oracle accepted, after challenge — that the divested entity was entitled to apportion 23% of the parent's certified Oracle entitlement under the OMA's affiliate transfer language. That single negotiation removed $7.2M from Oracle's "new customer" quote.

2. Java SE Universal Subscription Re-Paper

   The Java SE Universal Subscription at the parent was on an Employee Metric of 14,200. The divested entity's defendable Employee Metric was 1,840. We re-papered the Java SE line on the divested entity's actual count, with an Oracle-acknowledged carve-out from the parent's subscription that protected the parent from being re-counted with the divested entity's employees during the TSA period.

3. Standalone Contract Re-Papering With Buyer-Side Clauses

   The new Oracle agreement at the divested entity removed the uncapped renewal escalator, removed the change-of-control trigger, added a 5% renewal cap, added a 24-month audit moratorium, and added explicit BYOL portability between AWS, Azure and OCI in three named regions. Oracle resisted each clause individually; the buyer-side leverage came from the TSA cut-over date, which gave us a hard deadline that Oracle's account team needed to hit as much as the buyer did.

4. Support Stream Separation

   The parent's single global Oracle support contract was split into two streams — parent and divested entity — with separate Customer Support Identifiers, separate renewal cycles, and separate support pricing. The divested entity inherited a 22% support stream against the apportioned entitlement; we benchmarked the support spend against comparable post-divestiture deals and negotiated a 14% reduction against Oracle's opening number.

5. TSA-Period Audit Protection

   The transitional support agreement period — 12 months — is when Oracle's LMS team typically opens audits against newly-separated entities, on the basis that the divestiture itself is a "change of use." We pre-empted the audit risk with a contractual audit moratorium covering the TSA window and the first 12 months post-separation, and with a forensic baseline deployment record that closed any residual back-licence claim before Oracle had grounds to open one.

The Results

The standalone Oracle agreement at the divested entity was signed eight weeks before the TSA cut-over. The parent's Oracle estate, post-apportionment, was re-papered as a smaller, defensible Term position with a 5% renewal cap. Both entities entered post-separation with documented forensic deployment records, audit moratoriums, and BYOL portability in writing. Total savings against Oracle's combined opening positions: $12.2M.

Key Takeaways for M&A and Carve-Out Teams