Most enterprise software licenses contain an anti-assignment clause that voids the license if the company is sold or merged without the vendor's written consent, so a transaction that ignores software can hand the acquirer an estate of invalid licenses and a vendor with full negotiating power. License transfer in mergers and acquisitions is a contract problem disguised as a procurement problem. The transferability of each agreement is set by its assignment and change-of-control language, and vendors treat the moment consent is required as a negotiation they are positioned to win. The buyer's defense is diligence before close.
Anti-assignment and change-of-control clauses
Two clauses decide whether a license survives a transaction. The assignment clause governs whether the agreement can be transferred to another legal entity. The change-of-control clause governs what happens when the licensee itself is acquired, even if no formal assignment occurs. A strict anti-assignment clause prohibits transfer without consent and defines a change of control as a deemed assignment, which means an acquisition triggers the consent requirement automatically. The structure of these clauses, and how to soften them at signature, is covered in our software contract negotiation guide.
Why vendors hold the advantage
When consent is required, the vendor can condition it. Common conditions include a transfer fee, a forced migration to current products or current pricing, a true-up of any compliance gap discovered in the process, and a reset of negotiated discounts to standard rates. The transaction timeline works against the buyer, because deals have closing dates and vendors know it. A consent request made two weeks before close gives the vendor maximum advantage. A consent strategy built into diligence months earlier removes most of it.
Vendor-by-vendor positions
Transfer rules vary sharply by vendor, and the major enterprise vendors each have a known posture.
| Vendor | Typical transfer position | Common consent condition |
|---|---|---|
| Oracle | No assignment without consent; ULAs especially restrictive | Certification or buyout of ULA before transfer |
| Microsoft | Transfer possible with consent; EA tied to the legal entity | Re-enrollment or new agreement for the acquirer |
| SAP | Named-entity licensing; merger triggers review | Re-measurement and potential indirect-access true-up |
| IBM | Passport Advantage tied to enterprise; consent required | Sub-capacity re-verification |
| Salesforce / SaaS | Subscription tied to the contracting entity | Novation to the acquirer at current pricing |
Oracle and SAP carry the highest risk because their metrics are entity-specific and their audit practices are aggressive. An Oracle ULA in particular should be resolved before a transaction rather than transferred through it. The consolidation opportunities after close are in our cross-vendor consolidation and vendor consolidation guides.
The audit-during-M&A trap: A merger or acquisition is one of the strongest audit triggers a vendor watches for, because the transaction creates both a reason to review compliance and a counterparty under time pressure. Vendors frequently open an audit or a soft compliance review in parallel with a consent request, then fold the audit settlement into the price of consent. Surfacing and closing compliance gaps during diligence, before the vendor does, removes this advantage entirely. The full set of triggers is in our software audit triggers analysis.
Transition service agreements and divestitures
Divestitures carry their own trap, and the 180-day TSA is where it usually appears. When a parent sells a business unit, the unit often relies on software licensed to the parent under a transition service agreement (TSA) while it stands up its own contracts. Most licenses do not permit the parent to provide the software to a now-separate entity, even temporarily, without the vendor's agreement. A TSA that assumes the existing licenses cover the divested unit can create unlicensed use from day one. The right approach is to confirm TSA software rights with each vendor as part of the separation plan and to time the divested unit's own agreements to the TSA expiry.
License diligence before close
Software license diligence belongs in the deal, not after it, and the work has four parts. First, inventory the target's agreements and classify each by transferability. Second, identify which require consent and what the vendor is likely to demand. Third, quantify compliance exposure, because any gap becomes a transfer condition. Fourth, model the post-close estate to find the overlapping licenses that consolidation will remove. The output is a transfer plan and an exposure number that belongs in the purchase agreement as a representation or an indemnity, which ties back to the protections in our indemnification clauses guide.
The data-room license checklist
A buyer reviewing a target's data room should request seven specific items, because the standard data room rarely includes them by default. The list below is the minimum that supports a transferability and exposure assessment.
| Data-room item | What it reveals |
|---|---|
| Master agreements and order forms | Assignment and change-of-control terms |
| License entitlement reports | What the target actually owns |
| Deployment and usage data | Compliance gaps and shelfware |
| Prior audit findings and settlements | Open exposure and vendor posture |
| Support and maintenance contracts | Renewal obligations that transfer |
| Cloud commitment agreements | Unspent commitments and shortfall risk |
| Reseller and partner agreements | Third-party consent requirements |
Post-close integration and consolidation
The largest single saving in an acquisition is consolidating overlapping licenses, and it is typically worth 15 to 30 percent of the combined software spend. Two merged companies almost always run duplicate productivity suites, duplicate security tools, and overlapping database and middleware estates. The integration plan should map the overlap in the first 90 days, choose a standard for each category, and time the migration to the renewal dates of the agreements being retired so that committed quantities are not stranded. The consolidation method, vendor by vendor, is set out in our cross-vendor consolidation guide.
Representations, warranties, and indemnities
The exposure found in diligence should be priced into the deal, not absorbed after it. Where the target carries a known compliance gap or a consent requirement with a quantifiable cost, the buyer should require a representation that the licenses are valid and transferable, a warranty backed by the escrow or holdback, and a specific indemnity for any vendor claim arising from the transfer. This moves the risk back to the seller, who controlled the estate, and mirrors the risk-transfer discipline in our indemnification clauses guide. The escalation and fee discipline from our escalation clauses analysis applies to the consent fee itself, which is negotiable when sought early.
Securing consent on the buyer's terms
Consent is negotiable when it is sought early, and the three levers are timing, bundling, and alternatives. Approaching the vendor before the deal is public, while the buyer still controls the schedule, prevents the deadline squeeze. Bundling the consent request with a renewal or an expansion gives the vendor a commercial reason to grant it cheaply. And a credible alternative, including migration off the product, caps what the vendor can demand.
A transaction timeline for license transfer
License transfer has a natural sequence across a deal, and starting each step at the right point removes most of the risk. In the diligence phase, typically 60 to 90 days before close, the buyer inventories the target's agreements, classifies transferability, and quantifies exposure. In the signing-to-close window, the buyer prioritizes the consent requests that gate operations and opens the highest-risk vendor conversations, Oracle and SAP first, while the schedule is still in the buyer's control. In the first 90 days after close, the buyer secures the remaining consents, stands up any divested entity's own agreements before the transition service agreement expires, and begins the consolidation analysis. Treating these as one continuous workstream rather than three disconnected tasks is what keeps a vendor from turning a deadline into a fee.
| Phase | Window | License action |
|---|---|---|
| Diligence | 60 to 90 days before close | Inventory, classify transferability, quantify exposure |
| Sign to close | Variable | Open high-risk consents, secure reps and indemnities |
| First 90 days | Post-close | Complete consents, manage TSA, begin consolidation |
| Integration | Months 3 to 12 | Consolidate overlap, retire duplicate agreements |
The same timeline protects the seller in a divestiture. A seller that maps transferability before going to market can represent the estate accurately, avoid a price retrade when a buyer discovers an unconsentable agreement, and structure the transition service agreement around what the licenses actually permit. Sellers who skip this step often find that a late-stage license problem becomes a purchase-price adjustment, which is a far more expensive way to resolve it than a consent conversation held early. Whether on the buy side or the sell side, the principle holds: the cost of license transfer is set by how early it is managed, not by how the contracts happen to read.
A practical transfer checklist
Six actions cover most of the license-transfer risk in a transaction. First, inventory every agreement and flag the assignment and change-of-control language in each. Second, rank the agreements by transfer risk, with entity-specific and audit-aggressive vendors such as Oracle and SAP at the top. Third, quantify the compliance exposure in each high-risk agreement, because that number sets the vendor consent fee. Fourth, open the highest-risk consent conversations while the closing schedule is still in the buyer control. Fifth, write the exposure into the purchase agreement as a representation and a specific indemnity. Sixth, plan the post-close consolidation that removes the duplicate licenses the combined estate will carry.
The checklist works because it sequences the actions by negotiating power rather than by convenience. The buyer has the most negotiating power before the deal is public and the least in the final days before close, so the conversations that can cost the most, the entity-specific vendor consents, belong at the front. Pushing them to the end is the single most common and most expensive mistake in M&A license transfer, because it hands the vendor a deadline it can price against.
Used together with the diligence steps and the data-room list above, the checklist turns license transfer from a source of closing-day surprises into a predictable workstream with a known cost. That predictability is what lets the deal team price the software estate accurately into the transaction rather than discovering its cost after the price is fixed, which is the difference between an exposure that is managed and one that is simply inherited.
The broader point for any deal team is that software is rarely the largest line in a transaction but is frequently the one that produces the latest and most avoidable surprises. A few weeks of license diligence, started in the right phase, converts that risk into a known number that can be priced, negotiated, and indemnified like any other deal term. The cost of getting it wrong, an invalid estate or a vendor consent fee extracted under deadline, is almost always larger than the cost of getting it right. The right time to start is the moment a transaction becomes likely, not the week before it closes.
Handled early, license transfer becomes a managed workstream rather than a closing-day surprise. For buy-side or sell-side diligence and consent negotiation, see our software licensing advisory and vendor audit defense services.