Summary

• The European Commission has accepted binding commitments from SAP over maintenance and support practices for on-premise ERP software.
• The case affects large organisations that still run business critical ERP systems while weighing cloud migration, third party support, and legacy risk.
• The commitments sharpen scrutiny of software support terms, switching costs, and vendor control over core enterprise systems.

SAP has agreed binding commitments with the European Commission to resolve competition concerns over maintenance and support for its on-premise enterprise resource planning software, giving customers more flexibility over support choices, unused licences, and re-entry to SAP maintenance.

The Commission’s case focused on aftermarket support services for SAP’s on-premise ERP products. Although the decision does not cover SAP’s cloud services, it reaches into one of the most sensitive areas of enterprise technology: the commercial control attached to systems that run finance, procurement, HR, manufacturing, logistics, reporting, and supply chain processes.

ERP support is rarely a background cost. In large organisations, maintenance rules can shape whether a technology strategy is genuinely chosen or quietly forced by contract. If customers cannot easily reduce unused licences, move parts of an estate to third party support, or return to vendor support without disproportionate charges, the support layer becomes a mechanism of lock-in.

The Commission’s decision accepts SAP’s commitments as legally binding. SAP has said the changes will apply globally to current and future customers across on-premise products for a 10-year period, with the company presenting the outcome as a move towards greater flexibility and predictability.

Large public bodies, manufacturers, utilities, retailers, transport operators, and regulated companies still run heavily customised on-premise ERP systems. Many of those systems are old, expensive, and difficult to change, yet they remain deeply embedded in how organisations operate. Cloud migration may be the strategic direction, but it is often constrained by data quality, custom code, integration debt, business continuity risk, and the cost of replacing processes that already work, however untidily.

That makes Brussels’ intervention more than a legacy software dispute. European regulators have been examining the practical barriers that keep customers tied to dominant technology vendors, from cloud egress fees and software licensing rules to data portability and platform dependency. Enterprise software lacks the public profile of consumer platforms, but its market power can be just as material for businesses and public services.

The decision also complicates the usual modernisation narrative. Software vendors can reasonably argue that cloud products improve security, functionality, and innovation speed. Customers can still ask whether support policies for older systems are encouraging migration through product merit or through commercial pressure. Competition law now has a role in separating those two forces.

Procurement teams should not treat the commitments as a simple escape hatch. ERP estates remain difficult to unwind, and third party support brings its own risk questions around updates, liability, security, and future compatibility. However, the commitments may strengthen the negotiating position of customers that want to slow a migration, retire parts of an estate, or reduce shelfware without losing all strategic optionality.

The broader market signal is clear enough. Vendor power in enterprise software does not always sit in the application screen. It often lives in maintenance formulas, renewal dates, audit rights, licence definitions, support reinstatement fees, and the fear of disrupting systems that finance teams need every month. Brussels has now put that quieter machinery back under inspection.