Mainstream maintenance for SAP ECC 6.0 ends on 31 December 2027, with paid extended maintenance to 2030. Here is what that means for the custom code most companies have built up.
If your company still runs SAP ECC 6.0, the clock is now very visible. SAP's mainstream maintenance for ECC ends on 31 December 2027. Customers on enhancement packages 6 to 8 can buy extended maintenance until 31 December 2030, at an extra cost and under SAP's commercial terms.
Most articles about this deadline focus on licensing and the choice of S/4HANA edition. This one looks at the part that usually decides the timeline and the budget: the custom ABAP code your business depends on.
Your three realistic options
1. Stay on ECC with extended maintenance
This buys time until 2030. It suits companies with a heavy change program already under way or a planned acquisition. The risk is that every year on ECC adds more custom code to migrate later, and skilled ECC people become harder to keep.
2. Move to S/4HANA (brownfield, greenfield or selective)
A brownfield conversion keeps your configuration and data and converts the system. A greenfield project starts fresh with standard processes. A selective approach sits in between. All three require a clear decision about each custom object: keep, rewrite or retire.
3. Third-party support or a different ERP
Some companies move to third-party support or replace SAP altogether. This can cut short-term cost but limits access to SAP updates and legal changes, so it needs a careful look at tax and regulatory updates in each country you operate in.
Why custom code decides your timeline
A typical ECC system carries thousands of custom objects: reports, interfaces, conversions, enhancements and forms (often called RICEF). In an S/4HANA conversion, many of them break or become unnecessary because of data-model changes, for example the simplified finance tables and the move to the Business Partner model for customers and vendors.
Companies that start this work late often find that custom code, not infrastructure, is what holds up go-live.
A practical custom-code plan
- Measure usage. Turn on usage logging in production for several months. In many systems, a large share of custom objects is never used and can be retired.
- Run the checks. Use SAP's ABAP Test Cockpit with the S/4HANA readiness checks to list what will break.
- Classify every object. Retire, replace with standard, adapt, or rebuild as a side-by-side extension on SAP BTP.
- Clean the core. Move new development to released APIs and extension points so future upgrades are cheaper.
- Test with real scenarios. Build regression test scripts around month-end, order-to-cash and procure-to-pay before cut-over.
Where offshore ABAP teams help
Remediation is high-volume, well-defined work: analyze an object, fix it, unit test it, document it. That makes it a good fit for an offshore team working alongside your implementation partner. Usual approaches:
- An offshore ABAP pod that clears the remediation backlog while your onshore team handles design decisions.
- A support retainer that keeps ECC stable while your internal team focuses on the migration.
- Fiori and integration developers for the new extensions you'll need after go-live.
Time zones matter here. Level 8 runs SAP shifts that cover the working day in the UK, the Gulf, South Africa, North America and Australia, so questions get answered the same day.
Key dates at a glance
| Milestone | Date |
|---|---|
| End of mainstream maintenance, SAP ECC 6.0 (EHP 6–8) | 31 Dec 2027 |
| End of optional extended maintenance | 31 Dec 2030 |
Confirm the dates and terms for your exact release and contract with SAP or your SAP account team.