M&A, divestiture, and reorganization under cloud agreements: what transfers, what does not, and negotiating ahead of the event. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session twenty eight of thirty. For twenty seven sessions we have treated your organization as a fixed thing: a workforce, an entity list, a set of contracts. Today the org chart moves. Mergers, acquisitions, divestitures, reorganizations, and the moment any of them happens, every entity clause you have been quietly accumulating since session sixteen wakes up simultaneously and asks to be read. Here is the shape of the problem, and it is unforgiving: a corporate event is the one moment when the vendor's leverage peaks and yours collapses, because you have a close date and they have a consent right. Today: the asymmetry and why events price like emergencies, the transfer map instrument by instrument, the divestiture and acquisition problems, and the three clauses that make all of it uneventful, bought in peacetime for approximately nothing. Let's move the org chart safely.
Five takeaways. One, the asymmetry: why corporate events are structurally the worst table you will ever sit at, and what that predicts about the pricing of anything agreed under one. Two, the transfer map: subscriptions, perpetual licenses, support sets, OCI commitments, hyperscaler commitments, what moves with a business, what stays behind, and what needs somebody's consent. Three, the divestiture: standing up a carved out business without buying it a second estate, and the transition service agreement that has to exist before it is needed. Four, the acquisition: two estates becoming one, the collisions, and the consolidation window that opens at announcement and closes when the integration finishes. And five, the pre event clauses: assignment rights, divestiture adjustment, acquisition bands, negotiated in years when nobody expects a transaction, which is exactly when they are free. One sentence for the whole session: corporate event terms are cheap in peacetime and priced as ransom in wartime, and nothing about the terms changes in between.
The asymmetry, and I want to be precise about why it exists, because it is structural rather than anybody's bad behavior. Fact one, deal timelines are absolute: a close date is a board commitment with bankers, regulators, and public disclosure attached to it, and against that, a licensing question that blocks day one operation gets solved at whatever it costs. Both sides know that before the first call. Fact two, consent is a veto: assignment restrictions mean the vendor's signature sits on the critical path of your transaction, and a gate that appears eight weeks before close, held by a party who benefits from your urgency, is not a negotiation, it is a toll booth with a friendly account director standing next to it. And the third fact, in the note, compounds both: mid event, the estate is opaque to its own deal team, nobody in the room can say quickly which entity holds which order, which support set covers what, or which definitions sweep the moving population, so, exactly as in session twenty six, the vendor's picture of your estate is better than yours precisely when the stakes are highest. Now the counter, which is the entire session: all three facts reverse if the clauses exist before the event. The terms themselves are identical. Only the calendar changed, and the calendar is worth millions.
The transfer map, five instruments, and the answer for every one of them begins with nothing moves automatically. SaaS subscriptions: bound to the ordering entity and its named affiliates, session nineteen's entity list, and assignment to anyone else usually requires consent, so check the entity list and the assignment clause first, always. Perpetual licenses: transferable only per the assignment terms, frequently consent gated, occasionally barred outright, and check the prior transfer history too, because an estate that has already been assigned once may have terms nobody remembers. Support sets: they follow the licenses, and here is the trap from session twenty, a partial move reprices what remains, so splitting a support set in a carve out can raise the cost of the half you kept. OCI commitments: committed spend stays with the contracting entity and balances rarely split cleanly, so the question to ask early is whether a buyer can consume against your pool at all, and usually the honest answer is no. And hyperscaler commitments: the same problem with other vendors' names on it, and remember from session twenty seven that marketplace routing depends on them, so an EDP that cannot follow a divested business takes the Database at economics with it. Five rows, one pattern: everything moves by clause, and every clause was negotiable years earlier at a price of about zero. First check makes that concrete.
First check. You are selling a division. The buyer expects the division's Fusion ERP subscriptions to come with it. Your order names your parent entity and its affiliates. The realistic position: A, the subscriptions transfer with the business, they are the division's software. B, nothing transfers by default: at close the division stops being an affiliate, so continued use is unlicensed, and moving the subscriptions needs Oracle's consent, priced against your close date unless an assignment clause already governs it. C, the buyer can keep using them during a transition period automatically. Or D, subscriptions always transfer, only perpetual licenses are restricted. Pause here. On the day the sale closes, what is the divested entity's relationship to your order's affiliate definition?
The answer is B, and it is session nineteen's sentence detonating. The entity list on the order is the population, and at close the divested entity stops being an affiliate of the contracting party, which means every user in that division falls outside the licensed scope on day one, and session twenty five's telemetry sees it happen in real time, because the accounts keep logging in from a company that is no longer your company. A hears ownership where the contract says scope, and it is the single most common assumption I encounter in deal rooms: the division has used this software for eight years, the division's budget paid for it, therefore it is theirs. It is not theirs. It is licensed to an entity, and that entity just changed. C invents an implied transition right, and this one matters practically: transition service arrangements for SaaS access are negotiated with the vendor explicitly, in writing, and they cost real money, so they belong in the deal model before signing rather than in a panicked discovery after it. D has the hierarchy backwards, subscriptions are generally tighter than perpetual licenses because there is no owned asset to argue about. And the whole answer hangs on one word: unless. Unless the clause already exists, you are negotiating consent against a close date, which is the worst table this entire course has described.
The divestiture problem, three parts that arrive together. Part one, day one operation: the carved out business needs working systems from the close date, and it has exactly two routes, ride your contracts under a transition service agreement that Oracle has actually agreed to, or sign its own subscriptions as a newly independent mid size company, on a bankers' timeline, which is the most expensive software any business ever buys, no volume, no history, no time, and a vendor who knows all three. Part two, your residual position, which almost nobody models: session nineteen's asymmetry, your workforce and user counts fall on close, your subscriptions do not, so without a divestiture adjustment clause you pay for the departed population until renewal, and if you just signed a five year term, that is years of paying for people who work for someone else now. Part three, the support ledger: moving or terminating part of the perpetual estate reprices what remains, session twenty's trap, and a carve out is precisely the event that splits license sets down the middle. And the sequencing that works, in the note, is the most valuable line on this slide: agree the transition terms and the residual adjustment as part of deal preparation, before the buyer is even known, while the transaction is confidential and your urgency is invisible. Our guest analyst did exactly that, years early, by accident of good habit. Tom.
Guest analyst I want to tell you about the cheapest clause I ever negotiated, and what it was worth four years later. A chemicals group, routine Fusion renewal, no transaction pending, nothing on the horizon. I put three corporate event terms on the ask list, as I always do: assignment rights with consent not to be unreasonably withheld, a divestiture adjustment allowing quantity reduction at the next anniversary after a qualifying disposal, and a transition service framework at defined rates. The account executive's reaction was almost bored. He asked whether we were planning something, we said no, we are planning for the possibility of something, and he took it to his desk and came back with all three, essentially free, because in a year with no deal in sight those clauses cost his quota nothing. Four years later that group divested two business units in eighteen months. Here is the difference those three sentences made. The carved out businesses rode the parent's Fusion under the pre agreed TSA framework for nine months each, at rates set in peacetime, so day one was a non event. The residual adjustment took about four thousand hosted employees out of the subscription at the following anniversary, which was roughly two point two million a year that would otherwise have been paid for people who had left the group. And the assignment right meant Oracle's consent was a process with a timeline, not a negotiation with a deadline, so licensing never once appeared on the deal's critical path. I have since watched a comparable group without those clauses pay a seven figure consent and transition package eight weeks before close, because they had no choice and everyone in the room knew it. Same software, same vendor, same event. The only difference was who had spent five minutes on it four years earlier.
Three sentences, conceded almost for free in a year with no deal in sight, worth two point two million a year in residual adjustment alone plus a licensing question that never touched the critical path. We are planning for the possibility of something. That is the whole ask. Second check, the other direction.
Check two, acquisitions. Your group acquires a competitor. Both run Fusion HCM: yours at nine thousand Hosted Employees, theirs at four thousand, separate orders, separate renewal dates, different clause sets. The governance move: A, run both contracts to term, nothing needs doing until they expire. B, treat the integration as a consolidation event: map both entity lists and definitions, keep both running until one platform is chosen, then co term into one order that takes the better clause set from each and prices thirteen thousand at group scale, timed to whichever renewal comes first. C, cancel the smaller contract immediately and add four thousand to yours. Or D, merge the workforces into your order and let Oracle true up later. Pause here. Which of session twenty seven's disciplines does an acquisition hand you for free, exactly once?
The answer is B, and the gift the acquisition hands you is consolidation, free and briefly: two orders, two clause sets, two dates, and a genuine business reason to restructure every bit of it, which is leverage you simply cannot manufacture in an ordinary year. B does four things in a deliberate order. Map both entity lists and workforce definitions, because their Hosted Employee definition may sweep contractors yours excludes, and the merged population lands under whichever paper survives, so that choice is worth real money. Keep both running until the platform decision is made, because cancelling capacity before a migration decision is how integrations stall and how business units start buying their own software. Harmonize the clauses upward, Tom's conglomerate lesson from last session, the better cap and the better swap rights become the group template. And price thirteen thousand at group scale against session nineteen's band boundaries, because two mid size deals priced separately are strictly worse than one large deal priced once, which is the entire argument for consolidation in one sentence. C destroys the fallback before the platform is chosen, session twenty's rule applied to integrations. D volunteers the true up asymmetry: adding population without renegotiating quantities means paying the excess at the vendor's timing rather than yours. And A is the answer that looks safest and is quietly the most expensive, because the consolidation window closes when the integration finishes, and the leverage decays with every month you wait.
The acquisition problem in full, five collisions. One, overlapping subscriptions: two of everything, neither reducible mid term because of the asymmetry you now know by heart, which means the integration plan and the renewal calendar must become the same document, owned by one person. Two, colliding definitions: their workforce metric may count populations yours excludes, and since the merged workforce lands under whichever paper survives, that decision is a pricing decision disguised as an IT decision. Three, inherited compliance, and this is the one deal teams miss: you acquire their overuse too, their provisioning drift, their unnamed integrations, their optimistic declarations, so session twenty five's reconciliation belongs in diligence, before close, where it is a price adjustment, rather than after close, where it is your problem. Four, commitment collision: two OCI pools, two hyperscaler commitments, different expiries and burn rates, rarely any clean merge path, so model session seven's forfeit risk across both estates immediately, because unspent credits in an acquired pool expire on their original schedule regardless of how excited everyone is about synergies. And five, relationship duplication: two account teams, two histories, two sets of remembered promises, and one channel from the day the deal is announced, session twenty three's discipline, because during an integration the vendor will otherwise hear five different versions of your plans from five different people, and price the most optimistic one.
Negotiating ahead of the event, the three clauses, and by now you can hear why each exists. Assignment rights: the right to assign subscriptions and licenses to an acquirer, a successor, or a divested entity, with consent not to be unreasonably withheld, and that qualifier is most of the value, because it converts a veto into a process with a standard and a timeline. Divestiture adjustment: session nineteen's down lane, quantity reduction rights on qualifying corporate events, so a shrinking workforce shrinks the bill at the next cycle instead of never, the clause that was worth two point two million a year to Tom's chemicals group. And acquisition bands with transition service terms: pre priced treatment for acquired populations, so an acquisition does not reprice your whole estate at the vendor's discretion, plus a standing TSA framework so a carved out business can ride your contracts for a defined window at defined rates. Ask for all three at the first signature and at every renewal until they exist, and notice the psychology that makes this work, from the clip: in a year with no transaction pending, these clauses cost the seller's quota nothing, so they are conceded almost casually. The moment a deal is announced, the identical sentences become the most expensive paragraphs in the contract. Same words. Different week. Last check is that week.
Last check. The board announces an acquisition publicly on Monday. Your Oracle renewal is in five months and you hold no corporate event clauses. What just happened to your negotiating position? A, nothing, the renewal is a separate conversation from the transaction. B, it weakened materially: the vendor now knows the workforce is growing, that consents will be needed, and that your team is consumed by integration, so the renewal gets re planned around the disclosure rather than run as if nothing changed. C, it strengthened, a bigger company always gets better pricing. Or D, it is neutral until the deal actually closes. Pause here. What did the account team learn on Monday, and what did they do with their forecast that afternoon?
The answer is B. On Monday morning the account team learned three things and updated their forecast with all of them before lunch: your workforce is about to grow, which prices every workforce metric upward automatically; consents and assignments will be needed, which is leverage they did not hold on Friday; and your people will spend the next year on integration, which means the renewal gets session twenty seven's tired team, and they staff accordingly. A treats a public disclosure as private information, which it stopped being at the moment of the press release. D imagines that leverage arrives at close, when in reality the vendor's forecast moves the day the market learns, and the renewal five months out is now being planned against a customer they know is distracted and growing. C confuses scale with leverage, and the distinction matters: bigger estates negotiate better only when they arrive consolidated and prepared, and a mid integration estate is neither, it is two estates wearing one logo. Now, what B actually prescribes is practical rather than heroic, because you cannot un announce a deal. Re plan the renewal around the disclosure. Consider a short extension to clear the integration peak, session twenty seven's spacing rule, because a renewal fought during month four of an integration is a renewal conceded. Negotiate the consents and the acquisition treatment as one package rather than as a sequence of separate favors, each of which would be priced separately. And pull the acquired entity's contracts into the same negotiation so the consolidation window and the renewal window coincide, converting a bad week into the one good structural opportunity available. Then write the lesson down for next time, which is this entire session: the clauses that would have made Monday uneventful cost nothing in all the years when no transaction was pending.
The corporate events playbook, three states. In peacetime: assignment rights, divestiture adjustment, and acquisition bands on every order, the entity list current in the register from last session, the support repricing linkages modeled so nobody discovers them during a carve out, and the estate documented well enough that a diligence request takes days rather than months, which is itself a deal speed argument your CFO will appreciate. Under a transaction: licensing joins the deal team at signing rather than at close, the transfer map run instrument by instrument for the specific event, TSA terms and consents negotiated as one package because separate favors get priced separately, and message discipline, one channel, with the vendor learning the deal's shape from you, deliberately, at a time you choose. After the event: work the consolidation window while it is open, co term, harmonize the clauses upward, reprice at group scale, retire the duplicate estate, and then update the register, the calendar, and the files to the new org chart, because a governance system that describes the previous corporate structure is decoration. Three states, one underlying idea: the org chart will move, more than once, over the life of these contracts. The only question is whether the paper anticipated it. Next session, the last one before the capstone, we look across the table properly: the account team, their compensation, their quarter, and the incentives behind every conversation this course has taught you to have.
Session twenty eight, three sentences. One: nothing transfers automatically, subscriptions bind to entities, licenses move only by their assignment terms, support reprices when license sets split, and commitments rarely divide at all, so every corporate event is at bottom a clause question asked under time pressure. Two: divestitures need transition service terms and a residual adjustment or you pay for departed people until renewal, acquisitions open a consolidation window that closes when the integration finishes, and both outcomes are decided by paper written long before anyone knew a transaction was coming. Three: public disclosure moves leverage to the vendor the day it happens, which is exactly why assignment rights, divestiture adjustment, and acquisition bands are bought in peacetime, when nobody expects to need them, and cost almost nothing, and why the ask belongs on every renewal list until the answer is yes. Next week: the relationship, the account team, the quarter, and the incentives on the other side. Then the capstone. Two sessions left. See you there.
Homework, about an hour, and it is a stress test rather than an inventory. One, read the assignment clause, actually read it, in your master agreement and your two largest orders: what does assignment require, and is consent qualified in any way, because unqualified consent is a veto and qualified consent is a process, and most people do not know which one they signed. Two, run the divestiture case: pick your most separable division and answer three questions, what would it need on day one, what would transfer with it, and what would your residual bill look like with no adjustment clause, that third number is usually the one that gets the clause approved. Three, run the acquisition case: if the group bought a similar sized company tomorrow, what collides, definitions, dates, commitments, compliance posture, and name the first three problems out loud. Four, check the entity list on your orders against the current legal structure, because dissolved subsidiaries and missing new ones are both findings and both are common. And five, write the ask list: assignment rights, divestiture adjustment, acquisition bands, onto the next renewal's clause asks, and they stay on that list until they are signed. An hour now, in a quiet year, buys the week that Tom's chemicals group never had to have.
Five reads before next session, all free on redress compliance dot com. First, assignment clauses in mergers and divestitures, the clause that decides whether your event is a process or a toll booth, with the language to ask for. Second, license transfer in a divestiture or carve out, standing up the separated business step by step, useful the moment a disposal becomes real. Third, transfers between affiliates and subsidiaries, the entity mechanics underneath every check in this session, and worth reading even with no transaction pending because reorganizations trip the same wires. Fourth, Oracle licensing in M&A due diligence, the checklist for before and after close, including the inherited compliance problem most deal teams discover late. And fifth, Oracle mergers and acquisitions advisory, how these engagements actually run when the timeline is already fixed and the clauses are not there. That's session twenty eight. Nothing transfers automatically, everything transfers by clause, and the clauses are free in the years nobody needs them. Next week, the people across the table. See you there.