Acquisitions, divestitures, org consolidation and org splits. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
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. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP 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 five, licensing events, and this closes module five. Acquisitions, divestitures, org consolidations and splits. What these have in common is that they are corporate decisions with licensing consequences, made by people who have never read your Salesforce agreement, on timelines announced publicly before anybody asks you a question. The licensing questions themselves are not difficult. Being asked them six weeks before a go live is what makes them expensive. So today: the four events and what each does to your agreement, acquiring, divesting, consolidating and splitting, the clauses to hold in advance, and how to get into the room early. Three knowledge checks. Let's begin.
Five objectives. First, see the licensing event inside the corporate one, because every structural change moves users, entities and data across a contract boundary. Second, handle an acquisition: two agreements, two renewal dates, and a window where you hold unusual leverage. Third, handle a divestiture, where transition rights are the whole game and they are negotiated before the deal closes. Fourth, separate org work from licence work, because consolidating orgs is a technical programme with a commercial shadow. And fifth, get into the room early, since licensing arrives at corporate deals late and late is where the money is lost.
So, corporate events are licensing events. Entities move, because your agreement names who may use it and a new subsidiary may not be named. Users arrive, hundreds or thousands of them, needing access on a timeline set elsewhere. Two contracts exist, since both organisations have agreements, terms, dates and commitments of their own. And deadlines are fixed, because integration dates get announced publicly and your negotiating window is whatever remains. Let me explain why nobody in the deal room is thinking about any of this.
Guest analyst clip.
Which is why this session is really about timing. The licensing questions are not hard. Being asked them six weeks before a go live, with a public date attached, is the thing that makes them cost money.
Right, the four events. An acquisition asks whether the acquired entity can use your agreement and at what price, and the risk sits in the named entities and a deadline you did not set. A divestiture asks how the departing business keeps working after separation, and the risk sits in transition rights, which must be agreed before close. Consolidation asks about merging orgs, licence types and duplicate contracts, and the risk is two commitments that may both survive the merge. And an org split asks about separating one estate into two working environments, where minimums can apply twice and data must divide cleanly. In every one of these the licensing answer is easier when asked early, and every one of them tends to be asked late, which is the pattern worth breaking.
First knowledge check. Your company acquires a business. When should licensing be involved? A, at integration planning, once the systems approach is decided. B, during due diligence, before the deal closes. C, when the acquired users need accounts. D, at the next renewal, when everything can be tidied together. Pause here and pick an answer before you continue.
B. Diligence is when the target's software contracts are being read anyway, and it is the only point at which a licensing finding can still change the price or the terms of the corporate deal itself. A is common, and it is already past the moment where the systems approach could have been informed by cost. C is far too late, because the deadline is now fixed and public. And D leaves you operating outside your entitlement in the meantime, which is not a tidy position to be renewing from.
So, acquiring a business. Five questions, in order. Does your agreement cover them, which means reading the entity definition, because affiliate language varies enormously and it decides everything else. What do they already hold: their own Salesforce agreement, its term, its commitment and its renewal date. Which contract survives, because two agreements is a choice and running both is sometimes the cheaper answer for a period. What is the combined position, since two customers becoming one is a genuine increase in scale and scale is a lever. And when do you use it, which is before the integration deadline is public, because after that you are buying under duress. Now, the other direction.
Guest analyst clip.
Transition rights decide how this goes. The buyer needs continuity, because the divested business must keep operating on day one and usually on your systems. That needs permission, meaning a transition services arrangement, and your agreement has to allow a non affiliate to use it.
Agree it before close, because afterwards you are asking for a favour with a signed sale agreement behind you. Then plan your reduction, since those users leave your count eventually and the commitment does not fall by itself. And watch the minimum, because a divestiture can drop you below a committed floor you are still contractually holding.
Second knowledge check. You divest a division representing a fifth of your Salesforce users. What is the immediate commercial risk? A, nothing, fewer users means a lower bill. B, you remain committed to a minimum that now exceeds your usage. C, the buyer inherits your agreement automatically. D, your discount level is recalculated immediately. Pause here before you continue.
B. The commitment is contractual and the users leaving is operational, so the two do not move together unless you negotiated a divestiture provision, and most agreements are silent on exactly this point. A is the intuition and it is precisely backwards without a reduction mechanism. C does not happen, which is why transition rights matter and have to be arranged deliberately. And D would be a reasonable consequence and it is not automatic, and note that a discount tied to volume can actually work against you when volume falls.
Now consolidation and splits, which is a technical programme with a commercial shadow. Consolidation is not a saving by itself, because merging two orgs does not merge two contracts and those are separate pieces of work with different owners. Licence types rarely match, since two estates built independently will have different types, editions and add ons. Duplicate add ons surface, which is the best consolidation finding: two of everything and only one needed. Splits multiply minimums, because two orgs can mean two of every floor and platform allowances do not divide neatly. And time it with a renewal. Let me explain that last point, because it is where the value is.
Guest analyst clip.
A consolidation landing just before a renewal turns technical work into commercial leverage. Landing just after it turns the same work into a saving you will wait two years to collect, and that difference is purely scheduling.
So, five provisions worth having before you need them. A broad affiliate definition, so an acquired entity is covered without a separate negotiation under time pressure. Assignment and change of control, covering what happens to the agreement when either party's ownership changes. Divestiture transition rights, meaning a stated period during which a departing business may continue to use the service. And a reduction on divestiture, the right to reduce the commitment proportionately when a business leaves. And then the point that matters: ask at signature, because none of these can be won in the six weeks before an announced integration date, when the other side knows exactly how much you need them.
Five failures. Licensing told after announcement, so the integration date is public and every question now has a deadline attached to it. Acquired users connected quietly, with access granted to an entity the agreement does not name, discovered later by somebody counting. No transition rights, so a divested business locked out on day one, or an emergency arrangement at any price they choose to ask. The commitment never adjusted, where users left, the floor stayed, and it renewed unchanged for two more years. And consolidation without contract work, where the orgs merged beautifully, both agreements are still running, and no saving was realised at all.
Last knowledge check. When is your leverage highest in an acquisition? A, after the integration date is announced, when the urgency is shared. B, before the deadline is public, while the combined scale is the main fact. C, at the first renewal after integration. D, during the systems migration itself. Pause here and pick an answer before you continue.
B. Two customers becoming one is genuinely good news for the vendor, and that is the only moment where it is the dominant fact in the room, before a fixed public date turns the conversation into one about how quickly you can be accommodated. A misreads whose problem the deadline is, and it is yours. C is after every decision has been made and paid for. And D is the worst moment available, because a migration in flight cannot pause while somebody negotiates a contract. Let me finish with how you get told earlier.
Guest analyst clip.
Four things that put licensing into the diligence pack. A one page standing brief, setting out what corporate development needs to ask about software in any transaction. A named contact, meaning somebody in corporate development who knows to call you, by name, before close rather than after. A standard question set, five questions about the target's agreements, added to the diligence checklist so it happens without anybody remembering. Your own position kept current: entity definitions, commitments and renewal dates, ready rather than assembled under pressure. And it costs almost nothing, one page and one relationship, and it changes the moment at which you find out, which is the only variable that really matters here.
Three sentences. Every structural corporate change is also a licensing event, because agreements name entities, commitments do not move with users, and integration deadlines are announced publicly by people who have not read your contract. An acquisition gives you a genuine window of leverage while combined scale is the dominant fact, and a divestiture turns on transition rights and a reduction provision, both agreed before the deal closes rather than after it. And the clauses that make all of this manageable, a broad affiliate definition, change of control, transition rights and reduction on divestiture, are cheap at signature and unwinnable six weeks before an announced date. That closes module five.
Homework before session twenty six, about ninety minutes. One, read your entity definition: exactly who may use the agreement, and what counts as an affiliate. Two, find the change of control clause and what happens to the agreement if either side's ownership changes. Three, check for transition rights, meaning whether a divested business could keep using your service and for how long. Four, find your corporate development contact, one name, and introduce yourself before there is a transaction to discuss. And five, draft the one page brief: five questions about software contracts, ready to hand over on the day you are called.
Five guides, all on redresscompliance dot com. Salesforce merger contract negotiation covers what a CIO needs to know before the deal closes. Salesforce M and A licensing advisory describes how the diligence and integration licensing work is run. Salesforce licence count audit covers establishing the baseline you will need on both sides of a transaction. Salesforce minimums and true ups explains why a commitment does not fall when the users do. And Salesforce contract terms, ten clauses, shows where affiliate, assignment and change of control language sits.
That is session twenty five, and module five is complete. The thing to take away is that the licensing work in a corporate event is not complicated, it is just always late, and one page plus one relationship is what moves it earlier. Next time we open module six on negotiation, starting with the Salesforce fiscal calendar: the January year end, the quarter ends, and how timing sets the price. See you then.