Key Takeaways
- Practical SAP right-sizing after M&A follows a six-stage sequence: contract mapping, USMM analysis, ELP construction, reclassification modelling, SAP engagement, and contract amendment.
- The most common error is engaging SAP before completing internal analysis — this hands SAP's commercial team the initiative and the numbers.
- User reclassification analysis requires transaction-level data, not just role assignments — USMM's role-based classification routinely overstates Professional user counts by 20–35%.
- SAP's account team will reframe every right-sizing conversation as a "future growth" discussion — the discipline is to anchor the negotiation on documented current usage.
- Timeline matters: the optimal window for post-acquisition right-sizing is within the first 90 days, before SAP runs its own measurement of the combined landscape.
SAP right-sizing after M&A is one of the few situations in enterprise licensing where the buyer genuinely holds significant leverage — if they act before SAP sets the commercial agenda. Most enterprises waste that advantage by allowing SAP's account executive to position a post-merger "strategic review" as a helpful planning session. That session is, in practice, an exercise in maximising SAP's revenue from the transition event.
This practical guide sequences the right-sizing process correctly: internal analysis first, SAP engagement only after your position is documented, and contract amendment as the output — not as SAP's starting point. If you're looking for the broader strategic context, our complete guide to SAP right-sizing after M&A covers the full picture. Our SAP licence optimisation service can execute this methodology on your behalf.
Stage 1: Complete Contract Mapping
Before any analysis begins, you need a complete inventory of every SAP contract across both entities. This is routinely underestimated in complexity. The target company may have multiple regional agreements, separate BTP or SuccessFactors contracts, legacy contracts from prior acquisitions that were never fully integrated, and Order Forms that were negotiated at different points in time with materially different metric definitions.
Contract Inventory
Extract every SAP contract document: Master Agreements, Order Forms, T&Cs, Licence Metric Schedules, BOM attachments, and any amendment letters. Index them by contracting entity, product, metric type, quantity, unit price, and renewal date. Pay particular attention to definitions — the same licence type may be defined differently across contracts from different periods.
Change-of-Control Review
Identify every contract that contains a change-of-control clause. Note the notification deadline, the definition of "control change," and the rights SAP has upon notification. This determines your timeline for engaging SAP and the sequence in which contracts must be addressed. Do not notify SAP of the change of control until Stage 4 at the earliest.
Renewal Calendar Mapping
Map every contract renewal date across both entities. Renewals are the natural leverage point for re-pricing and right-sizing. If a target company has a major contract renewing within 18 months of the acquisition close, that renewal becomes your primary commercial event — plan the entire right-sizing strategy around it.
Stage 2: USMM Analysis Across Both Landscapes
USMM — SAP's User and System Measurement tool — is the technical foundation of any right-sizing exercise. Run USMM on every SAP system in scope: all production systems in both entities, including any sandbox, development, or training environments where real users are provisioned. The output is a measurement file that classifies users by licence type based on their system roles.
The critical technical point is that USMM classifies based on the highest-privilege role assigned to a user, regardless of whether that user exercises that privilege. A finance user who was granted an administrative role for a one-time project three years ago will still be classified as a Professional user in USMM — even if their daily activity is entirely at the Limited Professional level. Our detailed analysis of how USMM works explains this classification logic in full technical detail.
For each landscape, document the total Named User count by licence type, the number of users who have not logged in within the last 90 days (dormant accounts that can be deleted), the number of users with administrative roles that don't reflect actual job function, and any engine or package metrics that appear to have changed since the last formal measurement.
Need USMM Analysis Support?
Interpreting USMM output correctly — particularly identifying reclassification opportunities — requires technical SAP licensing expertise. Our SAP licence optimisation team provides end-to-end USMM analysis and reclassification modelling.
Get Your Licence ReviewedStage 3: ELP Construction and Reclassification Modelling
With USMM data from both landscapes, build a consolidated Effective Licence Position (ELP). The ELP is the document that proves your licence position — it is what you present to SAP as the basis for any commercial discussion. A well-constructed ELP is your single most important asset in a post-M&A right-sizing negotiation.
The ELP has two layers: the base ELP, which reflects current usage with no changes, and the optimised ELP, which models the position after legitimate reclassification actions. The difference between these two numbers is your identified savings opportunity.
For user reclassification, the analysis must go beyond USMM role data. Extract the actual transaction history for a sample of users — specifically the T-codes they execute and the frequency. Users who only execute read transactions (display modes, reporting, standard inquiry) are Limited Professional candidates regardless of what role was assigned. Users who only access HR self-service are Productivity or Employee licence candidates. Users who only interact with SAP via a specific operational interface (warehouse management, plant maintenance) may qualify as FUE licences.
Understanding the precise difference between SAP Professional and Limited Professional licences is essential at this stage — the definitions are in the Licence Metrics Schedule of your contract, not in USMM's classification logic, and the contract definition governs.
Stage 4: SAP Engagement Preparation
Before engaging SAP, complete three preparation activities. First, build a savings model that quantifies the licence cost reduction under your optimised ELP — including the 22% annual support cost saving, compounded over the remaining contract term. This is the number you're negotiating to capture. Second, draft a change-of-control notification that is accurate but minimal — it confirms the transaction, identifies the new contracting entity, and reserves your position on licence adjustments pending formal review. Third, prepare a brief for your legal team on the specific contractual provisions relevant to the M&A event: change-of-control clause, licence portability provisions, and any divestiture-specific language.
⚠ Never Let SAP Run USMM First
If SAP requests to run its own system measurement before you've completed your internal analysis, decline politely but firmly. Once SAP has its own measurement of the combined post-M&A landscape, that number becomes the commercial baseline. Your analysis must precede SAP's to maintain negotiating leverage. SAP's account team will often frame this as "helping you understand your position." It is not help — it is intelligence gathering for SAP's commercial team.
Stage 5: Structured SAP Negotiation
Enter the SAP negotiation with three prepared positions: your target position (the optimised ELP with full reclassification benefit), your walk-away position (minimum acceptable outcome below which you challenge commercially or legally), and your opening position (slightly beyond your target, to create room to negotiate without conceding real value).
SAP's account team will attempt to reframe the discussion around future growth: "With the combined entity, you'll need additional licences for new users, new modules, new integrations." Anchor the negotiation firmly on documented current usage. SAP's growth projections are designed to inflate the contract. Your documented ELP is the counter to every forward-looking SAP claim.
Key negotiating points in a post-M&A context: volume discount improvement based on combined licence count, multi-year price protection for the transition period, clean portability language for future corporate restructuring, and support cost containment provisions. Our SAP contract negotiation team handles this engagement on your behalf, ensuring SAP cannot exploit information asymmetry at the negotiating table.
Stage 6: Contract Amendment and Documentation
The output of the negotiation is a formal contract amendment — not an informal email confirmation, not a verbal commitment from SAP's account executive. Every agreed change must appear in a signed Order Form amendment or a formal addendum to the Master Agreement before you implement any licence changes or submit a new USMM measurement.
The amendment should include: the revised Named User counts by licence type for the consolidated entity, the updated pricing basis, the treatment of the divested entity's licences (if applicable), the new renewal date (which you should negotiate to align with your strategic planning calendar), and explicit language confirming the right-sizing is complete and no prior period audit claims will arise from the consolidation.
The final step is submitting the combined USMM measurement under the amended contract terms. This is the first time you give SAP an official measurement of the consolidated landscape — and it happens after the contract amendment is signed, not before.
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.