Bundling the commercial signature into the technical go live handed SAP the leverage in seven of ten conversions
Two events look like one because they land in the same programme plan. Separating the commercial signature from the technical cutover is the cheapest decision available, and the pressure to merge them comes from people who are not paying the licence bill.
Prepared by Redress Compliance · August 17, 2026 · SAP advisory. 35 SAP conversion engagements benchmarked, 2024 to 2025.
Executive summary
Bundling the signature into go live reset discounts upward in seven of ten conversions. Convenience at cutover is the most expensive convenience in the programme, because it hands SAP a deadline you cannot move.
Buyers who locked the baseline 9 to 12 months early held 25 to 40 percent more discount than those who started at renewal, which is the difference between negotiating with time and negotiating against a cutover date.
Brownfield came in 15 to 25 percent under greenfield on direct licence cost, while carrying more technical debt. That is a real trade rather than a free saving, and it should be priced as one.
On premise support sits near the standard 22 percent of licence value, so the maintenance base continues to matter throughout a conversion that people describe as a move away from it.
Two events, one programme plan
The technical cutover and the commercial conversion are separate decisions with separate risks. They appear as one because they sit in the same programme, and the integrator has no reason to distinguish them.
| Event | What it decides | Who owns the deadline |
|---|---|---|
| Technical go live | When the system cuts over | You, and it is genuinely hard to move |
| Commercial conversion | The contract, the counts, and the discount | You, unless you attach it to the cutover |
| Bundled together | Both, at once | SAP, effectively, because your date is now fixed and visible |
Attaching the signature to the cutover converts your operational deadline into their commercial deadline. A technical go live date is difficult to move, expensive to slip, and known to everyone including the account team. Signing the commercial conversion against that date means negotiating with a hard deadline you have publicly committed to, which is the weakest position available in any negotiation and one you have created yourself for the sake of programme tidiness.
Convenience at cutover is the most expensive convenience in the programme
The standard system integrator pitch is that you should convert the contract at the same time you cut over the technology, because it is simpler. It genuinely is simpler, for the integrator and for the programme plan. In roughly seven out of ten conversions benchmarked, bundling the commercial signature into the technical go live handed SAP the leverage and reset discounts upward. The integrator is not wrong that it reduces coordination effort; they are simply not the party paying for it.
The mechanism is a deadline transfer. A technical cutover date is hard to move, expensive to slip, and visible to everyone involved including the SAP account team. Once the commercial signature is attached to that date, the buyer is negotiating against a public deadline they cannot change, which removes the single most useful thing a negotiator can have. Nothing about the estate, the entitlement position, or the relationship has changed. What has changed is that one side now has a date and the other does not.
The counter is sequencing rather than resistance. Buyers who locked the FUE baseline and the indirect access position 9 to 12 months ahead of the commercial conversion held 25 to 40 percent more discount than those who started at renewal. That lead time is not preparation for its own sake: the usage audit that produces a defensible count takes months, and a count assembled under cutover pressure is the SAP proposed count by default, because there is no time to build an alternative.
One more decision deserves honest pricing. Brownfield conversions came in 15 to 25 percent under greenfield on direct licence cost while carrying more technical debt. That is a genuine trade rather than a saving, and treating it as a saving is how a licence decision quietly becomes an architecture decision made for the wrong reason. Price both the licence difference and the debt, and note that on premise support continues near the standard 22 percent of licence value throughout, so the maintenance base matters during a programme that everyone describes as a move away from it. The deployment model choice sits in the deployment models brief, the FUE benchmark in the RISE pricing benchmarks, and the library in the SAP practice.
- 520 vendor benchmarks, from SAP RISE to Oracle ULA to Microsoft EA
- FUE counts rebuilt from transaction logs rather than from proposals
- Every risky clause flagged with the exact quote, the page, and the replacement language
The sequence that holds the discount
- Separate the commercial signature from the technical go live as an explicit programme decision, since merging them is the default and it is the expensive default.
- Lock the FUE baseline 9 to 12 months ahead, because the usage audit behind a defensible count takes months and cannot be produced under cutover pressure.
- Settle the indirect access position in the same window, so it is argued on its merits rather than priced into a conversion envelope.
- Sign against a defended count, not an SAP proposed one, which is what the lead time exists to make possible.
- Price brownfield against greenfield on both dimensions, the 15 to 25 percent licence difference and the technical debt that comes with it.
- Keep the maintenance base in the model, since on premise support near 22 percent of licence value continues throughout the programme.
What the conversions showed, 2024 to 2025
Across roughly 35 SAP conversion engagements benchmarked:
Conversions where merging the commercial signature into the technical go live handed SAP the leverage and reset discounts upward.
Additional discount held by buyers who locked the baseline 9 to 12 months early rather than starting at renewal.
Brownfield projects came in 15 to 25 percent under greenfield on direct licence cost but carried more technical debt, which makes it a trade to price rather than a saving to claim.
On premise support sits near the standard 22 percent of licence value, so the maintenance base continues to matter throughout a programme framed as a move away from it.
Watch the briefing · 4:11S/4HANA Negotiations: The Discount Is Dead. The Tiers Are Not.Where the money sits in an S/4HANA conversion once the sequencing is right.
Your first five moves
- Decide explicitly that the commercial signature is not tied to the cutover date, and record it in the programme plan so the default does not reassert itself.
- Start the usage audit 9 to 12 months before the conversion, since a defensible count cannot be assembled under cutover pressure.
- Settle indirect access separately before it prices into the conversion envelope at SAP valuation.
- Price brownfield against greenfield on licence and on technical debt, treating the 15 to 25 percent as a trade rather than a saving.
- Keep support at 22 percent in the model throughout. The SAP practice runs the sequence with you.
Frequently asked questions
Should the contract convert at technical cutover?
No. In roughly seven of ten conversions benchmarked, bundling the commercial signature into the technical go live handed SAP the leverage and reset discounts upward. The integrator pitch that it is simpler is true and it is not their bill.
Why does bundling cost so much?
It transfers a deadline. A technical cutover date is hard to move, expensive to slip, and visible to the account team. Attaching the signature to it means negotiating against a public deadline you cannot change.
How much lead time is needed?
9 to 12 months. Buyers who locked the baseline that far ahead held 25 to 40 percent more discount than those who started at renewal, because the usage audit behind a defensible count takes months to complete.
What happens without that lead time?
You sign against the SAP proposed count by default, since there is no time to build an alternative. The count is not disputed because nothing exists to dispute it with.
Is brownfield cheaper than greenfield?
On direct licence cost, by 15 to 25 percent. It also carries more technical debt, which makes it a trade rather than a saving. Pricing only the licence difference turns an architecture decision into an accounting one.
When should indirect access be settled?
In the same 9 to 12 month window, separately from the conversion. Left until the conversion, it is priced into the envelope at SAP valuation rather than argued on its merits.
Does support cost change during conversion?
On premise support continues near the standard 22 percent of licence value, so the maintenance base matters throughout a programme that is usually described as a move away from it. Keep it in the model.
Is the integrator wrong to recommend bundling?
Not about the coordination effort, which is genuinely lower. They are simply optimising a different objective. Programme tidiness and commercial outcome point in opposite directions here, and only one party pays for the second.
What exactly should be locked early?
The FUE baseline and the indirect access position. Both require evidence that takes months to assemble, and both become SAP-defined by default if the conversion arrives before they are settled.
Can the two events realistically be separated?
Yes, and it is mostly a governance decision rather than a technical one. The systems do not require the contract to convert on the same date; the programme plan assumes it because nobody challenged the assumption.
The Move You Are Actually Being Asked to Make
Session 1 of the SAP RISE Migration Series. RISE bundles S/4HANA Cloud private edition, infrastructure and base run services into one subscription priced on Full Use Equivalents. It changes who operates the platform, not who carries the liability, and the perpetual entitlement terminates at signature.
