Every SAP customer still running ECC 6.0 has the same date in the diary. SAP has set the end of mainstream maintenance for Business Suite 7 at the end of 2027, with optional extended maintenance available on a chargeable basis until the end of 2030. Those dates have been public for years, which is exactly why they are so easy to keep deferring.
The deadline itself is the least interesting part of the conversation. What matters is that a system conversion is not a technical upgrade that can be dropped into a quiet weekend. It touches custom code, integrations, master data quality, authorisations and the working habits of everyone who uses the system daily. Organisations that treat 2027 as a project start date rather than a project end date tend to discover this the expensive way.
Three routes, three very different projects
There is no single migration path, and the choice you make shapes budget, duration and risk more than any other decision in the programme.
- Brownfield (system conversion) — you convert the existing system in place, carrying configuration, history and custom code forward. Fastest route to S/4HANA, but it also carries forward whatever technical debt you have accumulated.
- Greenfield (new implementation) — you build a fresh system on standard processes and migrate only the data you genuinely need. Cleanest end state, longest runway, and the most change management.
- Selective data transition — a middle path that lets you redesign parts of the landscape while retaining selected history and configuration. Powerful, but it needs disciplined scoping or it quietly becomes both of the other options at once.
Start with the readiness work, not the route
The most useful thing you can do long before choosing a path is to find out what is actually in your system. SAP provides readiness tooling that reports on simplification items, custom code conflicts and add-on compatibility. Running it early costs very little and reliably changes the shape of the business case.
Custom code is usually where the surprises live. Many ECC systems accumulate thousands of objects, a large share of which have not been executed in years. Retiring dormant code before conversion is far cheaper than remediating it afterwards, and it shrinks the testing burden for every subsequent release.
A migration date does not create urgency on its own. A clear picture of your custom code, your data quality and your integration surface does.
Planning backwards from 2027
Working backwards from the deadline is a sobering exercise. A mid-sized conversion typically needs a discovery and readiness phase, a design and remediation phase, at least two full test cycles including a dress rehearsal, and a stabilisation period after go-live. Add procurement, budget approval and the reality that no business wants a cutover during its financial close, and the comfortable window narrows quickly.
Extended maintenance to 2030 is a genuine option, not a failure. It buys time at a price, and for some organisations that trade is entirely rational. What is not rational is arriving at 2027 without having made the choice deliberately.
Leave a Reply