Divesting a Business Unit Running SAP: Licensing and Contract Strategies

Why SAP Divestitures Are Different

Most enterprise software agreements are written for a single legal entity. When a business unit is sold, that assumption collapses. SAP's standard licensing agreements prohibit the assignment or transfer of licences to a third party without SAP's explicit written consent. This is not a boilerplate clause — it is the central commercial mechanism that gives SAP leverage at precisely the moment when your negotiating position is weakest: a deal in progress, a timeline fixed by M&A milestones, and a business that depends on SAP continuity to operate.

The challenge compounds rapidly. The selling organisation discovers it cannot simply hand the SAP system over to the buyer. The SpinCo discovers it cannot legally access SAP until a new agreement is in place. Both parties discover that SAP is fully aware of the situation and prices accordingly. Deals that close without a licensing strategy regularly produce six- or seven-figure remediation costs that neither the acquisition model nor the transition budget had anticipated.

The asymmetry is stark: SAP knows the separation is happening, knows you require continuity, and knows the timeline is dictated by deal close, not commercial readiness. Buyers who enter licensing negotiations after close with no prior planning have already surrendered the most powerful positions available to them.

The Four Core Licensing Problems in Any Divestiture

Problem 1: The Transfer Prohibition

SAP's licence agreements prohibit assignment without prior written consent across all licence types — perpetual on-premise agreements, RISE with SAP subscriptions, and cloud agreements alike. When the divested entity becomes a separate legal entity, it cannot use the parent's SAP licences even if it is accessing the same physical systems on the same physical instance, without a contractual arrangement that explicitly authorises that access.

SAP's compliance team monitors for ownership changes. Deal announcements, regulatory filings, stock exchange disclosures, and press releases are all reviewed. Organisations that proceed without addressing this exposure face retroactive licence claims that SAP characterises as unlicensed use and prices at its highest applicable rates — applied to the entire period of non-compliant access.

Problem 2: The Volume Threshold Collapse

Enterprise SAP agreements are priced on scale. A 30,000-user estate negotiated as a single relationship will carry volume discounts of 40 to 65 percent off list. When that estate splits into two entities — one retaining 20,000 users and one carrying 10,000 — both entities lose the pricing tier that supported the original discount. SAP treats each as an independent pricing event.

The parent's remaining licences are repriced at a smaller volume, typically at a worse effective discount than before. The SpinCo, as a new customer without negotiating history, receives minimal concessions — in some cases, as little as 15 to 20 percent off list compared to the 50-plus percent the parent secured over years of commercial relationship. In practice, the combined SAP cost across both entities after separation is consistently 25 to 40 percent higher than the unified pre-split cost. This figure rarely appears in acquisition models. It should be a standard line item in every divestiture valuation.

Problem 3: The Transitional Service Agreement Trap

The most common near-term solution is a Transitional Service Agreement (TSA), under which the parent continues providing SAP access to the separated entity for a defined period, typically six to eighteen months post-close. SAP must formally authorise this arrangement — and it charges for doing so.

SAP typically levies a fee of 10 to 20 percent of the divested unit's annual licence value for the TSA period. On a divested operation carrying a €5 million annual SAP licence cost, this represents €500,000 to €1 million in additional fees simply to maintain access during the transition. The fee is documented as a transition cost, but SAP's account teams rarely surface it proactively. It emerges when the TSA is formally requested, which typically happens after deal close — when your negotiating leverage is at its lowest point. Planning the technical separation in parallel with the commercial negotiation is not optional if you want to control this cost.

Problem 4: The S/4HANA Migration Complication

Many enterprises entering a divestiture are simultaneously managing S/4HANA migration planning. The 2027 end of mainstream maintenance for ECC EHP 6–8 creates genuine urgency — organisations remaining on ECC after that date face extended maintenance fees equivalent to approximately 24 percent of licence value, compared to 22 percent for standard maintenance, plus a 2 percent annual uplift on top. A divestiture in this environment creates a worst-case scenario: two separate entities each facing migration deadlines, each negotiating independently with SAP, each losing the combined commercial weight that existed before separation.

According to Gartner data from late 2024, only 39 percent of SAP's 35,000 ECC customers had licensed S/4HANA. Divestitures are a meaningful factor in delayed migration decisions, as organisations struggle to determine which entity owns the migration project, how costs are allocated across the separating businesses, and how migration credits — which decrease by approximately 10 percent per year of delay — are assigned when a single estate becomes two.

What SAP Will and Will Not Permit

SAP has structured its agreements to maximise commercial leverage at moments of corporate transition. Understanding the boundaries is the prerequisite for identifying where negotiation is possible and where it is not.

SAP will permit a TSA arrangement, but it charges for it. The fee is negotiable — particularly when the SpinCo brings a commitment to become an independent SAP customer with a clear long-term agreement in place. Organisations that arrive at TSA negotiations with a defined three-year commercial roadmap for the SpinCo consistently achieve fees in the lower end of the 10 to 15 percent range rather than the 20 percent ceiling.

SAP will permit the partial transfer of licences to a SpinCo if the original enterprise agreement contains carve-out language — but only if that language was negotiated proactively, before the divestiture event was announced. Retroactive requests to introduce carve-out rights are granted rarely and on commercially punitive terms. The window for securing them is the original licence negotiation or the most recent major renewal, not the press release announcing the sale.

SAP will not permit informal continuation of shared access where no TSA or explicit contractual arrangement exists. Shared systems, integration points, and intercompany processes that touch SAP all require documented licence coverage during the transition period. SAP's compliance team specifically examines intercompany data flows and system access patterns following ownership changes — and it knows which companies are in the middle of corporate transactions.

Negotiation Strategy: Protecting Both Entities

Engage SAP Before Deal Close

The optimal time to open SAP licensing discussions is before the transaction closes — ideally during the due diligence phase. This is when the selling entity retains the most commercial leverage. SAP wants to preserve the revenue relationship with both the parent and the future SpinCo, and deal urgency has not yet compressed the negotiating window. Organisations that initiate SAP discussions three to six months before close consistently secure better TSA terms, lower SpinCo pricing, and carve-out provisions that would be commercially unavailable post-close.

Frame the SpinCo as an Incremental Revenue Opportunity

SAP will reduce TSA fees and improve SpinCo pricing when the SpinCo commits to a multi-year agreement — particularly one that includes a defined roadmap toward S/4HANA or RISE with SAP. A SpinCo that enters discussions with a clear three-year spend commitment is a fundamentally different commercial proposition than one that arrives asking for temporary access with no long-term commitment. Framing the SpinCo as an incremental revenue opportunity for SAP, rather than a compliance liability, is the most effective single lever available in these negotiations.

Negotiate Carve-Out Rights in Every Major Renewal

If your organisation anticipates any portfolio activity — divestitures, spin-offs, joint ventures, or partial disposals — negotiating carve-out rights into every major SAP renewal eliminates SAP's primary leverage at the moment of separation. Language that allows a defined percentage of licences to be transferred to a separated entity with written notice, rather than requiring prior written consent for each transfer, changes the entire commercial dynamic. One global industrial group secured the right to reassign up to 20 percent of its total SAP user estate to a separated entity without requiring SAP's prior consent, which allowed it to complete a major division sale with zero additional transition fees.

Run a Full Licence Position Before Separation

Divestitures surface latent compliance exposures that have accumulated across years of organic growth. Indirect access risks, over-deployed modules, and incorrectly classified user licence types that were commercially manageable under a single large agreement become individually significant when split across two smaller entities. Running a full internal licence measurement — using SAP's USMM and LAW tools — before the separation is formally announced gives both parties a clean baseline and removes SAP's ability to use compliance findings as additional leverage during TSA negotiations.

What SAP Does Not Volunteer

There is a specific commercial detail in SAP divestiture negotiations that SAP account teams consistently fail to disclose: in some TSA negotiations, the percentage fee is applied against the undiscounted list price of the divested unit's licence value, not against the contracted price. If your organisation secured a 55 percent discount on its SAP estate, applying a TSA percentage to the list-price equivalent produces a fee that is dramatically higher than the percentage implies. Always specify in writing — before any TSA fee is agreed — that the calculation is applied exclusively against the contracted annual licence cost, not the list equivalent.

SAP's fiscal year ends on 30 September. Its most commercially productive quarter (Q4) runs from July through September, when account teams have maximum discount authority and strongest incentives to close large deals. Divestiture-related licence discussions that can be structured to conclude in SAP's Q3 (April to June) or early Q4 benefit from pricing authority that is genuinely unavailable in other quarters. Deals that land in October or November, immediately after SAP's fiscal year-end, face account teams with freshly reset targets and no immediate incentive to concede anything.

The Cost of Doing Nothing

A European industrial group completed a major division sale in 2024 without engaging SAP prior to close. The SpinCo continued operating on the parent's SAP environment under an informal internal arrangement. Fourteen months after close, SAP's compliance team identified the arrangement during a routine system access review and issued a backdated licence claim covering the full period of shared use. The claim was calculated against list pricing — the most aggressive rate available to SAP under the circumstances — and the eventual settlement cost approximately 30 percent more than a proactively negotiated TSA would have cost for the identical period. The parent also faced a compliance finding on its remaining estate, as the shared-access period complicated the licence baseline measurement for both entities simultaneously.

This outcome is not exceptional. The organisations that incur the highest divestiture-related SAP costs are consistently those that treated licensing as an IT afterthought rather than a commercial negotiation requiring dedicated specialist attention from the outset of the deal process.

The Bottom Line on SAP Divestitures

Divesting a business unit that runs SAP requires a commercial strategy running in parallel with the M&A process itself — not appended to it after close. The licensing questions at stake — transfer restrictions, TSA costs, volume repricing, compliance baseline, migration credit allocation — are not SAP technicalities. They are deal economics. Each is negotiable when approached with the right timing, the right commercial framing, and the right specialist input. Left unaddressed, they become post-close surprises that erode deal value on both sides of the transaction in ways that no post-close negotiation can fully recover.