Divesting a Business Unit Running SAP: Licensing, Contract, and Cost Strategies

01Why 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.

Key constraints include: SAP's standard terms prohibit transferring perpetual licences to another company without written consent; cloud subscriptions (S/4HANA Cloud, SuccessFactors, Ariba) are locked to the contracting entity and cannot be assigned to a new entity on separation; and volume discounts negotiated for the combined enterprise typically collapse when the remaining parent's user count falls below discount thresholds — meaning both entities pay more after the split.

02The Day-One Problem: Maintaining Continuity

The most urgent challenge in any SAP-involved divestiture is ensuring the carved-out entity has legal, operational access to SAP from Day One of separation. Without a contractual bridge, the new entity may be running on unauthorised licences from the moment the transaction closes. SAP's audit teams treat this exposure seriously, and the window between transaction close and licence resolution is when audit risk is highest.

Three mechanisms address the Day-One problem. First, a Transitional Services Agreement (TSA) allows the divested unit to continue using the parent's SAP infrastructure temporarily, with the parent acting as a service provider. SAP licences remain with the parent, and the divested unit operates under the TSA's contractual umbrella. TSAs typically run 6 to 18 months for SAP transitions. Second, the divested entity can procure new SAP licences ahead of or at close — a clean break that requires lead time (typically 60 to 90 days) and involves repricing from scratch without any volume discount inheritance. Third, SAP may grant a licence transfer with explicit written consent, which is negotiated individually and almost always involves fees or licence reconciliation.

03SAP's Non-Transferability Rules in Detail

SAP's standard software licence agreement defines the authorised licensee as the contracting entity and its majority-owned affiliates (generally entities where the contracting party owns more than 50% of voting shares). When a divestiture removes the carved-out entity from the parent's affiliate group, those entities lose their right to use licences that were purchased under the parent's agreement. This is non-negotiable under SAP's standard terms — there is no automatic transfer mechanism, no grandfather clause, and no grace period.

Cloud subscriptions compound the problem. SAP's cloud agreements (SuccessFactors, Ariba, S/4HANA Cloud, Concur) are tied to the named contracting entity and cannot be transferred without SAP's explicit approval, a new contract, and typically a fee. In some cases, SAP requires a full new subscription agreement for the carved-out entity, with pricing reset to current rates — potentially eliminating any negotiated discounts from the original deal.

04The Volume Discount Cliff: Why Both Sides Pay More

Most large enterprises negotiate SAP licence pricing based on total enterprise user counts, revenue, or headcount — achieving volume discounts of 15 to 30% or more. When a divestiture splits the user base, both the parent (now smaller) and the divested entity (starting from scratch) typically fall into lower volume tiers. The parent loses its volume-based discount on the remaining licence base. The divested entity starts negotiations without negotiating history or volume credentials.

Mitigating the discount cliff requires proactive commercial strategy: negotiating with SAP before the transaction closes to lock in pricing for both entities, structuring the TSA to preserve parent pricing during the transition period, and — where possible — consolidating the divested entity's SAP requirements into a single negotiation that demonstrates sufficient scale for meaningful discounts. Benchmarking SAP discounts against market norms is essential to avoid overpaying on the new entity's initial contract.

05Key Protective Clauses to Negotiate Before the Deal

The optimal time to address SAP licensing in a divestiture is before the transaction closes — ideally during due diligence, when the target's SAP estate can be audited and a licensing strategy developed. Clauses to negotiate with SAP include: a TSA cost cap that prevents SAP from increasing support fees during the transitional period; a licence transfer consent clause that pre-authorises transfer of specified licences to the divested entity at a defined fee; a new entity commercial terms commitment where SAP agrees to offer the divested entity volume pricing consistent with its projected user count; and indemnity coverage in the transaction agreement ensuring the seller indemnifies the buyer for any SAP licence compliance claims arising from the transition period.

Internal protective steps include conducting a complete licence inventory before announcement (understanding exactly which users, modules, and integrations are in scope for the carve-out), creating a clean technical separation plan so that systems are properly partitioned and access is controlled from Day One, and engaging independent SAP licensing advisors who can assess the compliance position and advise on transition options without the commercial conflict of interest that SAP's account teams bring.

06Cloud and S/4HANA Considerations in Divestitures

The migration trend toward SAP S/4HANA and SAP's cloud portfolio introduces additional complexity in divestitures. S/4HANA Cloud subscriptions cannot be split — the contracting entity owns the subscription, and the carved-out entity must establish a new agreement. If the parent is mid-migration to S/4HANA, a carve-out can freeze the programme for the divested unit while the parent completes the migration, creating a technical debt problem where the divested entity inherits an unsupported ECC instance. RISE with SAP, SAP's cloud transformation programme, is tenant-specific and cannot be transferred — each legal entity requires its own RISE agreement. For divestitures involving significant cloud investment, modelling the total cost of establishing independent cloud agreements — including the lost amortisation of pre-paid cloud credits — is essential for accurate transaction valuation.

07Post-Divestiture SAP Compliance Risk

Divestitures are among the highest-risk events for SAP licence compliance. SAP's licence measurement process (the USMM tool) captures total system usage across all connected systems and entities. In a poorly managed separation, the divested entity may continue to access the parent's SAP systems after close — through shared interfaces, inherited user IDs, or un-decommissioned integrations — creating compliance exposure for both parties.

Common post-divestiture compliance failures include: user accounts for divested-entity employees remaining active in the parent's SAP system (they are now unlicensed third-party users); interfaces between the divested entity's systems and the parent's SAP instance (creating indirect access exposure); and shared master data environments where the divested entity continues reading or writing to the parent's SAP data (treated by SAP as unauthorised access). Engaging independent audit defence advisors immediately after transaction close, before SAP conducts any licence measurement, is strongly recommended.

08A Practical Divestiture SAP Checklist

Before announcement: Complete a full SAP licence inventory for the carve-out scope. Identify all cloud subscriptions, integrations, and indirect access points. Model the volume discount impact on both entities. Engage independent SAP licensing counsel.

During negotiations: Negotiate TSA terms with SAP that bridge the gap to new licence establishment. Agree pre-emptive licence transfer terms or new entity pricing commitments with SAP before close. Include SAP licensing representations and indemnities in transaction documents.

At close: Execute the TSA immediately. Freeze user provisioning changes pending technical separation. Activate the divested entity's new SAP tenant or licences. Document the licence position as of Day One.

Post-close: Complete technical separation within the TSA window. Conduct a clean licence measurement for both entities. Negotiate the new entity's long-term SAP agreement with market benchmarks. Consider engaging SAP contract negotiation specialists to establish favourable long-term terms for the divested entity.