S/4HANA migrations: pricing the move without surrendering your installed base.

The move to S/4HANA, usually via RISE with SAP, is the largest software decision most SAP customers will make this decade, and SAP has framed it perfectly for its own side of the table. The migration is presented as inevitable, the on-premise maintenance deadline as an immovable countdown, and the RISE subscription as the natural destination. Each of those framings is doing work, and the work is to make you feel that you have no leverage and no time, which is exactly the state in which buyers overpay.

The reality is more favorable than the framing. You are not a new customer choosing SAP; you are an installed base with years of investment, a running system, and a maintenance relationship that is itself worth something. The migration is a negotiation, and the pricing of it is decided in the details SAP would rather you not model: how your users are classified, what the move actually costs against staying, and how much of your existing position you carry into the new deal. Price those, and the inevitable move becomes a deal you shape.

The move is a crossover, not a leap

The first thing to model is the one SAP presents as settled: whether, and when, moving actually pays against staying. A migration is not a single price, it is two cost paths over time. Staying on your current system carries the ongoing maintenance run rate. Moving carries the RISE subscription plus the one-time migration cost and the dual-running period where you pay for both worlds at once. Those two cumulative paths cross at some point, and where they cross, the payback year, is the number that tells you whether the deal in front of you is good, bad, or merely urgent.

Seeing the crossover changes the conversation entirely. A RISE offer that never pays back within a sensible horizon is not a migration, it is a subscription you were talked into on a deadline. One that pays back in a couple of years, after the migration and dual-run costs are absorbed, is a real case. The playbook builds both paths, including the year-one double cost that vendors gloss over, so the move is evaluated as the multi-year investment it is rather than the foregone conclusion it is sold as.

Right-classify the users before you count them

The pricing engine of a RISE deal is user classification, and it is where the most money quietly moves. RISE prices on Functional User Equivalents, a weighted count where an advanced professional user costs far more than a self-service or occasional one. SAP's opening proposal tends to classify generously in its own favor, counting more users at higher tiers than your actual usage supports. Right-classifying them, mapping each user band to what people genuinely do, and weighting accordingly, can move the FUE count substantially, and the FUE count is the deal.

This is the SAP equivalent of reclaiming idle seats: the negotiation is won in the composition, not the headline discount. A proposal at a given discount on an inflated FUE count is worse than a smaller discount on an honest one, and the only way to know the difference is to build the classification from evidence rather than accept SAP's. The playbook makes that count auditable, so when SAP proposes a number of advanced users, you can answer with the number your actual usage supports, which is a very different starting FUE and therefore a very different price.

The installed base is leverage, not a liability

The framing SAP most wants you to forget is that your existing position has value in the new deal. You are not walking in empty-handed. Your current maintenance run rate is the anchor the RISE subscription must beat to justify itself, your existing investment supports a conversion credit that should be reflected in the offer, and the cleanup you do first, retiring inactive users, dropping maintenance on shelfware, addressing digital access on your own terms, all reduces the base SAP gets to price from. Every one of those is leverage you carry into the migration if you establish it before you negotiate, and forfeit if you do not.

The deadline is real but it is not only your problem. SAP has its own fiscal pressure and its own strong interest in moving its base to RISE on schedule, which means the urgency runs in both directions even though only one side talks about it. A buyer who has modeled the crossover, right-classified the users, and quantified the installed-base credits arrives at the deadline with a priced position rather than panic, and a priced position is what turns a deadline from a threat into a shared incentive to close.

Pricing the S/4HANA migration

A model, not a reason to stay

Modeling the migration is not an argument against moving, and for many organizations S/4HANA is the right destination on its own merits, technical and strategic, that a TCO chart does not capture. The crossover tells you the economics; the decision also weighs capability, roadmap, and risk that are genuinely SAP's strengths. The point is to make the move a choice you priced, not a deadline you obeyed.

What the modeling removes is the asymmetry SAP builds the whole conversation around, that they know the numbers and you feel the pressure. Once you have the crossover, the honest FUE count, and the installed-base credits, you are negotiating a large, multi-year investment on equal informational footing, which is the only footing on which a deal this size should ever be signed. The move may still be inevitable. The price is not.