The M&A Licensing Challenge: Non-Transferable Rights
SAP licenses are non-transferable without explicit SAP consent. This single fact reshapes the entire M&A licensing landscape. When your company acquires another organization with SAP systems, you cannot simply assume those licenses belong to you. When you divest a business unit, the spun-off entity cannot automatically take SAP contracts with them. SAP's licence agreement makes this clear: change of control—defined as a change in beneficial ownership exceeding 30% of voting shares—triggers a mandatory review by SAP and often an audit.
SAP monitors corporate announcements, SEC filings, and deal notifications. Within weeks of a public M&A announcement, SAP's licensing team reaches out. If you acquired a company with 50 named users on SAP ERP, SAP will ask: "How many users from the acquired entity should be licensed under your new master agreement?" The answer is rarely obvious, and SAP's starting position almost always costs more than you budgeted.
Free SAP Licensing Guide
Download our comprehensive guide covering named user types, audit risk, and optimisation strategies.
Download the SAP Licensing Guide →Change-of-Control Clauses: The Fine Print That Costs Millions
Your SAP contract contains a change-of-control clause. Most customers never read it carefully until an acquisition is imminent. Here's what these clauses typically require:
- Immediate notification: You must notify SAP of any material change of control within 30 days.
- Compliance audit rights: SAP gains the right to audit your entire licensing position within 90 days, at no cost to SAP.
- Price adjustment: SAP can rebase your licence fees upward based on the post-acquisition user count or system scope.
- Continuation terms: SAP may require you to sign a new or modified agreement as a condition of transferring the acquired entity's SAP systems to your master agreement.
RISE with SAP contracts have stricter change-of-control language than on-premise agreements. Cloud subscriptions give SAP more leverage because termination costs are lower for SAP than terminating a large on-premise licence estate. If you're in a RISE contract and acquire another SAP customer, expect SAP to push for a higher subscription tier or additional users.
The DDLC Problem: System Integration Multiplies Indirect Access Exposure
DDLC stands for Digital Document and Licence Compliance—SAP's metric for measuring indirect access. It counts the number of documents (purchase orders, invoices, shipments, etc.) processed by your SAP system, whether or not a user ever directly opens SAP. The more documents your system processes, the higher your implied user footprint, and the larger your indirect access risk.
In a standalone company, DDLC exposure is somewhat controlled: you know which systems feed documents into SAP, and you've likely established a baseline. Post-acquisition, this changes radically. The acquired company's ERP, procurement platform, e-commerce site, and third-party integrations now feed data into your consolidated SAP environment. System integrations that were never built before are now running. Document volumes surge.
We've seen DDLC document counts increase 40-60% within the first year of integration, simply because of new system connections. SAP uses this as justification for a rebase of your licence position. If you were previously at 500 named users under the old DDLC baseline, a spike to 800 documents/hour can push SAP to demand a 25-30% increase in users or a conversion to a full-use model.
Structuring the Deal: Three Negotiation Strategies
Strategy 1: Pre-Emptive M&A Carve-Out in Your Current Contract
If you anticipate M&A activity in the next 18-24 months, negotiate an M&A carve-out clause now, before you announce a deal. This clause specifies exactly what happens if you acquire another company with SAP. Typical carve-out language includes:
- A 90-day "free look" period post-acquisition to assess the acquired SAP systems without triggering a full audit.
- A cap on how much SAP can increase your fees based on the acquisition (e.g., maximum 15% of the acquired entity's standalone licence value).
- A right to use DAAP (Dynamic Application Access Pricing) conversion for acquired systems, allowing you to avoid a user count spike by migrating to a cloud-based consumption model.
- A commitment from SAP that change-of-control does not trigger a renegotiation of your existing discount structure or contract term.
This requires negotiating with your SAP Account Executive and Legal team before a deal is public. Once SAP knows you're acquiring, your leverage evaporates.
Strategy 2: Use DAAP Conversion During Integration
DAAP (Dynamic Application Access Pricing) is SAP's consumption-based model for on-premise systems. Instead of paying per named user or DDLC metric, you pay per "access point" or per transaction. For acquired ECC systems that you don't plan to migrate to S/4HANA immediately, DAAP conversion can prevent a user count explosion.
Here's why this works: suppose the acquired company has 200 named users on SAP ECC. Without DAAP, those 200 users become "additional users" in your master agreement, and you pay the blended rate (likely 10-15% of your existing per-user cost, scaled to the new total). With DAAP, you pay per transaction or access, and the baseline is typically 30-40% lower than purchasing new named-user licences. If the acquired system processes 300,000 transactions per month, DAAP pricing is often more favorable than the alternative of rebasing the entire user base.
The catch: DAAP works only if you're confident you won't consolidate the acquired ECC into your existing S/4HANA instance within 18-24 months. If you migrate acquired systems to your S/4HANA, DAAP converts back to named users or full-use licensing at that point, and you've only delayed the rebase.
Strategy 3: Negotiate TSA Terms Aggressively
A Transition Services Agreement (TSA) is a temporary arrangement where SAP (or your licencing team acting as a licencing agent) continues to provide SAP services to a divested entity using your existing SAP environment, on a time-limited, fee-based arrangement. TSAs are common in divestitures.
SAP typically charges 10-20% of the divested unit's standalone licence value per year for TSA rights. If the divested business was worth $500k in annual SAP support, SAP might charge $50-100k per year for a TSA. Support costs continue to accrue during the TSA period at 22% of net licence value, further inflating your costs.
Our recommendation: cap your TSA commitment at 12 months. Longer TSA periods lock you into paying for systems you no longer control, and they delay the divested entity's negotiation of a standalone SAP contract (which gives SAP more leverage over the divested company later). Additionally, negotiate a fixed TSA fee, not a percentage-based fee, to lock in costs as system activity might increase during transition.
Need guidance on M&A licensing strategy?
Our team has defended 80+ indirect access disputes and negotiated 500+ acquisitions. Let's review your deal structure.Post-Acquisition Rebase Risk: S/4HANA Migration Triggers Full Re-Baseline
Many acquirers plan to migrate the acquired company's legacy SAP ECC system to their S/4HANA instance. This is a technical and business priority, but it has massive licensing implications that are often overlooked until the migration is underway.
When you migrate acquired ECC systems to your S/4HANA, SAP treats this as a new licence position, not a modification of your existing contract. You lose all legacy entitlements tied to the old system. If the acquired ECC was licensed under a 10-year-old support contract with grandfather pricing, that pricing dies when the data moves to S/4HANA. If the acquired system had perpetual licences, those may convert to subscription or require a rebase negotiation.
Even more critically, S/4HANA forces a re-baseline of named users and modules. Many companies run ECC with customizations and "dormant" user accounts that were never cleaned up. When you onboard those users to S/4HANA, SAP's tooling makes them active again, inflating your named-user count by 15-25%. Protecting against this requires contractual language that caps the post-migration user count based on the pre-migration baseline, even if the new system shows more active users.
Divesting? Plan Your Separation Licensing Now
If you are divesting a business unit that runs SAP, you have limited options: (1) keep the divested entity on your SAP systems via a TSA, (2) spin off a copy of your SAP systems and transfer it to the divested entity (with SAP's permission), or (3) require the divested entity to negotiate a new, standalone SAP contract.
Option 1 (TSA) is most common but creates ongoing costs and operational complexity. Option 2 requires SAP's explicit consent and typically triggers a licensing adjustment—SAP may argue that the "spun-off" system is a new system requiring a new licence. Option 3 forces the divested entity to negotiate a new contract, which puts SAP in a strong position because SAP knows the entity needs to operate independently and urgently.
The best time to negotiate divestiture licensing terms is before you announce the deal. Include language in your current SAP agreement that allows you to transfer licences to divested entities at a pre-agreed percentage of your current blended rate. If your current rate is $200 per named user (after discount), negotiate that divested systems can be transferred at $180-190 per user, with SAP's consent within 15 days of notice. This removes negotiation drama post-announcement.
Annual Support Costs: The Compounding Factor
SAP's annual support fee is approximately 22% of your net licence value. This percentage applies whether you're on-premise, in the cloud, or in a hybrid model. During M&A, support costs become invisible until you're deep in integration.
Suppose you acquire a company with $300k in annual SAP licence fees (net of discounts). You immediately owe SAP 22% support on top: $66k per year. If you negotiate a 12-month TSA for a divested unit with $200k in licence fees, you're paying $44k in support for systems you no longer control, every year the TSA runs. These costs compound.
Factor support costs into your deal economics upfront. Too many M&A teams focus on "licence optimization" (user count reductions, DAAP conversion) and ignore support costs, which can dwarf licence savings.
Get our SAP M&A licensing checklist
20-point framework used by 500+ enterprises to structure acquisition licensing, cap rebase risk, and negotiate TSA terms.Key Takeaways
M&A and SAP licensing intersect at three critical moments: (1) pre-announcement, when you can negotiate carve-outs; (2) post-announcement, when SAP audits your position; and (3) post-integration, when DDLC spikes and S/4HANA migrations reset baselines.
Non-transferable licences mean you cannot assume acquired SAP systems are yours. Change-of-control clauses give SAP audit rights and price adjustment power. DDLC metrics create indirect access exposure during system integration. RISE and cloud contracts constrain your flexibility more than on-premise agreements. Divestitures require TSA negotiations that can cost 10-20% of divested licence value annually. And S/4HANA migrations reset the entire licensing position, erasing grandfather pricing and forcing re-baselines.
The best protection is a contractual M&A carve-out negotiated before you announce a deal, combined with DAAP conversion strategies for acquired systems and capped TSA terms for divestitures. With 80+ indirect access disputes defended and 500+ engagements across diverse M&A scenarios, Redress Compliance has shaped the playbook that buyers use to protect themselves.