Case Study: Divesting a Business Unit Running SAP

01The Core Problem: SAP Licences Are Non-Transferable

SAP software licences are tied to the contracting entity and its majority-owned affiliates. When a business unit is divested and ceases to be a majority-owned affiliate of the parent, it immediately loses the legal right to use the parent's SAP software. This is not a theoretical risk — SAP actively monitors M&A activity and divestitures are known audit triggers. The divested entity has no licence rights from Day One of separation without a contractual bridge.

This guide provides a practical framework for managing SAP licensing in carve-outs, spin-offs, and corporate separations — covering the three available options, how to protect commercial terms, and what to negotiate with SAP before the transaction closes.

02Three Options for the Divested Entity

Option 1: Transitional Services Agreement (TSA)

The most common immediate solution. The parent company continues to operate SAP as a service provider to the divested entity under a formal TSA. SAP licences remain with the parent; the divested entity operates under the TSA umbrella. TSAs typically run 6 to 18 months for SAP environments and must be carefully structured to define service levels, cost allocation, and the termination trigger. The TSA buys time for the divested entity to establish its own SAP footprint without creating Day-One compliance exposure.

Option 2: New Licence Agreement for the Divested Entity

The cleanest long-term resolution: the divested entity negotiates and signs its own SAP licence agreement. This requires 60 to 90 days lead time to execute properly and involves repricing from scratch — the divested entity has no inherited volume credentials, which is why pre-transaction negotiation with SAP is essential. Establishing a credible user count and projected growth narrative before entering negotiations helps secure reasonable pricing. Engaging independent benchmarking ensures the divested entity does not accept above-market rates.

Option 3: Explicit Licence Transfer Consent from SAP

SAP may grant written consent to transfer specific licences to the divested entity. This is negotiated individually and almost always involves fees, licence reconciliation, or both. SAP is not obligated to grant transfer consent and typically uses this as a commercial lever. Transfer consent is best pursued for perpetual licences where the divested entity has a clear, ongoing need for the same software stack — and where the cost of a new licence agreement would significantly exceed the transfer fee.

03The Volume Discount Impact

Most large enterprises negotiate SAP pricing based on total enterprise user counts, achieving discounts of 15 to 30% or more. When a divestiture splits the user base, both entities face a volume discount cliff. The parent company's remaining user count may fall below the threshold for its current discount tier, triggering an automatic price increase at the next renewal. The divested entity starts from zero with no negotiating history.

The optimal mitigation strategy is to negotiate with SAP before the transaction closes, securing pricing commitments for both the parent's reduced estate and the divested entity's new agreement simultaneously. SAP's account teams are aware of this dynamic and will typically engage commercially when they understand that both entities represent future revenue — but only if the conversation happens before the deal structure is finalised.

04Cloud Subscription Complexity

SAP's cloud subscriptions (SuccessFactors, Ariba, Concur, S/4HANA Cloud) are tied to the contracting entity and cannot be assigned or transferred without SAP's explicit written approval and a new agreement. RISE with SAP is tenant-specific and must be renegotiated for each new legal entity. For divestitures where significant cloud investment exists, modelling the total cost of establishing independent cloud agreements — including the lost amortisation of pre-paid cloud credits and any migration costs between tenants — is essential for accurate transaction valuation and deal economics.

05Protective Clauses to Negotiate Before Close

TSA cost cap: Prevents SAP from increasing support fees during the transitional period. Essential if the TSA runs more than 6 months.

New entity commercial terms commitment: SAP agrees to offer the divested entity volume pricing consistent with its projected user count, not starting from list price.

Transfer consent pre-authorisation: Where licence transfer is preferred, pre-negotiate SAP's consent and the transfer fee before the deal closes — leverage is higher before the transaction completes.

Indemnity in transaction agreement: Ensure the seller indemnifies the buyer for SAP licence compliance claims arising from the transition period and any use of the parent's SAP systems by divested entity users after close.

Engaging independent SAP licensing advisors before transaction announcement provides the clearest picture of the licence position and the widest range of commercial options — before SAP's account teams are engaged and the negotiating dynamic shifts.

06Post-Close Compliance Risks

The most common post-divestiture SAP compliance failures include: divested entity employees retaining active user accounts in the parent's SAP system after close (creating unlicensed user exposure); interfaces between the divested entity's systems and the parent's SAP instance (indirect access exposure); and shared master data environments where the divested entity continues reading or writing to parent SAP data. Conduct a full technical access audit immediately after close and engage independent audit defence advisors before SAP conducts any licence measurement.