Key Takeaways
- M&A events — acquisitions, divestitures, spin-offs, and mergers — are among the most complex SAP licensing scenarios an enterprise will face, and SAP's default response is to charge you for both entities.
- SAP's standard licence agreements include "change of control" clauses that can trigger immediate compliance obligations and give SAP leverage to force a commercial renegotiation.
- Right-sizing requires a forensic audit of both landscapes: user counts, user classifications (Professional, Limited Professional, FUE), engines, packages, and Digital Access documents before any consolidation begins.
- Named User reclassification alone typically yields 20–35% licence cost savings in a post-merger environment where duplicate accounts and over-classified users are endemic.
- SAP will not proactively flag over-licensing — your contract team must build the case independently and negotiate from a position of documented evidence.
- Divestitures require a formal licence disaggregation process; SAP will not automatically release licences for the divested entity without specific contractual provisions.
- Independent advisory is essential: SAP's account team's interests are directly opposed to yours during M&A right-sizing.
A manufacturing conglomerate acquires a competitor. Both companies run SAP ECC. The combined entity now has two SAP landscapes, thousands of duplicate user accounts, overlapping contracts, and an SAP account executive who sees a once-in-a-decade commercial opportunity. Within months, if the new entity doesn't move decisively, they'll be paying for licences they don't need — and possibly facing an audit that uses the consolidation as cover for inflating the compliance gap.
SAP right-sizing after M&A is not a housekeeping exercise. It's a high-stakes commercial negotiation that determines whether the combined entity benefits from economies of scale in its licensing — or gets penalised for the complexity SAP's own contract structure created. Our SAP licence optimisation advisory has guided dozens of enterprises through post-merger right-sizing, and the patterns are consistent: enterprises that act fast with independent analysis save millions; those that rely on SAP's guidance overpay for years.
What Is SAP Right-Sizing After M&A?
SAP right-sizing in an M&A context means systematically aligning your SAP licence entitlement with your actual usage after a structural corporate change — whether that's an acquisition, a merger, a spin-off, a carve-out, or a full divestiture. The goal is to eliminate overpayment caused by duplicate licences, incorrectly classified users, unused Named User accounts, and engines or packages that belonged to the target company but are now redundant in the combined landscape.
It's distinct from standard licence optimisation in one critical way: M&A events create contractual triggers. SAP's standard Enterprise Licence Agreements (ELAs) contain change-of-control provisions that legally obligate you to notify SAP of ownership changes. Those notifications, if handled poorly, open the door for SAP to demand a full commercial renegotiation — on SAP's terms, not yours.
Done correctly, right-sizing after M&A is an opportunity to consolidate onto fewer, more cost-effective licences, negotiate volume pricing benefits from the combined user base, shed licences associated with divested entities, and reclassify users who have been over-assigned to high-tier licence types. Our team has seen enterprises achieve 30–40% reductions in their SAP licence spend through a disciplined post-acquisition right-sizing programme.
⚠ SAP's Change-of-Control Clause
Most SAP ELAs require written notification to SAP within 30–90 days of a change of control. Failure to notify is itself a contractual breach. But notifying SAP without first completing your independent licence analysis is equally dangerous — it hands SAP's commercial team the initiative before you've built your own position.
The M&A Licensing Problem SAP Created
SAP's licence model was not designed with corporate simplicity in mind. Named User licences are tied to specific legal entities. Indirect access obligations attach to specific system landscapes. Engine-based licences often sit within contracts that have no automatic portability clause. The result is that every M&A event creates immediate licence complexity — and SAP's commercial team is trained to monetise that complexity.
In an acquisition scenario, the acquiring entity typically inherits the target's SAP contracts, which may have different pricing, different metric structures, and different T&Cs. Consolidating two separate ELAs into a single agreement requires SAP's consent — and SAP will use that consent process as a negotiating lever. "We can consolidate your contracts, but your licence count needs to increase to reflect the new user base" is a common SAP commercial play.
In a divestiture scenario, the problem is reversed. The divesting entity needs to separate the licences used by the divested business. SAP's contracts rarely contain clean licence portability clauses. Instead, SAP expects the divesting entity to continue paying for the full licence count while the divested entity negotiates its own new agreement — often at significantly higher prices than the original contract.
Our SAP licence compliance advisory regularly encounters enterprises paying for two full licence counts for 12–18 months post-divestiture, simply because they didn't know they could challenge SAP's position. The commercial logic SAP presents — "you signed for these licences, you continue to pay" — has significant contractual and practical vulnerabilities that independent analysis can exploit.
The Right-Sizing Framework: First Principles
Before any conversation with SAP's commercial team, you need a complete, independent view of your licence position across both entities. This means running USMM (User and System Measurement) across all relevant SAP systems, extracting the full LAW (Licence Audit Workbench) report from each landscape, and building a consolidated Effective Licence Position (ELP) that reflects actual usage — not contracted entitlement.
Step 1: Map the Combined Licence Landscape
Create a master inventory of every SAP contract across both entities: Order Forms, T&Cs, Master Agreements, and the attached Licence Metrics Schedules. Identify the licence types in each contract — Named Users by category (Professional, Limited Professional, Developer, Employee, ESS, FUE), Engines (ALE, ICH, APO), Packages, and any Digital Access entitlements. This is your contractual baseline.
Step 2: Run USMM Across All Landscapes
The USMM tool generates the system measurement file that SAP's auditors use to calculate your compliance position. In a post-M&A scenario, you need USMM output from every system in scope — including systems at the target company that may not yet have been brought under your IT governance. Understanding how USMM classifies users in each landscape is essential: the same user role can be classified differently depending on the system configuration, and those discrepancies are often exploitable.
Step 3: Build Your Independent ELP
The ELP — Effective Licence Position — compares what you're contracted to use against what you're actually using. In a post-merger environment, the correct ELP calculation must account for users who exist in both landscapes (and should only be counted once), users who are no longer active post-integration, and users who have been assigned to licence types that exceed their actual system usage. Our guide to building an SAP ELP covers the methodology in detail.
Is Your Post-M&A SAP Landscape Over-Licensed?
Most enterprises completing acquisitions or divestitures are paying 25–40% more than they should on SAP licences. Our SAP licence optimisation advisory identifies the exact savings available before you enter any commercial discussion with SAP.
Get Your Licensing ReviewedUser Reclassification: The Biggest M&A Savings Lever
Post-merger environments are characterised by licence inflation. The target company's IT team provisioned users based on the target's internal governance. The acquiring company's IT team applies its own standards. The result is a combined user base where a significant percentage of accounts are either duplicate (the same person in two systems) or over-classified (assigned to Professional when Limited Professional would suffice based on their actual transaction patterns).
Named User Professional licences typically cost 3–5x more than Limited Professional. A company with 10,000 users where 30% are over-classified as Professional is paying for 3,000 licences they shouldn't need. At typical SAP pricing, that's a seven-figure annual overpayment — and it compounds every year through SAP's annual support maintenance uplift of 22%.
Reclassification requires a transaction-level analysis of each user's SAP activity. Which T-codes are they executing? Are they posting documents or only reading? Are they creating master data or only consuming it? SAP's USMM classifies based on the highest-level role assigned to a user ID, not on what that user actually does. Our practical guide to SAP right-sizing after M&A covers the reclassification methodology in detail.
The Functional User Exception
FUE (Functional User Equivalent) licences apply to users who interact with SAP exclusively through simplified, single-purpose interfaces — for example, warehouse staff who only process goods receipts, or HR employees who only use ESS (Employee Self-Service) for leave requests. Identifying and reclassifying FUE-eligible users from the combined post-merger user base is frequently one of the highest-value actions in a right-sizing programme.
Divestiture Strategy: Protecting the Licence You Paid For
When divesting a business unit, the default SAP commercial position is that the divested entity must obtain its own SAP licence agreement — and the remaining entity continues to pay for its full contracted entitlement, with no reduction to reflect the loss of users. This position is almost never contractually unassailable, but it requires an evidence-based challenge to overcome.
The key questions to examine are: Does your Master Agreement contain a divestiture clause? If so, what are the mechanics for licence reduction? If not, what does the agreement say about changes to the legal entity? Does the contract define "use" in a way that can be argued to exclude the divested entity's users after the transaction closes?
In many cases, the contract is ambiguous, and SAP's position is a commercial gambit rather than a legal certainty. Enterprises that challenge with independent legal and licensing analysis regularly secure licence reductions of 15–25% following a divestiture. Our SAP contract negotiation team has negotiated divestiture licence adjustments across dozens of transactions.
✓ Case Reference: Post-Divestiture Licence Reduction
A global financial services group divesting a regional business unit was told by SAP that licence counts could not be reduced until contract renewal. Through independent contractual analysis and negotiation, our team secured a 22% reduction in Named User licences within 90 days of the divestiture closing — saving £4.1M over the remaining contract term. See our case studies for more detail.
Avoiding SAP Audit Traps During M&A
M&A events are among SAP's highest-probability audit triggers. SAP's audit team monitors change-of-control notifications, public M&A announcements, and USMM measurement changes that flag new systems appearing in an existing landscape. When SAP's audit team identifies an M&A event, they frequently launch a "supportive" measurement exercise that is, in practice, an audit — designed to establish a compliance gap that justifies a commercial conversation.
The three most common M&A audit traps are: new systems brought into the landscape without licence coverage (common when integrating a target's SAP environment), indirect access claims arising from the target's integration connections (third-party systems feeding SAP via APIs or batch jobs that weren't covered under the target's own licence), and engine counts that increase when the combined landscape exceeds the original contracted metric thresholds.
Defending against these traps requires pre-emptive analysis — ideally before the M&A transaction closes, as part of due diligence. Our SAP audit defence service provides specific M&A audit preparation, including pre-transaction licence due diligence, integration planning that minimises new compliance exposure, and post-close audit readiness.
Negotiation Strategy: Using M&A as Leverage
M&A events are not only risks — they're opportunities. A company that has just completed a significant acquisition is a materially different commercial prospect for SAP. Larger combined user base. More SAP products in use. A longer-term commitment to the SAP ecosystem as the integration proceeds. All of these factors give you leverage that pure renewal negotiations don't.
The most effective M&A negotiation positions consolidate the commercial discussion around three levers: first, the volume benefit from combining two licence sets should produce a price-per-user reduction; second, the integration commitment (if you're standardising on SAP across the combined entity) should produce multi-year price protection; third, the complexity of the M&A situation justifies a governance review that may surface credits, concessions, or price-lock terms that SAP would never offer in a standard renewal.
Critically, you should understand how SAP prices enterprise deals and the quarterly cycles that drive SAP's commercial team before entering any M&A-related negotiation. SAP's negotiating posture changes significantly based on where you are in SAP's fiscal year, and post-M&A negotiations give you the unusual advantage of being able to time your engagement strategically.
Don't Negotiate Your Post-M&A SAP Position Alone
SAP's account team enters every M&A commercial conversation with a clear objective: maximise revenue from the transition. Our independent SAP contract negotiation service ensures you enter the same conversation with an equally clear objective — and the evidence to achieve it.
Book a Free ConsultationSupport Cost Implications of M&A Right-Sizing
Every SAP licence carries a mandatory Enterprise Support obligation of 22% of licence value per annum. This means that reducing your licence count through right-sizing doesn't just save you the licence value — it saves you 22% of that reduction every year, compounding forward. On a €10M licence reduction, you save €2.2M per year in support costs alone, every year for the remaining contract term.
Post-M&A right-sizing therefore has a disproportionate ROI compared to tactical licence optimisation. The support cost tail amplifies every licensing decision. Our SAP support cost reduction advisory covers both the licence renegotiation component and the separate question of whether third-party maintenance alternatives are viable for the combined entity's stable, non-RISE SAP landscape.
Integration Planning: Licensing Must Come First
The most common mistake we see in post-merger SAP integration planning is treating licences as an IT infrastructure question rather than a commercial one. Integration teams focus on technical migration paths, data consolidation, and system harmonisation — all valid priorities. But licences are agreed at the start of the engagement or not at all. By the time the technical integration is complete, the commercial window for renegotiation has often closed.
The correct sequence is: licence analysis before technical planning, commercial agreement with SAP before system consolidation begins, and contract amendment secured before the first combined USMM measurement is submitted. Reversing this sequence — running USMM after the technical integration before any commercial agreement — gives SAP a measurement snapshot that shows a materially larger combined user base, and establishes that as the compliance baseline.
For enterprises planning S/4HANA migration as part of post-M&A integration, the complexity increases further. Our S/4HANA migration licensing advisory addresses the intersection of migration and M&A right-sizing — specifically how to avoid paying for legacy ECC licences and new S/4HANA licences simultaneously during the transition period.
Frequently Asked Questions
Does SAP automatically reduce our licence count when we divest a business unit?
No. SAP's default position is that licence reductions require a formal contract amendment, and SAP's commercial team will not initiate this process voluntarily. You must present a documented case for licence reduction — typically citing the contractual mechanism for changes to the legal entity's user base — and negotiate the amendment explicitly. This process can take 3–6 months and requires experienced independent support to execute effectively.
What is a change-of-control clause in an SAP ELA and how does it affect M&A?
SAP's change-of-control clause typically requires written notification to SAP within 30–90 days of any transaction that changes the ownership of the contracting entity by more than a defined threshold (usually 50%). The clause gives SAP the right to review the new entity's licence position and, in some agreements, to terminate or renegotiate the contract if the new parent entity does not meet SAP's contracting criteria. In practice, SAP rarely exercises termination rights, but uses the notification process to trigger a commercial review. The key is to notify only after you have completed your independent licence analysis and are prepared to negotiate.
Can we consolidate two separate SAP ELAs into one after an acquisition?
Yes, but the process requires SAP's consent and will be treated as a commercial renegotiation. SAP typically uses contract consolidation as an opportunity to eliminate favourable pricing terms or volume discounts from the older agreement. Before agreeing to consolidate, you should model the combined cost under both the existing contracts (maintained separately) and a consolidated contract, and negotiate from the option that produces the lower combined cost. In many cases, maintaining separate contracts short-term while negotiating a purpose-built consolidated agreement produces significantly better terms than a direct consolidation.
What SAP licences are most commonly over-counted in post-merger environments?
Named User Professional licences are the most common source of M&A over-counting, typically because the target company's governance classified users based on its own internal standards that don't align with the acquiring company's norms. The second most common category is Employee and ESS licences where users have been granted access to HR modules they don't actually use. Engine licences (particularly ALE and APO) are also frequently over-counted when the combined landscape has redundant integration paths that were maintained for business continuity during integration but are no longer actively used.
Should SAP licensing be included in M&A due diligence?
Absolutely, and it is consistently underweighted in standard due diligence processes. A target company's SAP licensing position — including any unresolved audit claims, over-classified users, indirect access exposure, or impending contract renewals — represents a material financial liability that directly affects deal valuation. We recommend including an independent SAP licence due diligence review as a standard component of enterprise M&A processes where the target has a significant SAP environment. This typically takes 3–4 weeks and provides the acquiring entity with a clear picture of the licence inheritance risk and the right-sizing opportunity available post-close.
More in This Series
Independent SAP licensing advisory — not affiliated with SAP SE. SAP, S/4HANA, RISE with SAP, and all SAP product names are trademarks of SAP SE.