SAP M&A Licensing

Managing SAP Licensing During Mergers, Acquisitions & Divestitures Non-Transferability, Carve-Outs, TSAs, and Consolidation Strategies

SAP licences are contractually non-transferable without SAP's consent. When companies merge or split, those agreements do not automatically adjust. This playbook covers on-premise perpetual licences, cloud subscriptions, carve-out strategies, TSA planning, merger consolidation, negotiation leverage, and audit defence for every M&A scenario.

Non-Transferable
SAP licences cannot be transferred without written consent.
12-18 Months
Typical TSA window for transitional system access.
Elevated Risk
M&A events are known SAP audit triggers.
~22%
Annual maintenance on stranded shelfware post-split.
SAP Knowledge Hub SAP Licensing Guide M&A Licensing Playbook
Plan Licensing Before the Deal Closes

The outcome of every M&A licensing scenario depends on what you negotiate before the event, not after. Companies that include carve-out clauses and TSA provisions in their SAP contracts save millions compared to those scrambling post-close. SAP monitors divestitures and mergers as known audit triggers. See also: SAP Audit Survival Guide and SAP Negotiation Strategies.

01

SAP's Non-Transferability Rule

Licence TypeTransfer RuleImplication for M&A
Perpetual on-premiseLicensed to a specific "Licensee" (your company, often including majority-owned affiliates). Cannot be sold, given, or assigned to a different company without SAP's written consent.A divested entity that is no longer under the original licensee's control has no right to use the SAP software. Even with servers inherited, no licence exists without formal transfer.
Cloud subscriptionsSuccessFactors, Ariba, Concur, Fieldglass contracted on a per-subscribing-entity basis. Cannot be split or transferred without consent. No concept of "partial assignment."If part of the business leaves, those users cannot continue under the old contract. SpinCo must sign a new subscription. See SAP Concur Licensing Guide.
RISE with SAPSubscription tied to specific legal entity. Change-of-control provisions may terminate or require renegotiation.Acquiring or divesting a RISE customer requires SAP consent and likely contract novation. See RISE with SAP Tiers.
02

Divestiture Scenarios

ScenarioSAP Licence ImplicationsRecommended Action
Parent retains majority stake in SpinCoSpinCo still an affiliate. Can use Parent's SAP temporarily. Licence rights remain with ParentCo.Use this window to plan separation. Negotiate eventual transfer or new licences before affiliate status ends. Include a TSA clause.
SpinCo fully separated (sold to new owner)SpinCo not covered by Parent's licences. Must stop using unless SAP allows. ParentCo has excess shelfware licences.Negotiate new licence for SpinCo or assignment of some licences. Implement TSA or partner solution for interim. ParentCo seeks to down-scope maintenance. See Reducing SAP Shelfware.
Pre-agreed transfer clause existsSpinCo can take those licences with SAP's consent per contract terms.Execute transfer formally. Ensure SpinCo signs its own support agreement. ParentCo reduces counts accordingly.
No transfer rights, no new licence (risky)SpinCo continues accessing without legal cover. Both companies out of compliance.Not recommended. If this occurs, urgently engage SAP. Always avoid through TSA planning.
Cloud apps shared pre-splitShared environment must be split. SpinCo needs its own instance/licence.Arrange data migration to new tenant. Get short-term SAP approval for continued access. Sign new subscriptions at closing.
03

Carve-Out and Assignment Rights

Protection to NegotiateWhat It Does
Transfer/assignment rights for divestitureClause allowing assignment of licences or a portion of the agreement to a divested entity. E.g., transfer of up to X% of user licences at the same discounted rate. Ensures divested business can continue using SAP without immediate repurchase and spares the parent from shelfware.
Transitional use clauseAllows the parent to continue providing SAP system access to the divested unit for a defined period (typically 6-18 months). Key terms: scope of use, duration, fees (if any), and requirement for divested entity to agree to original contract terms during the period.
Cloud contract assignment provisionLanguage in SuccessFactors/Ariba/Concur agreements allowing contract assignment to a surviving entity or buyer, with SAP's consent not to be unreasonably withheld. Prevents SAP from using a merger as an excuse to force a contract reset.
Change-of-control protectionProvision that a change of ownership (acquisition) does not automatically terminate the contract or trigger renegotiation. Protects the acquiring entity from losing existing discounts. See SAP Contract Negotiation Service.
04

TSA and Transitional Solutions

ApproachHow It WorksKey Consideration
SAP-consented TSA useWork with SAP for formal agreement allowing SpinCo's use during transition. SAP may issue temporary licence or amend ParentCo's contract for the TSA period. SAP may charge a fee (often 20% of divested unit's licence value for 12 months).Negotiate at or before closing. If you have a pre-negotiated TSA clause, just notify SAP and follow the contract terms.
Partner or SAP-hosted solutionMove divested operations temporarily onto an SAP partner's infrastructure. SAP Partner Managed Cloud or HANA Enterprise Cloud where partner hosts and "leases" licences as part of the service.Avoids rushed perpetual licence purchase. Uses subscription model to cover the interim. RISE with SAP could also serve this purpose.
Accelerated new licence purchaseSpinCo purchases its own SAP licences (perpetual or RISE subscription) effective at closing. No transitional overlap needed.Fastest to achieve clean separation but requires advance planning and budget. SpinCo may pay higher per-user rates without ParentCo's volume discount. See SAP Pricing Benchmarks.
05

Merger and Acquisition Consolidation

M&A ScenarioLicence ImplicationsRecommended Action
Two SAP customers mergeCombined use not automatically allowed. Each contract limited to its original company. Must consolidate agreements.Negotiate unified contract leveraging combined scale. Keep usage separated during interim. Retire duplicative licences. See S/4HANA Licensing Guide.
SAP customer acquires non-SAP companyNew users need SAP licences. Original contract may cover affiliates but additional licences are needed.Quantify additional usage. Purchase new user licences. Leverage volume for better pricing. Time with integration milestones.
Non-SAP acquirer inherits SAP operationChange-of-control may trigger contract renegotiation or termination. Acquirer has no SAP relationship.Seek consent and novation during due diligence. Audit target's compliance. Negotiate new contract or plan migration off SAP as leverage.
Combining licence portfoliosOpportunity for volume discounts, enterprise agreements, and maintenance rationalisation. Risk of duplicate payments.Leverage increased scale. Negotiate ELA or flex agreement. Co-terminate contracts. Demand price protections. See ECC-to-2033 Transition Option.
06

Real-World M&A Outcomes

ScenarioOutcomeFinancial Impact
Spin-off with pre-negotiated clauseGlobal manufacturer transferred 300 of 2,000 SAP user licences to SpinCo at the same discounted rate. Parent terminated maintenance for transferred portion.Saved several million dollars vs. no transfer rights scenario.
Divestiture without rightsEnergy company divested a division without licence transfer provisions. SAP charged 20% transition fee. SpinCo purchased fresh licences at 40% higher per-user pricing. Parent stuck with 500 excess licences.Estimated $5M in combined extra costs.
Merger leading to enterprise agreementTwo mid-sized companies (each ~$2M SAP spend) merged and proposed a 7-year RISE subscription. Received 30% lower rate plus additional modules at no extra cost.Significant savings over the period. Eliminated two-contract complexity.
Failed licence integrationLarge acquisition. Failed to consolidate contracts for 3+ years. Informal cross-use discovered by SAP audit. ~200 unlicensed users on each system.$1.5M compliance bill + $500K/year wasted maintenance on 2,000 excess users.
07

Recommendations for SAM and Procurement Teams

#ActionWhat to Do
1Review SAP contracts earlyAs soon as a deal is on the table, review all SAP agreements. Identify clauses on assignment, change of control, affiliate use, or divestiture. Understanding your contractual position informs how you approach SAP.
2Negotiate TSA and carve-out rights in advanceInclude provisions proactively: permission for SAP access to divested entity for defined months, right to transfer licences with SAP's consent not to be unreasonably withheld. See SAP Negotiation Strategies.
3Perform licence due diligenceIf you are the buyer, assess the target's SAP licensing. Request contract copies and recent audit reports. Evaluate compliance. If the target needs a costly true-up, reduce the purchase price. For divestitures, map which licences are attributable to the carved-out unit.
4Plan and document interim operationsDetermine TSA duration and scope. Formalise with SAP through a licence addendum or transitional licence. Mark end dates. Do not let transitional arrangements drag on undocumented. See SAP Audit Trends 2026.
5Leverage M&A for better SAP termsDemand volume discounts from combined scale. Negotiate enterprise agreements. Rationalise maintenance. Co-terminate contracts. Time negotiations around SAP's quarter/year-end for maximum incentives.
6Engage independent licensing expertiseIndependent advisors know what concessions SAP has given other clients in similar situations. Their cost is far lower than what you save. See SAP Licence Optimisation Services.
7Document everythingKeep copies of contracts, SAP communications granting permissions, and negotiation notes. If SAP verbally agrees to something, get it in writing. Verbal assurances do not hold up in an audit. Only contractual terms do.
FAQ

Frequently Asked Questions

Not by default. SAP's standard contracts contain strict non-assignment clauses. You cannot transfer without SAP's written consent. If your contract includes a pre-negotiated carve-out clause, you can execute the transfer per those terms. Otherwise, negotiate directly with SAP, which typically involves fees or new purchases for the separated entity.

Cloud subscriptions cannot be partially assigned. The spun-off entity needs its own tenant and contract. SAP may agree to novate if an entire business unit with a distinct subscription is sold, but shared subscriptions require the spin-off to sign a new agreement. Coordinate with SAP early for a transition period. See SAP Ariba Licensing Guide.

Yes. SAP monitors customer developments. These events frequently cause compliance gaps: unlicensed cross-use, transferred systems without licensing, or dramatic user count changes. Being proactive significantly reduces audit risk. See SAP Audit Survival Guide.

TSA periods typically range from 6 to 18 months, with 12 months common. Duration depends on your negotiations with SAP and contract provisions. SAP may charge a transitional fee, usually a percentage of the divested unit's licence value, for the interim use period.

If you acquire a company using SAP, you inherit any compliance problems. Unlicensed users, misclassified user types, indirect access issues all become the new owner's responsibility. Always perform a thorough SAP licence audit during due diligence. Include compliance representations in the purchase agreement. See SAP Compliance Tools Guide.

Absolutely. Mergers create significant leverage. As a combined, larger customer, demand better volume discounts, negotiate enterprise agreements, rationalise maintenance, and consolidate contracts on more favourable terms. Time negotiations around SAP's fiscal year-end. See SAP Contract Negotiation Service.

The parent is often stuck with shelfware, paying 22% annual maintenance on licences no longer needed. SAP generally does not allow mid-term maintenance reductions. Strategies include negotiating drops at next renewal, swapping unused licences for other products, or including shelfware reduction in a broader renegotiation. See Reducing SAP Shelfware.

Navigate SAP Licensing Through M&A With Confidence

Redress Compliance provides independent SAP M&A advisory: licence due diligence, carve-out clause negotiation, TSA planning, merger consolidation, and audit defence. Former SAP licensing specialists. Fixed-fee engagements.

SAP Contract Negotiation Service

Related Resources

FF

Fredrik Filipsson

Co-Founder, Redress Compliance

Two decades of enterprise software licensing expertise, including hands-on experience at IBM, SAP, and Oracle. Advises Fortune 500 enterprises on SAP M&A licence transitions, audit defence, contract negotiation, RISE advisory, and digital access compliance. His team includes former SAP licensing specialists who understand SAP's audit methodologies and sales practices from the inside.

← Back to SAP Knowledge Hub

Facing an M&A Event Involving SAP?

Independent SAP M&A advisory: licence due diligence, carve-out negotiation, TSA planning, merger consolidation, and audit defence. Fixed-fee engagements. No vendor conflicts.

SAP Contract Negotiation Book a Consultation
Always-On Advisory

🛡️ Vendor Shield — Subscription Advisory

Continuous, always-on advisory coverage across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, and more. One subscription. Every vendor. Always prepared, never outmanoeuvred.

Learn About Vendor Shield Multi-vendor protection
Licensing Intelligence

Stay Ahead of Vendor Moves

Monthly licensing intelligence, audit alerts, and negotiation tactics from our advisory team. Trusted by 1,000+ enterprise leaders.

Subscribe Free No spam. Unsubscribe anytime.
Explore All Vendor Hubs