Topic · SAP ECC

The ECC estate is still the audit target.

Mainstream maintenance runs through 2027, extended maintenance to 2030, and the audit programme remains active. The drift inside ECC environments is where the audit value lives.

Pre-Conversion WindowThe compliance posture that determines the conversion economics.

Section I · The Landscape

ECC is not legacy.

Treating SAP ECC as a legacy product is a procurement mistake. Mainstream maintenance is contracted through 2027, with extended maintenance available through 2030. Many enterprise estates will not finish converting to S/4HANA before that horizon, and the ECC contract continues to govern the licensing position throughout.

The audit programme has not slowed. ECC carries the largest accumulated licensing drift in the SAP installed base, across user classification, dormant accounts, indirect access, and engine throughput. Every one of those categories is recoverable spend on either side of the table.

The pre-conversion window is the most commercially significant compliance moment of the ECC lifecycle. Whatever exposure exists in the ECC estate at the moment of conversion is monetised into the S/4HANA agreement, often at higher unit pricing and with fewer contractual levers than the original ECC licensing model offered.

Close the ECC position first. Defend the indirect-access surface, reclassify the user population, retire the shelfware, and document the engine throughput. The clean ECC position is the precondition for a defensible conversion. We work the ECC estate from the contract upward.

Section II · The Risk Surface

Eight ECC audit triggers.

— I.

User-Type Drift

Professional seats held by occasional users. Limited seats running Professional transactions. The classification has drifted ten years in most ECC estates.

— II.

Dormant-Account Population

Accounts that have not logged in for 180 days but remain licensed. In a typical ECC estate, the dormant share runs eight to fifteen per cent of total Named-User seats.

— III.

Indirect-Access Exposure

Salesforce, ServiceNow, custom portals, RPA, EDI. Every interface that touches ECC carries the historic indirect-access exposure under the Named-User model.

— IV.

USMM Configuration Errors

The measurement tool is configurable. The configuration in your environment may classify users more aggressively than your contract requires.

— V.

LAW Aggregation Risk

The consolidation across multiple systems double-counts users in some configurations. The defensible aggregation requires verification.

— VI.

Engine Metric Drift

SAP HR records, payroll runs, document volumes. The metric in the contract may not be the metric the engine is measuring.

— VII.

Acquisition & Divestiture Drift

The corporate-history licensing position. Acquired businesses with unmerged contracts. Divested businesses still consuming Named-User seats.

— VIII.

Pre-Conversion Monetisation

Every ECC compliance gap is monetised into the S/4HANA agreement at conversion. The pre-conversion close-out is the lowest-cost moment to settle.

— Field Note · ECC Pre-Conversion

The ECC estate that could not be converted until the indirect access was closed.

A global pharmaceutical client carried twelve years of ECC indirect-access drift across Salesforce, MuleSoft, and four custom portals. SAP's conversion proposal carried the full historic exposure into the digital-access baseline.

We closed the ECC indirect-access position first. The S/4HANA conversion then negotiated against a defensible baseline rather than a worst-case one. The conversion proposal fell by sixty-one per cent.

Read the case file →

Conversion Opening

$18.6M

SAP digital-access baseline

After ECC Close

$7.2M

defensible conversion settlement

Reduction

61%

below conversion opening

ECC Estate

12yr

of drift, closed in eight weeks

Questions, frequently.

Is SAP ECC still supported in 2026?

SAP ECC mainstream maintenance has been extended through 2027, with optional extended maintenance available through 2030. The product remains commercially supported, and the audit programme remains active. Treating ECC as legacy is a procurement mistake.

Why does SAP audit ECC customers?

ECC estates carry the largest accumulated licensing drift in the SAP installed base. User-classification drift, dormant accounts, indirect-access exposure, and unmeasured engine throughput are all common in ECC, and all monetisable at audit. The conversion window adds urgency.

What is the indirect-access exposure in ECC?

Indirect access in ECC arises when third-party systems, custom interfaces, or RPA bots create or read data in the SAP system. The historical Named-User model treated indirect users as licensable, and the exposure surface has grown with every interface added across the deployment history.

Should we close ECC compliance before converting?

Yes, where the timing permits. Every ECC compliance gap is monetised at conversion, usually at higher unit pricing in the new agreement. The pre-conversion close-out is the cheapest moment to settle the historic exposure. The conversion then negotiates against a clean baseline.

What is USMM, and why does its configuration matter?

USMM is the measurement tool that produces the user and engine inventory SAP uses at audit. Its configuration is customer-controlled, and an aggressively configured USMM will overstate the licensing position. Independent reconstruction is the only reliable test.