SAP Licensing in Carve-Outs and Divestitures: What Happens to Licences When You Split

A carve-out or divestiture creates one of the most commercially dangerous moments in an enterprise's SAP lifecycle. The deal team is focused on the SPA (Sale and Purchase Agreement), the business case, the integration or separation timeline. SAP licensing — the question of which entities retain which rights, under what terms, for how long — rarely gets the attention it deserves until it is almost too late to influence the outcome.

The consequence of that gap is predictable. The divested entity arrives at completion without a valid SAP licence arrangement. SAP triggers change of control provisions. The buyer is forced into a rushed new contract negotiation — at list price, without the legacy discounts the seller had accumulated over years — while simultaneously managing a complex IT separation. Meanwhile, the seller discovers that reducing their licence count post-sale is not as simple as removing names from an invoice.

SAP licensing in carve-outs is a specialised discipline that intersects contract law, SAP's commercial policies, technical landscape separation, and M&A deal structure. This guide covers the essential framework every M&A team, IT director, and commercial lead needs to understand before and during any corporate separation event.

What SAP's Contract Actually Says About Carve-Outs

SAP's standard Master Licence Agreement and its successor general terms contain change of control provisions that are triggered by a divestiture event. The specific language varies by contract vintage and the governing terms in your Order Forms, but the general principle is consistent: SAP licences are granted to a specific named legal entity, and a change in the control or ownership of that entity requires SAP's consent to transfer the licence.

This is not a theoretical risk. SAP's commercial team monitors corporate announcement feeds, tracks M&A news about their customers, and proactively contacts accounts where a change of control event has been announced. In some cases, SAP's notification arrives before the deal team has finished reviewing the SAP contract provisions in the SPA.

The seller's position

The selling entity typically holds the Master Agreement and the associated Order Forms. When a business unit is sold, the seller faces a fundamental question: which licences were being used by the divested business unit, and what happens to those entitlements post-closing? The answer is more complex than it appears.

SAP licences under a group entity structure are often not cleanly attributable to individual subsidiaries or business units. A group ELA (Enterprise License Agreement) might cover users across 40 entities in 20 countries, with users in the divested unit mixed into the same measurement pool as users who are staying. Untangling that is not a simple administrative exercise — it requires a forensic analysis of user assignments, system access, and the contractual scope of the original licence grant.

The buyer's position

The acquiring entity faces a different problem. Even if the seller has contractually allocated SAP licences to the divested business in the SPA, SAP must consent to the transfer. And SAP's consent is not unconditional. SAP will typically use the occasion of a licence transfer to review the commercial terms, potentially eliminate legacy discounts, and push for a new commercial relationship on current pricing. The buyer who assumes they are inheriting a valuable licence position may find that SAP's consent comes with a price reset attached.

The Four Most Common SAP Carve-Out Licence Scenarios

SAP Licence Due Diligence in a Carve-Out

Whether you are the buyer or seller in a divestiture, a structured SAP licence due diligence is essential. This is a distinct workstream from the general IT due diligence — it requires SAP licensing expertise, not just IT architecture knowledge.

For the seller: pre-deal licence analysis

Before the SPA is finalised, the seller must understand their SAP licence position well enough to make representations about what is being transferred. This requires a detailed ELP (Effective License Position) analysis that covers:

• User attribution: Which Named User licences are assignable to the divested entity, and which are shared across the broader group? The USMM measurement tool captures system-level user data, but attributing those users to legal entities requires a separate analysis layer
• Package and engine licences: Engines and packages are typically licensed to a legal entity or system, not to individual users. Understanding which engines are embedded in systems used by the divested entity — and whether those systems are being transferred — is essential
• Maintenance allocations: Annual maintenance fees are typically invoiced to the contracting entity rather than attributed to individual subsidiaries. The seller must determine how maintenance costs should be allocated in the SPA and how the divested entity's ongoing support will be funded
• Order Form scope: SAP Order Forms often define the permitted use by reference to subsidiaries and affiliates of the contracting entity. If the divested entity ceases to be a subsidiary, its continued access may be contractually unauthorised — even before the TSA expires

For the buyer: licence validation before signing

Buyers frequently accept seller representations about SAP licence entitlements without independent validation. This is a material risk. The representations in the SPA about what SAP licences are being transferred may be technically accurate but commercially misleading — for example, a representation that 1,000 Named User Professional licences are being transferred may be technically correct but fail to disclose that those licences carry a maintenance obligation of €4M per year, or that they are subject to SAP's change of control consent right.

Pre-signing SAP licence due diligence for buyers should cover:

• Review of the actual SAP contract documentation — Master Agreement, all Order Forms, applicable T&Cs, and Maintenance Schedules
• Identification of change of control provisions and the mechanism for consent
• Assessment of the current ELP for the divested entity — what licences are actually being used versus contractually allocated
• Understanding of SAP's likely commercial position on the transfer: will they consent on existing terms, or use this as a repricing opportunity?
• Identification of any current audit exposure, measurement shortfalls, or compliance gaps that would transfer with the licence

Negotiating SAP's Consent: What SAP Wants and What You Can Push Back On

SAP's consent to a licence transfer is required under most change of control provisions, but the terms of that consent are negotiable. Understanding SAP's commercial interests in a carve-out — and where they are and are not willing to flex — is essential for managing both the timing and the commercial outcome of the transfer.

What SAP's commercial team wants from a carve-out

SAP's primary commercial interest in any change of control or divestiture event is revenue protection and revenue growth. Specifically:

• Eliminate legacy discounts: The seller may have negotiated favourable maintenance rates, volume discounts, or structural protections over years of commercial engagement. SAP will attempt to use the transfer as an opportunity to reset these to current commercial terms for the buyer
• Increase user counts: If the licence count being transferred is based on historical measurements that are below actual usage, SAP may use the transition to require a true-up or establish a new baseline that reflects actual usage
• Accelerate cloud migration: SAP's commercial team frequently conditions licence transfer consent on the buyer's commitment to a migration timeline — essentially using the carve-out as a forcing function for RISE with SAP or S/4HANA adoption
• Establish a direct commercial relationship: A divested entity that previously operated under a group agreement gives SAP the opportunity to establish a direct account relationship, with all the associated commercial opportunities that creates

What you can push back on

SAP's change of control rights are real and enforceable, but the terms of their consent are not fixed. These are the areas where push-back is both possible and commercially significant:

SPA Provisions That Protect Both Parties on SAP Licensing

The Sale and Purchase Agreement is the legal framework that governs the allocation of SAP licensing risk between seller and buyer. Too often, SAP licensing provisions in SPAs are either absent, vague, or drafted by lawyers without sufficient SAP licensing expertise to anticipate the commercial risks. These are the provisions that matter.

Representations and warranties

The seller should warrant the accuracy of the ELP as of a defined reference date, confirm that no audit is pending or threatened, represent that there are no undisclosed compliance gaps, and confirm the nature and scope of all outstanding SAP maintenance obligations. Buyers should ensure these representations are backed by appropriate indemnities and have meaningful survival periods — SAP audit claims can emerge 12–24 months post-closing.

Licence allocation schedule

The SPA should include a detailed schedule that specifically identifies the SAP licences being allocated to the divested entity — not as a general reference to "all SAP licences used by the business" but with specific reference to Order Form numbers, licence metrics, quantities, and permitted entities. Ambiguity in this schedule creates disputes post-closing.

TSA SAP provisions

The TSA should explicitly address SAP access — specifically, confirming that the seller's licence permits the continued use by the divested entity during the TSA period, establishing who is responsible for maintenance costs during the TSA, defining the process for establishing the buyer's independent licence arrangement, and setting a clear end-date after which the buyer bears full responsibility for their own SAP licence compliance.

SAP consent risk allocation

If SAP's consent to transfer is required, the SPA should address what happens if that consent is withheld or conditioned on new commercial terms. Specifically: who bears the cost if SAP demands a new maintenance rate as a consent condition? Who bears the cost of a true-up if SAP conditions consent on a measurement and the measurement reveals a shortfall? These are real scenarios that arise in nearly every carve-out involving SAP, and leaving them unaddressed in the SPA creates post-closing disputes.

The SAP Licensing Carve-Out Timeline

Managing SAP licensing in a carve-out requires dedicated workstreams that start well before signing and continue through completion and into the post-closing stabilisation period. This is the realistic timeline for a well-managed SAP licence separation:

"The most common and most expensive SAP carve-out mistake is treating the licence separation as an IT infrastructure problem. It is a commercial negotiation with SAP as the counterparty — and SAP has a direct financial interest in the outcome. It requires the same rigour and specialist expertise as any major SAP contract renegotiation."

Working With SAP During a Carve-Out: Practical Advice

SAP's response to a carve-out notification will depend heavily on the relationship quality, the commercial significance of the accounts involved, and SAP's internal M&A tracking capabilities. A few practical principles from enterprise M&A engagements:

• Notify SAP at the right time: Too early (before signing) and you risk deal confidentiality. Too late (at closing) and you lose the opportunity to shape SAP's approach. The optimal timing is typically just after public announcement, with a structured briefing from the account team leads of both buyer and seller
• Present a unified position: If buyer and seller are not aligned on the SAP licensing outcome, SAP's commercial team will identify and exploit the disagreement. Agree the commercial position between buyer and seller before engaging SAP
• Do not negotiate under time pressure: SAP knows deal timelines and will use TSA expiry dates and closing deadlines as negotiating pressure. Beginning the SAP licence negotiation at least 12 months before any hard deadline is the single most important way to protect your commercial position
• Use independent advisors: SAP implementation partners and system integrators have conflicts of interest in M&A licence negotiations. Independent buyer-side SAP licensing advisors who work exclusively with enterprise buyers provide the objectivity and benchmarking data needed to challenge SAP's consent conditions effectively

Related Articles

• SAP Licensing in Mergers & Acquisitions: What Happens to Your Licences When Companies Merge
• SAP Change of Control Clauses: What Happens to Your Contract During an Acquisition
• SAP Group Licensing and Affiliates: How to Extend Your ELP Across the Corporate Group
• SAP Licence Compliance for Subsidiaries and Affiliates: Group Licensing Rules Explained
• SAP Contract Amendments: How to Renegotiate Order Forms and Licence Schedules
• SAP General Terms and Conditions Explained: Key Clauses Every Enterprise Buyer Must Understand
• SAP Contract Negotiation: The Enterprise Guide for 2026