Almost every company running SAP ECC has already decided to move to S/4HANA. What most of them have not decided yet, even if they think they have, is what they are going to move.

The difference matters. A migration that carries fifteen-year-old processes onto a new platform costs as much as a transformation but delivers what an upgrade delivers. Two or three years later, when the business asks for what the project never addressed, the company pays again to redesign those processes on the new system.

That second payment almost never shows up in the original business case. This article is about how to avoid it.

Where it goes wrong

The problem starts in the first meeting, when someone frames the project as «the S/4 migration». From then on IT leads it, it is budgeted as infrastructure, and it is measured on a single variable: going live on time.

Within that frame, every process decision that comes up along the way is settled in the safest way for the schedule, which is to leave it as it was. The purchase approval flow with five levels, the month-end close that depends on twenty manual reconciliations, the tax report built outside the system: all of it travels intact to the new platform. Nobody decided that explicitly. Nobody had the mandate to change it.

S/4HANA is a good deal more than ECC on a faster database. It changes the finance data model, simplifies tables that today support custom developments, and brings standard processes that many companies would no longer need to customize. Capturing that requires someone from the business, with authority, deciding which processes get redesigned. If that seat stays empty, IT makes the call by default.

Where the budget goes

When you open up a migration that went over budget, the overrun is rarely in licenses or infrastructure. It sits in three places the business case underestimated.

Custom code. A fifteen-year-old ECC landscape carries hundreds or thousands of in-house developments. Many were written to work around limitations S/4HANA no longer has, and others stopped being used years ago. Adapting all of them without asking whether they are still needed is the most expensive way to migrate. Every program retired before the project starts is one less program to adapt, test and maintain.

Replicated processes. When a process moves as is, it moves with its exceptions, its redundant approvals and its side spreadsheets. The new system ends up configured to reproduce the old one’s inefficiency, and the finance team keeps closing the month in the same number of days as before. The return that justified the investment never shows up, because nobody designed it.

Data. Duplicate customer and supplier master records, accounts nobody uses, documents left open for years. The migration forces the company to face its data quality, and doing that a few weeks before integration testing costs far more than doing it at the start.

All three have something in common: they are business decisions dressed up as technical tasks.

Greenfield, brownfield or selective

The choice of approach is usually presented as a technical debate among architects. In fact it is the most important business decision in the program, because it defines how much of the past the company takes with it.

  • Brownfield converts the current system with its history, configuration and custom code. It is the fastest path and the least disruptive to operations. It is also the one that most easily ends up as ECC under a new name.
  • Greenfield starts from scratch on standard processes and migrates only the data that is needed. It can capture the most value and demands the most from the organization: it changes how people work, not just the screen.
  • Selective transition combines both: it keeps what works and redesigns what does not. Done well, it is often the most sensible option for multinational groups with different realities in each country. Done badly, it adds the complexity of both.

None of them is better in the abstract. The useful question is which processes give the company an edge today and which are simply habit. IT does not have that answer. The CFO, the COO and each process owner do.

The calendar is not the excuse

The dates are clear. Mainstream maintenance for SAP ERP 6.0 ends at the close of 2027. Extended maintenance runs from 2028 through 2030, at a premium of two percentage points on the maintenance basis. A transition option runs to 2033, but it requires systems to be moved to SAP ERP, private edition, on SAP HANA before December 31, 2030 (SAPinsider).

Calendar pressure pushes toward a fast brownfield: «let’s go live on time and optimize later». The problem is that later rarely comes with a budget. Once the system is live, the team goes back to operations, the sponsor moves on to other priorities, and optimization becomes a pending line in next year’s roadmap.

There is time to do it right, but not to keep postponing the decision on what gets redesigned. That decision has to be made before choosing a system integrator, not after.

Five questions before signing

If the committee approving the migration cannot answer these questions with a name attached to each one, the project is not ready to start.

  1. Who in the business owns the redesign of each process? Not the project: each process. Order-to-Cash, Procure-to-Pay, Record-to-Report.
  2. Which metrics will change, and by how much? Days to close, DSO, cost per invoice processed. If the business case has no measured baseline, it will not be able to prove a return.
  3. What share of the custom code is actually used? Measuring it before budgeting its adaptation changes the size of the project.
  4. What will we do differently on tax compliance? In Latin America and Europe, e-invoicing requirements change every year. If the tax solution is migrated as one more patch, the problem returns with the first regulatory change.
  5. What are we not going to do? A scope that does not say what is out is not a scope.

In the S/4HANA migrations that go well, the integrator and the methodology matter less than people think. What matters is that someone understood from day one that the company was redesigning how the business runs, and put the business in charge of that decision.

Mariano Musi is Founder and CEO of Aunergia, a boutique management and technology consulting firm with hubs in Buenos Aires, Madrid, São Paulo and Orlando.