Key points

  • Mainstream maintenance for SAP ECC ends on 31 December 2027.
  • AI value depends on current processes, clean data and a standard core.
  • Start with evidence: landscape, custom code, data quality and cost baseline.
  • A phased, value-led plan beats a compressed big-bang migration.

What changes on 31 December 2027

Mainstream maintenance for SAP ECC ends on 31 December 2027. After that date, organisations need a different support arrangement or a move to SAP Cloud ERP. The date is not a surprise, but it is now close enough that “we will look at it next year” is no longer a plan.

The temptation is to treat this as a technical migration: lift the custom code, move the database, keep the processes the same. That approach protects the status quo and carries the complexity forward. It also makes the AI conversation harder, because AI needs standard, current processes and trusted data underneath it.

The ERP decision and the AI decision are the same decision

SAP Cloud ERP includes Joule, SAP’s AI copilot, inside everyday workflows. The value of that AI depends on how much of your process runs on standard SAP and how much runs on custom code, spreadsheets and workarounds.

If you move to the cloud with the same bespoke processes, you get a more expensive version of today. If you use the move to reset the core, you create the conditions for AI to work. That is the strategic choice hiding inside the deadline.

Start with evidence, not a vendor demo

Before you choose a path, you need a factual view of what you run. That means an application inventory, a custom-code assessment, a data-quality profile and a cost baseline for the current estate.

  • Which applications and integrations support the core processes?
  • How much custom code is active, and what business outcome does it protect?
  • Which master data is duplicated, incomplete or unowned?
  • What does the current estate cost to licence, host and support?

Decide what “clean” means before design

A clean core is not a slogan. It is a set of decisions about what stays standard, what moves to an extension and what retires. Make those decisions before the build starts, with a design authority that can defend them when pressure arrives.

SAP BTP provides the extension platform for the small number of capabilities that genuinely differentiate the business. The rest should be standard SAP. The test is simple: does this customisation create competitive advantage, or does it preserve a workaround?

Sequence the move around business value

A phased plan lets the business see value early and gives the program room to learn. The sequence depends on your starting point, but the logic is consistent: stabilise the data, standardise the core, then extend.

For some organisations, a defined scope can move quickly. Emphasys delivers its SAP-qualified GROW Fast package in 16 weeks for consumer goods organisations. Larger or more complex estates need a longer, staged program. The mistake is assuming every scope needs the same timeline.

Build a business case the board can compare

The board needs to compare the cost of moving with the cost of staying. That comparison should include licence and infrastructure, support and custom-code maintenance, the cost of key-person risk, and the opportunity cost of not being able to use AI on current data.

A costed roadmap does that. It turns a technology deadline into a sequence of funded decisions, each with an owner and an expected outcome.

What to do in the next 90 days

Four steps will give you a defensible position without committing to a vendor or a build.

  • Commission a landscape and custom-code assessment.
  • Profile master data quality and identify the migration risks.
  • Agree the clean-core principles with the CIO and CFO.
  • Build a costed roadmap with two or three funding gates.