Get SAP Advisory Insights Delivered
Join enterprise IT leaders receiving our monthly advisory on SAP contract strategy, M&A licensing risks, and cost optimisation.
By Fredrik Filipsson · SAP Contract Negotiation · Updated February 2026 · ~18 min read
01 Why SAP Licensing Is the Hidden Risk in Every Divestiture
Corporate divestitures create immediate SAP licensing challenges that most deal teams underestimate. The core problem is contractual: SAP software licences are non-transferable. They are tied to the original licensee and its majority-owned affiliates, and they cannot be assigned, split, or sold to another entity without SAP's explicit written approval.
The moment a divested business unit ceases to be a majority-owned affiliate of the parent company, it has no legal right to use the parent's SAP software. Every user who logs into the SAP system, every interface that exchanges data, and every batch job that executes is technically unlicensed. This is not a theoretical risk. SAP actively monitors M&A activity and divestitures are known audit triggers.
Non-Transferable Licences
SAP's standard terms prohibit transferring perpetual licences to another company. Even in an internal reorganisation or spin-off, splitting licences between entities requires SAP's written consent, which is never automatic and frequently involves fees or new licence purchases.
Cloud Subscriptions Locked
SAP cloud products (SuccessFactors, Ariba, Concur, BTP) are contracted per subscribing entity. There is no concept of partially transferring a cloud tenant or splitting a shared subscription. The spin-off needs its own agreement and tenant.
Audit Trigger
SAP monitors customer M&A activity. Divestitures are among the most common audit triggers because they frequently create compliance gaps: unlicensed cross-use, transferred systems without proper licensing, or dramatic changes in user counts.
Financial Exposure
Without planning, the divested entity faces relicensing at list price (losing the parent's negotiated discounts), while the parent continues paying maintenance on licences it no longer needs. Both sides lose money.
02 SAP's Non-Transferability Rule and Affiliate Clauses
Understanding SAP's contractual framework is essential before planning any divestiture licensing strategy. Two provisions dominate the landscape.
The Assignment Restriction
SAP's General Terms and Conditions explicitly prohibit customers from assigning, transferring, or sublicensing software rights to any third party without SAP's prior written consent. This restriction applies to both perpetual on-premises licences and cloud subscriptions. Unlike some enterprise vendors that allow licence transfers in certain M&A scenarios, SAP provides no automatic exception for divestitures.
The Affiliate Definition
SAP contracts typically extend usage rights to the licensee's "affiliates," defined as entities in which the licensee holds a majority ownership interest (usually greater than 50%). While a business unit remains a subsidiary, it operates under the parent's SAP umbrella. The moment ownership drops below the majority threshold, the former subsidiary falls outside the affiliate definition and loses all SAP usage rights.
Perpetual Licences
Tied to the original customer and named affiliates. Cannot be assigned or sold to another entity without SAP's written approval. Once the spin-off is no longer majority-owned, it has no entitlement to use the parent's SAP software, regardless of whether the systems physically reside in the divested entity's data centres.
Subscription Services
SuccessFactors, Ariba, Concur, BTP, and other SAP cloud services are contracted to a specific legal entity. There is no mechanism to "split" a cloud subscription mid-term. The spin-off requires its own subscription agreement and tenant, with a full data migration.
Digital Access & Interfaces
If third-party systems or custom interfaces access the parent's SAP system on behalf of the divested entity, this creates indirect/digital access licensing exposure. Post-divestiture, any continued data exchange between the separated entities through SAP triggers additional licensing requirements.
03 Licensing Options for the Spun-Off Entity
When a business unit is divested, there are two primary licensing paths, each with distinct advantages, costs, and operational implications.
| Dimension | New Contract for SpinCo | Licence Transfer (SAP Approval) |
|---|---|---|
| Mechanism | SpinCo becomes a new SAP customer with its own agreement | ParentCo splits off specific licences via SAP-approved amendment |
| SAP approval | Standard process. No special approval needed. | Explicit written approval required. Not standard. |
| Pricing | Negotiated from scratch. May lose parent's volume discounts. | SpinCo may retain legacy pricing on transferred licences |
| System impact | Requires SAP system migration and data carve-out | Minimal system disruption if licences cover existing deployment |
| Parent impact | Parent left with unused licences unless terminated with SAP | Parent sheds licences it no longer needs |
| Speed | Months to negotiate and implement | Faster if SAP agrees |
| Likelihood | Common. This is the default path. | Uncommon unless pre-negotiated in the contract |
The Transitional Services Agreement (TSA)
In practice, most divestitures use a Transitional Services Agreement to bridge the gap between closing day and the spin-off obtaining its own SAP capability. Under a TSA, the parent continues to operate SAP on behalf of the divested entity for a defined period, typically 6 to 18 months, while the spin-off procures its own licences and builds or migrates its own SAP environment.
04 Pricing Implications and Cost Mitigation Strategies
Splitting an SAP estate almost always increases total licensing costs. Understanding where the cost pressure comes from enables targeted mitigation strategies.
Volume Discount Erosion
The parent's negotiated discounts (often 30 to 60% off list) were based on a combined user count and licence volume. Post-divestiture, neither entity individually qualifies for the same discount tier. SpinCo buying 500 licences gets worse pricing than ParentCo buying 3,000.
Overlap Costs
During the TSA period, both entities may be paying for SAP: the parent on its existing contract (including the divested users) and the spin-off provisioning its new environment. Careful timing of maintenance renewals and licence terminations minimises this overlap.
Stranded Licences
After divestiture, the parent retains licences it no longer needs but continues paying 22% annual maintenance on them. SAP's contracts do not automatically allow partial termination. The parent must negotiate with SAP to shed the excess, which SAP has limited incentive to facilitate.
Migration & Implementation
Building a new SAP instance for the spin-off involves system implementation, data migration, customisation, testing, and training costs that can easily exceed the licence cost itself. Budget for total cost of ownership, not just licence fees.
Vendor Shield: SAP Divestiture Advisory
Our SAP advisory team has guided dozens of corporate separations, spin-offs, and carve-outs. We protect both sides of the transaction from audit exposure and secure favourable terms from SAP.
05 Planning Ahead: Protective Contract Clauses
The most effective divestiture licensing strategy is one negotiated before any deal is announced. CIOs who anticipate potential corporate restructuring should negotiate protective provisions into their SAP agreements during regular renewal or purchase cycles.
Divestiture Transfer Rights
Negotiate a clause permitting a portion of licences to be transferred to a new entity in the event of a divestiture. Even a one-time carve-out right saves the spin-off from an immediate list-price repurchase and saves the parent from paying maintenance on stranded licences. Example language: "In the event Customer divests a business unit or subsidiary, Customer may transfer a proportionate share of its SAP licences to the divested entity, subject to written notice to SAP within 90 days of closing."
Transitional Use Clause
Ensure the contract explicitly allows continued SAP use by a divested entity under a TSA. This removes ambiguity about the legality of TSA-based access and prevents SAP from charging unexpected transitional fees. Example: "Following a divestiture, the divested entity may continue to use SAP software under a TSA with Customer for up to 18 months, without requiring a separate SAP licence during the transition period."
Price Protection Clauses
Negotiate protections against financial penalties triggered by a divestiture. Preserve the economic value of the parent's negotiated terms through the transition. Example: "A reduction in Customer's licensed user count resulting from a divestiture shall not trigger a recalculation of discount percentages or an increase in support fee rates. The divested entity shall be entitled to purchase SAP licences at the same discount level as Customer for 24 months following the divestiture."
Maintenance Base Reduction Right
Include a right to reduce the maintenance base proportionally following a divestiture. Without this, the parent is locked into paying maintenance on licences it can no longer use. Example: "If Customer divests a business unit, Customer may terminate support for the proportionate share of licences attributable to the divested entity at the next annual renewal date."
06 Step-by-Step Divestiture Licensing Playbook
Assess the SAP Landscape (Pre-Announcement)
Before the deal is announced, conduct a comprehensive inventory of all SAP products, licences, users, and interfaces attributable to the business unit being divested. Include on-premises licences, cloud subscriptions, indirect/digital access touchpoints, and any shared services or cross-entity SAP usage. Quantify the maintenance cost attributable to the divested unit.
Engage SAP Early (Deal Announcement)
Inform SAP as soon as practically possible after the deal is announced. Use the early engagement to understand SAP's position on the transaction, explore transfer or novation options, and begin negotiating transitional arrangements. SAP's cooperation is essential. Surprising them at closing creates adversarial dynamics.
Negotiate TSA and Transitional Licensing (Pre-Closing)
Finalise the Transitional Services Agreement with explicit SAP coverage. Negotiate any transitional fees, duration, scope, and exit milestones. If your contract contains pre-negotiated divestiture clauses, activate them. If not, negotiate ad hoc arrangements with SAP using the commercial leverage of the spin-off's future licensing needs.
Procure SpinCo's SAP Licences (Closing to TSA Period)
The spin-off should begin licence procurement immediately. Negotiate as a new customer but leverage the parent's relationship, volume, and any pre-negotiated price protections. Evaluate whether on-premises perpetual, cloud subscription, or RISE with SAP best serves the spin-off's strategy. Right-size from day one.
Execute Data and System Migration (TSA Period)
Carve out the spin-off's data, configure its new SAP environment, migrate customisations and interfaces, and conduct thorough testing. This is typically the longest workstream and should begin as early as possible. Plan for parallel running of both environments to validate data integrity before cutover.
Optimise the Parent's Estate (Post-Closing)
After the spin-off is operating independently, terminate or reallocate the parent's surplus licences. Work with SAP to reduce the maintenance base. Conduct a post-divestiture licence review to confirm the parent is not carrying shelfware attributable to the divested unit. Ensure all shared services and cross-entity access has been properly decommissioned.
07 Cloud Subscription Considerations
SAP cloud products require special handling during divestitures because of their subscription-based, per-entity structure.
No Partial Assignment
Cloud subscriptions cannot be partially transferred. If the parent and divested unit share a SuccessFactors tenant with 5,000 employees, you cannot peel off 1,500 users to a new entity. The spin-off needs its own tenant, its own contract, and a data migration. Mid-term contract splits are not supported.
Contract Novation
If the divested unit has its own distinct SAP cloud subscription (e.g., a separate Ariba instance), SAP may agree to novate the contract, transferring the subscription from the parent to the spin-off. This is case-by-case and requires SAP's explicit agreement, but it avoids the cost and complexity of a new procurement.
Greenfield Cloud
For spin-offs building from scratch, SAP cloud may offer the cleanest path. SAP is aggressively pricing RISE with SAP and S/4HANA Cloud for new customers. The spin-off can negotiate as a greenfield opportunity, potentially securing better terms than the parent's legacy on-premises arrangement.
08 Common Pitfalls and How to Avoid Them
09 Case Studies
Frequently Asked Questions
Not without SAP's written consent. Standard SAP agreements prohibit transferring licences to another company. In practice, the spin-off will need its own SAP contract, unless you previously negotiated a divestiture transfer clause. Even with SAP's approval, transfer fees or contract modifications are likely.
Only for a defined transition period under a TSA that SAP has approved or acknowledged. Typical TSA durations are 6 to 18 months. After the TSA expires, the spin-off must be operating on its own SAP licence. Extending a TSA beyond the agreed period without SAP's consent creates compliance exposure for both parties.
SAP can audit and demand back-payments or immediate relicensing at list price. The parent may be held responsible for allowing unlicensed use by a former affiliate. SAP monitors M&A activity through public filings and account team intelligence. The resulting audit produces the worst possible financial outcome because you have zero negotiating leverage.
Several approaches work: include the spin-off's licence needs in the parent's next SAP deal to preserve volume leverage; negotiate a price protection clause before the divestiture that extends the parent's discount tier to the spin-off for 12 to 24 months; position the spin-off as a greenfield cloud opportunity if evaluating RISE with SAP or S/4HANA Cloud; and engage independent advisory to benchmark pricing and negotiate from an informed position.
No. Cloud subscriptions cannot be partially assigned mid-term. If the spin-off uses the parent's cloud instance (e.g., shared SuccessFactors), it needs its own subscription, tenant, and data migration. SAP may agree to novate a distinct, standalone subscription to the new entity, but shared subscriptions must be separated through new procurement.
Yes. Divestitures are among the most common SAP audit triggers. SAP actively monitors customer M&A activity and recognises that corporate separations frequently create compliance gaps. Engaging SAP early, obtaining written approval for transitional arrangements, and maintaining demonstrable compliance throughout the process significantly reduces audit risk.
📚 SAP Contract Negotiation Series
SAP Contract Negotiation Playbook (Pillar) → Managing SAP Licensing During M&A → Temporary Licence Bridging for M&A Transitions → Merging SAP Contracts After a Merger → Negotiating SAP Contracts for Audit Protection → SAP Indirect Access Licensing Explained → Benchmarking SAP Discounts → Bundling SAP Modules for Discounts → SAP Support Negotiations → Cutting SAP ECC Maintenance Before 2027 →SAP Contract Negotiation Playbook
Pillar Guide
SAP Knowledge Hub
Knowledge Hub
SAP Assessment Tools (11)
Assessment Tools
SAP Audit Preparation Toolkit
Audit Defence
SAP Contract Negotiation Service
Service
Renewal Playbooks (7)
Renewal Playbooks
SAP Case Studies
Case Studies
White Papers
White Papers
Navigating SAP Licensing in a Divestiture?
Our SAP advisory team has guided dozens of corporate separations, spin-offs, and carve-outs. We protect clients from audit exposure and secure favourable terms from SAP. 100% independent, vendor-neutral advisory.