M&A, Carve-Outs, and Contract Transfers: SAP Agreements in Corporate Transactions

M&A events raise a new set of questions for SAP contract relationships: Who takes over the agreement? What compliance risks does the acquiring company inherit? What is affiliate licensing, and when does SAP need to be formally involved? Addressing these questions early keeps you in a governance moment where you still have options.

What Happens to SAP Contracts in an Acquisition

An acquisition touches SAP contract relationships on multiple levels at once. On the acquiring side, the question is how to integrate, consolidate, or replace the target's existing SAP agreements. On the target side, the concern is continuity: do licenses carry over? Are there notification obligations to SAP? And what happens to usage rights that are tied to a legal entity that, after the transaction, no longer exists in its original form?

SAP contracts are generally not transferable by default. The contractual basis determines under what conditions a change of contracting party, or a structural change to the contract relationship, is permissible. Those conditions are not always spelled out explicitly, and in practice M&A transactions frequently close without the SAP contract layer having been reviewed systematically.

The timing of that review matters. Addressing SAP contract issues after a transaction closes means negotiating from a weaker position. Treating them as part of contractual due diligence allows you to assess risks and structure governance options before they become constraints.

Assignment clauses govern the conditions under which contractual rights and obligations may be transferred to another legal entity. In SAP agreements, these provisions tend to be restrictive: transferring a contract to a different legal entity generally requires SAP's written consent.

What qualifies as a "transfer" varies by contract structure. The following scenarios typically trigger a review obligation:

Merger: When the original contracting party ceases to exist as a legal entity because it is absorbed into another company, the contractual basis changes.
Share deal: In many structures, the legal entity formally remains intact even when all shares change hands. The contractual situation can still shift if clauses address a change of control.
Asset deal: In an asset deal, assets are transferred, not the legal entity itself. Licenses tied to the original entity do not automatically carry over in an asset deal.

The consequence of an undisclosed transfer can be a contract breach. In practice, that does not automatically mean immediate termination, but it narrows your negotiating position and creates a need for clarification that is far easier to handle before the transaction than after.

Affiliate Licensing: Bringing Group Entities Under an Existing Contract

Affiliate licensing refers to provisions in SAP agreements that allow group entities to use SAP software under a single master contract. The scope of that entitlement, the conditions attached, and the obligations that arise when the group structure changes vary by contract version and what was negotiated at signing.

Two scenarios matter for M&A situations:

Scenario 1: The acquiring company already has an SAP contract with an affiliate clause. The question here is whether the newly acquired company can be brought in as an affiliate automatically, or whether a formal amendment is required. Affiliate clauses typically define what qualifies as a "related company" and often include notification obligations when the group structure changes.

Scenario 2: The acquired company has its own SAP contract. This raises the consolidation question: should both agreements run in parallel? Can they be merged? And what does that mean for term lengths, volumes, and usage rights?

Both scenarios require a precise reading of the existing contract text. Affiliate clauses are not self-executing. They provide a framework, but they do not substitute for checking whether the specific situation actually falls within it.

Carve-Outs and Spin-Offs: What Transfers and What Does Not

In a carve-out or spin-off, the question runs in the opposite direction: which SAP licenses follow the separated unit, and which stay with the original company?

SAP licenses are tied to legal entities, not to organizational units. A business unit carved out of a legal entity does not carry licenses along automatically. The separated unit needs a new contractual basis, either through a new agreement signed directly with SAP, or through a structured transfer out of the existing contract, provided SAP agrees.

The remaining company also faces open questions: if user volumes, system usage, or transaction volumes attributable to the carved-out unit are no longer part of the picture, the actual scope of usage decreases. That creates a basis for reviewing the contract scope, but it does not produce an automatic reduction in obligations.

In practice, a carve-out is one of the most complex SAP contract scenarios because three parties each have governance interests at the same time: the original company, the carved-out unit, and SAP. Coordinating those three interests requires lead time and structured documentation.

Compliance Risks Inherited from Acquired Companies

An acquisition transfers not just assets and customer relationships, but also compliance status and contract history. In the SAP context, that means the target's compliance position with SAP becomes part of your own.

The following areas are relevant in a contractual due diligence:

License compliance: Is the target using SAP software within the volumes and entitlements covered by its agreements? Are there open measurement periods, unresolved derived-charges positions, or known usage outside the license scope?
Contract history: Are there open disputes or unresolved positions from past renewals or measurement cycles?
Support and maintenance: Is maintenance current? Are there gaps in support coverage that could create operational constraints after the acquisition?
SAP Enterprise Support vs. Standard Support: The support tier determines which SLAs apply and which escalation paths are available.

These risks cannot always be fully quantified before a transaction closes. But they can be captured systematically. An SAP-specific contractual due diligence that addresses these points provides a reliable basis for valuation and for any warranty provisions in the purchase agreement.

When to Bring SAP Into the M&A Process and How Much Lead Time You Need

A common question in practice: at what point should SAP be brought into an M&A process? The short answer: earlier than most companies do.

SAP is not a silent observer of a transaction. Depending on the contract structure, notification obligations may apply. And even when no formal obligation exists, SAP is, after the transaction, the contracting party with whom operational and commercial questions will need to be resolved. That process is easier when it is approached cooperatively and with preparation than when it happens reactively under time pressure.

Recommended lead times from practice:

Due diligence phase (before signing): Contractual review of all SAP agreements at the target. Identify assignment clauses, notification obligations, and open compliance items. Output: risk assessment for the purchase agreement.
Between signing and closing: Prepare for the SAP conversation. Which scenarios are viable? What needs to be communicated? Who speaks with SAP at which level?
After closing (promptly): Formal notification to SAP where contractually required. Clarify the integration roadmap: consolidation, parallel operation, or replacement?

Lead times for SAP conversations are typically several months in practice when contract amendments are needed. Starting those conversations too late means working against deadlines rather than with them.

Governance Checklist for M&A Situations

The following points structure the SAP contract work in M&A transactions. They are not exhaustive, because every transaction comes with its own contract structure. They serve as a starting point for a systematic review.

Before signing:

Which SAP contracts exist at the target (product types, terms, volumes)?
Are there assignment clauses, and what do they trigger in a share deal, asset deal, or merger?
Is there an affiliate provision, and does it cover the new group relationship?
What is the target's compliance status with SAP?
Are there open measurement periods, unresolved positions, or ongoing disputes?

Between signing and closing:

Which integration scenario is the goal: consolidation, parallel operation, or replacement?
What information needs to be communicated to SAP, and at which level?
Which governance moments arise for renewal, volume adjustment, or restructuring?

After closing:

Formal communication to SAP where contractually required.
Start contract documentation for the integrated entity.
Review usage data from both entities as the basis for future governance.
Assign responsibility for ongoing SAP contract governance in the new context.

Conclusion: SAP Contract Governance as Part of the M&A Process

M&A transactions change the foundation of SAP contract relationships, regardless of whether that aspect is addressed explicitly. The question is not whether SAP contract issues will become relevant, it is when they get addressed.

Companies that bring SAP contract considerations into the due diligence phase have more governance moments available to them than those who address the topic only after closing. The checklist above provides a starting point. The actual analysis requires knowledge of the specific contract structure.

If you are currently managing or preparing an M&A situation and want to review the SAP contract layer in a structured way, a Contract Check provides clarity on your starting position and the governance options available to you.

Further reading: