Divesting a Business Unit Running SAP: Licensing and Contract Strategies

Why SAP Divestitures Are Uniquely Dangerous

SAP actively monitors public M&A announcements and uses corporate restructuring events as an opportunity to initiate licence audits or renegotiate commercial terms. When SAP's account team learns that one of its customers is selling a business unit, the immediate internal action is a review of the licence position: How many users and licences are attributable to the divested unit? Are there any DDLC-generating integrations running under the parent contract? Is the licence base sufficient to cover the transition period?

The answers almost always reveal a gap — and SAP's commercial team will seek to monetise that gap. The parent organisation, focused on deal execution, is typically poorly positioned to defend a licence claim simultaneously. The divested entity, newly independent and without its own SAP contract, cannot legally use SAP on the day after closing without a transitional arrangement. The buyer, who acquired the business on the assumption that SAP was included in the deal, faces an unexpected licensing cost before the ink is dry.

This convergence of vulnerabilities is not accidental. SAP's contract structure is designed to ensure that every entity touching SAP software has a separate, direct relationship with SAP — and that relationship must be established at market rates, without the discount history of the parent contract. Understanding how to navigate this structure in advance of a divestiture is the difference between a managed transition and an unbudgeted SAP bill of several million dollars.

The Five Critical Contract Issues in Any SAP Divestiture

1. Transitional Service Agreement (TSA) Licence Coverage

The most immediate issue in any divestiture is the Transitional Service Agreement (TSA) — the contract under which the parent organisation continues to provide operational services, including SAP access, to the divested entity for a defined period post-close. TSAs for SAP typically run 12 to 18 months, covering the period required for the divested entity to implement its own SAP environment or migrate to a different ERP solution.

The critical requirement is that the TSA period must be explicitly covered by a licence amendment from SAP. Without SAP's written consent, the parent providing SAP access to the divested entity after the legal separation is providing access to a third party under the parent's contract — which constitutes a breach of SAP's licence terms. SAP's standard contract language is unambiguous: licences cover the named customer entity and its affiliates. Once the divested entity is no longer an affiliate, the parent's contract no longer covers it.

Securing a Transitional Use Clause before the deal closes requires the parent to approach SAP with a specific request: written confirmation that the existing contract permits continued access for the named divested entity for a defined TSA period. SAP will typically grant this permission subject to a commercial arrangement — often a time-limited licence fee for the transitional period. Negotiating this arrangement in advance of closing gives the parent more leverage than requesting it post-close when operational continuity is at stake.

2. Licence Transfer Rights and SAP's Consent Requirement

SAP's licence agreements are fundamentally non-transferable without SAP's explicit written consent. This means that a parent organisation cannot simply carve out the SAP licences used by the divested unit and assign them to the buyer as part of the asset transfer. SAP must approve any licence transfer, and it does so at its own discretion, in its own commercial interests.

In practice, SAP approval for a licence transfer is obtainable, but it comes with conditions. SAP will typically require: a formal licence measurement to establish the scope of the transfer; an audit of any over-deployment that may exist in the transferred estate; a new licence agreement between SAP and the buyer entity (not an assignment of the existing agreement); and pricing for the transferred licences that may not reflect the discounts embedded in the parent's long-standing agreement.

The strategic objective for the parent is to negotiate the licence transfer terms — including discount preservation for the buyer and amnesty for any transitional compliance gaps — during the deal negotiation process, when the parent still has leverage as SAP's primary commercial relationship. Post-close, the leverage transfers to the buyer, who typically has a much weaker negotiating position with SAP as a new, standalone customer.

3. Cloud Subscription Assignment and Novation

SAP's cloud applications — SuccessFactors, Ariba, Concur, and any BTP-based solutions — present a distinct challenge. Unlike perpetual licences, which in theory can be transferred (with SAP consent), cloud subscriptions are contracted on a per-subscribing-entity basis. There is no concept of a partial assignment of a cloud subscription. The subscription covers the parent entity and its affiliates; once the divested entity is no longer an affiliate, it falls outside the subscription scope.

For SuccessFactors, this means the divested entity's employees — still being processed through SuccessFactors during the TSA period — are potentially outside the contractual coverage on day one post-close. For Ariba, purchase orders and invoices processed by the divested unit continue to count against the parent's transaction volume even after the legal separation, creating a period of phantom usage. For Concur, expense reports submitted by employees of the divested entity are processed under the parent's subscription without authorisation.

The resolution is a novation — a new contract established between SAP and the buyer entity, replacing the parent's cloud subscription for the divested entity's users. Novation requires SAP's consent, will be priced at current market rates without the parent's discount history, and must be timed to coincide with the legal separation rather than occurring weeks or months later. The buyer's due diligence should include a full inventory of cloud subscriptions in use by the divested entity and a realistic cost estimate for standalone subscription contracts at arm's length pricing.

4. Digital Access and DDLC During the Transition

During the TSA period, the divested entity continues to generate digital documents in the parent's SAP environment through integrated systems — HR portals, payroll engines, procurement platforms, and any other third-party tools that connect to SAP. These documents are generated under the parent's contract and contribute to the parent's DDLC counter.

The Digital Document Licence Charge (DDLC) implications of a TSA period are rarely assessed during deal planning. An 18-month TSA covering 2,000 employees of the divested entity could generate several hundred thousand SAP documents — with DDLC implications that neither the parent nor the buyer has modelled. When SAP conducts its post-merger audit (a near-certainty within 18 months of a significant transaction), the DDLC generated during the TSA period will be claimed as the parent's liability unless explicitly excluded by the TSA licence arrangement.

Negotiating a carve-out from DDLC liability for documents generated by the divested entity during the TSA period — with explicit language in the licence amendment from SAP — is a critical but frequently overlooked element of divestiture contract management.

5. Price Protection for the Post-Divestiture Parent

After the divestiture, the parent organisation retains its SAP contract but with a materially smaller user count and potentially a smaller licence base. SAP's contract terms typically include a maintenance floor — a minimum annual maintenance fee that does not reduce proportionally when the licence base shrinks. This floor means that the parent may pay the same or nearly the same annual maintenance after the divestiture as it did before, despite having significantly fewer users and licences.

Negotiating maintenance floor relief as part of the divestiture licence arrangement is essential for the parent's post-transaction SAP economics. SAP is unlikely to offer this relief voluntarily — the maintenance floor is one of SAP's most profitable contract mechanisms — but it can be negotiated as part of the overall TSA and transfer arrangement, particularly when the parent is offering SAP a new commercial relationship with the buyer entity as a quid pro quo.

The parent should also negotiate that the post-divestiture discount percentage on the retained licence base is preserved. SAP's default position is that a smaller licence base commands a smaller discount — moving the parent from, say, a 45 percent discount on a $5 million licence base to a 35 percent discount on a $3 million retained base. Explicit discount preservation language in the contract amendment protects against this ratchet.

RISE with SAP and Divestiture Complexity

Organisations running RISE with SAP face additional complications during a divestiture. RISE is structured as a single subscription covering the entire customer entity, priced on headcount tiers. Carving out a business unit from a RISE subscription is not a straightforward user-count reduction — it requires a contract amendment, SAP's agreement to a modified headcount tier, and a determination of whether the divested entity's headcount falls within the scope of any existing RISE provisioned environment.

If the divested business unit runs on the same RISE instance as the parent, the technical separation — spinning up a distinct S/4HANA environment for the buyer — is a significant infrastructure and implementation project, independent of the licensing question. The buyer will need its own RISE subscription, its own S/4HANA instance, and a data migration programme to extract its records from the shared environment.

The RISE amendment also triggers a review of the headcount tier. If the parent drops below a tier threshold after the divestiture, the next RISE renewal may occur at a lower headcount band — reducing the annual subscription cost. SAP will not proactively offer this reduction; the parent must negotiate it explicitly during the amendment process.

Timing: Why Pre-Deal Engagement with SAP Is Non-Negotiable

The single most consistent finding across the SAP divestiture engagements we advise on is that organisations that engage SAP before the deal closes achieve materially better outcomes than those that engage post-close. The reasons are structural: pre-close, the parent is SAP's primary commercial relationship and the deal is still being structured. SAP's account team, motivated to protect and expand the relationship through the transition, will negotiate constructively on TSA terms, licence transfer conditions, and price protection. Post-close, the parent is a smaller customer and the buyer is a new, unknown one — SAP's account team has limited incentive to offer concessions to either party.

Pre-deal engagement does not require disclosing sensitive M&A details prematurely. The initial engagement can be framed as a commercial review — exploring TSA provisions, hypothetical separation scenarios, and the range of transfer terms SAP would support under various circumstances. SAP's account team will draw the inference, but the commercial conversation can proceed without formal M&A disclosure until the appropriate point in the deal timeline.

The practical timeline recommendation: SAP licensing counsel should be engaged at the same time as legal and financial due diligence commences — typically 60 to 90 days before expected signing. The goal is to have a draft TSA licence amendment and licence transfer terms agreed in principle with SAP before the deal is announced, so that the closing process is not delayed by SAP negotiations running in parallel with regulatory and commercial closing conditions.

Checklist: SAP Divestiture Pre-Close Requirements

• Inventory all SAP contracts covering the divested entity: Identify every contract covering the business unit — ECC/S/4HANA, RISE, SuccessFactors, Ariba, Concur, BTP, and any specialist modules. Each requires a separate assessment of transfer or novation options.
• Run a DDLC mapping for the divested entity: Identify all third-party integrations generating SAP documents attributable to the divested unit, quantify annual volumes, and assess DDLC liability for the TSA period.
• Negotiate a Transitional Use Clause with SAP: Secure written SAP consent for continued access by the divested entity during the TSA period, with explicit DDLC carve-out language.
• Negotiate licence transfer or novation terms: Agree the commercial framework for any perpetual licence transfer or cloud subscription novation, including discount preservation and audit amnesty for the transitional period.
• Negotiate parent maintenance floor relief: Secure a reduction in the maintenance minimum for the post-divestiture parent, and confirm that the existing discount percentage is preserved on the retained licence base.
• Include SAP representations in the purchase agreement: Ensure the purchase agreement includes representations covering the SAP licence position, the TSA terms, and the buyer's right to standalone SAP access at agreed terms.