SAP ECC and APO leave mainstream maintenance at the end of 2027. ISG found that 39% of SAP’s roughly 35,000 ECC customers had not migrated by the end of 2024, and fewer than one in five reimplement their processes when they do move. The technical deadline is clear. The decisions that decide whether the migration pays off are business decisions, and they come first.
1. What Is in Scope, and Why
Decide which processes must change and which only move. A migration that tries to change everything at once stalls; one that changes nothing gives you a new system with the old problems. Write down the three business outcomes the programme must deliver, and use them to say no.
2. How Standard You Want to Be
Every custom development you take along is a cost you carry for the next fifteen years. Agree a rule before design starts: where does the business accept the SAP standard, and where does it truly differ from competitors?
3. Who Owns Which Data
Material, customer, supplier and planning master data decide whether the new processes work on day one. Name an owner per data object, agree quality rules, and start cleaning before the build, not during cutover.
4. Which Planning Tool, for Which Problem
APO users must choose a new planning platform: SAP IBP, embedded PP/DS in S/4HANA, or a specialist such as OMP or Kinaxis. Choose by the planning problem you need to solve (demand volatility, capacity constraints, shelf life, network complexity), not by the demo.
5. Who Runs the Change
Bain found that 88% of business transformations miss their original ambition, and that a dedicated transformation lead adds 24% of planned value. Give the programme a business owner with real time for it, and a transformation office that tracks value, not only go-live dates.
Sources: ISG research reported by The Register (February 2026); SAP maintenance announcements; Bain & Company (April 2024).
