SAP Practice
SAP S/4HANA migration strategy. The buyer guide.
An S/4HANA migration is a sequence, not a cutover. The 2027 deadline turns the timeline into a commercial weapon. Build the strategy before SAP builds it for you.
An S/4HANA migration is a sequence, not a cutover. The 2027 deadline turns the timeline into a commercial weapon. Build the strategy before SAP builds it for you.
An S/4HANA migration strategy is a sequence, not a single cutover. This guide covers the realistic timeline, the greenfield versus brownfield decision, protecting indirect access, and a five year cost model.
The 2027 deadline pushes many enterprises into a rushed program. Rushing is the most expensive way to migrate. A staged strategy keeps both cost and risk under control.
Strategy answers four questions: how long, which path, how to protect indirect access, and what it costs over five years. This guide takes them in order.
A realistic program runs 12 to 30 months end to end. The path and the estate size set the position within that band.
Every program moves through preparation, build, test, and cutover. The commercial work runs alongside, not after.
The commercial baseline must be locked before the deadline pressure builds. SAP gains leverage as the 2027 date approaches. Early preparation removes that leverage.
Mainstream ECC maintenance ends in 2027. Extended maintenance runs to 2030 at a premium. SAP set out the schedule in its maintenance commitment announcement.
The path choice shapes effort, cost, and the process landscape you end with. Match it to the estate, not to the vendor pitch. SAP documents the target system on its S/4HANA pages.
Migration strategy decision factors
| Factor | Brownfield | Greenfield | Selective |
|---|---|---|---|
| Duration | 9 to 14 months | 18 to 30 months | 18 to 30 months |
| Process change | Minimal | Full reset | Phased |
| Technical debt | Carried forward | Removed | Partly removed |
| Best fit | Clean estates | Heavy customization | Large groups |
Brownfield wins for clean estates that want speed and lower direct cost. It carries existing customization forward, which is a benefit only if that customization still earns its keep.
Greenfield wins where processes need a reset or customization has become a burden. It costs more and takes longer but produces a cleaner landscape.
Selective transition wins for large multi entity groups that cannot take a single cutover. It is the most complex to coordinate and to license.
Migration is the moment SAP most often resets indirect access. Protecting the position is a core strategy item, not an afterthought.
Negotiate indirect access as a standalone item. Do not let it ride inside the conversion or subscription quote where it is hard to challenge.
Measure your own digital access document volume first. The points below recur in our programs.
The common advice is to wait until closer to 2027 because the technology and tooling keep improving, so a later start is a cheaper start. We disagree. In the programs we have advised, late starters absorbed price increases of 10 to 20 percent because the looming deadline stripped their leverage. The buyer side move is to start the commercial baseline 9 to 12 months early even if the technical build waits, so the negotiation happens on your timeline and not under deadline pressure. Better tooling does not offset the discount you lose when SAP knows you have no time left.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The deadline is real, but it is a commercial weapon long before it is a technical one. The buyer who starts early negotiates. The buyer who starts late signs.
The five year view is the only honest comparison. A headline license fee hides the run and implementation cost that follow.
Cost splits into license, implementation, and run. Each behaves differently across the term.
RISE shifts cost to a subscription, while on premise keeps capital plus maintenance. SAP frames the subscription on the RISE with SAP pages. Model both with the RISE TCO calculator before choosing.
Annual escalators and indirect access are the two costs that buyers miss in the headline. Both compound across the term and both are negotiable.
Five moves keep a migration on budget and on schedule.
Lock the FUE and indirect access baseline 9 to 12 months before the technical project, using vendor terms from SAP's agreements center.
Pick brownfield, greenfield, or selective from a real assessment of customization and process need, not the integrator default.
Negotiate digital access separately and on your own measured document count.
Compare RISE and on premise over the full term, including escalators and exit terms.
Avoid committing to volume the program will not consume early. Align license ramp to adoption.
A realistic program runs 12 to 30 months end to end. A clean brownfield conversion can finish in 9 to 14 months, while greenfield and selective programs at large enterprises run 18 to 30 months. Commercial preparation should start before the build.
No. Late starters lose negotiating leverage as the deadline approaches and absorb price increases. Start the commercial baseline 9 to 12 months early even if the technical build waits, so the negotiation happens on your timeline.
Brownfield converts the existing system in place and is fastest. Greenfield rebuilds on a clean system and resets processes. Selective transition phases the move and suits large multi entity groups that cannot take a single cutover.
Mainstream ECC maintenance ends in 2027, with paid extended maintenance available through 2030. After that, customers must run S/4HANA or move to third party support to keep their systems maintained.
Negotiate indirect access as a separate item rather than letting it ride inside the conversion quote. Measure your own digital access document volume first, strip duplicates and internal flows, and convert only once the count is defended.
No. RISE is one delivery option, but private cloud and on premise paths remain available. Compare RISE against on premise over five years, including escalators and exit terms, before committing to a subscription model.
Timing drives cost more than path in our experience. A defended FUE and indirect access baseline, locked early, moves the license bucket more than any discount conversation held under deadline pressure.
A defensible baseline is a documented count of users, engines, and indirect documents scored against actual usage. It is the anchor for every negotiation. Without it, the buyer negotiates against SAP's numbers instead of their own.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The deadline is a commercial weapon long before it is a technical one. The buyer who starts early negotiates. The buyer who starts late signs.
