SAP ECC: three routes and what decides between them

SAP has said mainstream maintenance for ECC 6.0 and the other Business Suite 7 core applications ends on 31 December 2027, with extended maintenance available until the end of 2030. The dates come from SAP statements as reported in the trade press, for example The Register, 28 January 2025. SAP also describes a separate option for large landscapes, running from 2031 to 2033. SAPinsider reports it as a transition option, not an extension of maintenance. Terms differ by release and contract, so check SAP's own maintenance notice for yours.

• The support date is driving the talk and nobody has priced the alternatives.
• Most customising sits in add-ons and reports, not in finance or logistics.
• Business teams keep shadow systems because an ECC change takes quarters.
• New systems link up through file drops and middleware that no one dares change.
• The conversion quote puts every benefit at the final stage.

What changes

Convert to S/4HANAThe core moves to the new product

Replace the coreA different ERP takes the core

Build around ECCApps, integrations and reporting go up beside the core

Suits

Convert to S/4HANAProcesses close to standard SAP

Replace the coreA decision to leave SAP

Build around ECCPain in the edges, core still sound

Who leads

Convert to S/4HANAAn SAP implementation partner

Replace the coreThe new vendor's partner

Build around ECCBrihat, working alongside your SAP partner

Value arrives

Convert to S/4HANAAfter the conversion

Replace the coreAfter the cutover

Build around ECCIn the first releases

Deadline pressure

Convert to S/4HANASet by the conversion plan

Replace the coreSet by the programme

Build around ECCLower, because the core decision can wait

1. Separate core from add-ons. Measure the share of ECC that is standard and record what each custom object does. This decides between routes.
2. Cost all three routes with the same scope, before choosing.
3. Build the surrounding platform first: an integration layer, operational apps for the painful processes, and a reporting model that reads from ECC.
4. Move the core later, once operations and reporting no longer depend on it. The conversion then becomes a bounded technical project.

The surrounding platform keeps its value if you convert later. Interfaces are preserved, so teams keep working while the core is swapped.

• Your processes match standard SAP flows and you want a conversion programme.
• You are already part-way through a conversion. Finishing is usually cheaper than restarting.
• The estate is compact and tidy, so a plain technical upgrade will do.