Section I · The Brief
The conversion trigger
The client, a top-five European integrated utility with operations in fourteen countries, was eighteen months into a planned S/4HANA conversion when SAP proposed an interim measurement and licence-bridge agreement. The proposal carried an opening migration true-up of sixteen point eight million dollars on top of a recontracting demand to move forty-seven thousand named users from ECC bands to the four S/4HANA professional/functional/developer tiers, plus a separate digital-access entitlement priced on the prior twelve months of API-traffic logs.
The trigger event was the client’s formal notification to SAP that the conversion programme would complete in eighteen months. SAP’s response was a measurement request, a USMM run, and a proposal that combined three commercial conversations into one document — the named-user reband, the digital-access entitlement, and an engine-metric reconciliation across the HANA, BW, and PI estates.
The stakes were not only the headline number. The conversion baseline becomes the floor for all subsequent SAP commercial conversations. Accepting an inflated baseline meant accepting an inflated reference point for every renewal, every uplift, and every M&A scope-expansion conversation for the next decade.
Section II · The Opening Claim
The SAP position
SAP’s opening claim was structured as a four-component figure that the account team presented as a single conversion true-up. The components were not separately negotiable in the form delivered, and the account team’s position was that the conversion factor — the discount applied to the bridge entitlement — would degrade if the conversation extended past the fiscal year boundary.
The four components, as presented in the opening proposal letter, broke down as follows.
- Named-user reband to S/4HANA tiers: 47,000 users at an unblended average that priced the migration at $7.2M, with no entitlement credit for the existing ECC band assignment.
- Digital-access entitlement: 2.4 billion documents per year, priced at the published per-document rate, contributing $5.6M of the headline.
- Engine-metric reconciliation: HANA Enterprise CPU recalculation, BW LSA++ migration, and PI message-throughput reset, contributing $2.8M.
- Conversion services and remediation: SAP-led conversion advisory and remediation, contributing the remaining $1.2M.
Section III · The Defence
The baseline rebuild
We took the engagement on a renewal-preparation footing with explicit written notice to SAP that the conversion conversation would be conducted on a measured, evidence-based timetable independent of the SAP fiscal year. The first defensive move was to convert the conversation from a single combined proposal into four separately defensible workstreams. Each became a contractual element with its own evidence file, its own negotiation calendar, and its own commercial close-out.
On the named-user reband, we ran a parallel USMM with an evidence-based classification methodology over a twelve-month activity window. The output reclassified 18,400 users from the SAP-proposed Professional tier to Functional or Developer tier, and identified 3,100 dormant accounts retired before measurement. The reband ran the migration component to $2.1M against the opening $7.2M.
On the digital-access component, we ran a six-week document-classification programme across the inbound and outbound API surfaces. We reclassified system-internal RFC traffic out of the chargeable population, applied document deduplication for traffic the contract excluded, and locked the digital-access pricing to the published 2024 rate card before the 2026 uplift took effect. The digital-access component closed at $1.8M against the opening $5.6M.
On the engine metrics, we documented the actual HANA Enterprise CPU consumption, demonstrated that the BW LSA++ migration did not change the metered count under the existing contract, and reset the PI message-throughput measurement to the contractually-defined baseline. The engine component closed at $0.9M against the opening $2.8M.
- USMM rebuild over a 12-month evidence window — 21,500 reclassifications and retirements
- Document-classification programme across 14 API surfaces — system-internal traffic excluded
- Digital-access rate-card lock to the 2024 schedule — pre-uplift pricing held
- Engine-metric reconciliation against contract definitions — HANA CPU and BW LSA++ neutralised
- Conversion-services rebid against three independent providers — SAP advisory removed from the bundle
Section IV · The Settlement
The signed position
The final conversion true-up closed at five point four million dollars against the opening sixteen point eight million dollar proposal — a sixty-eight percent reduction. The settlement was structured as four independent contractual elements rather than a single combined commitment, preserving the client’s ability to renegotiate any of the four at the next contract anniversary on its own evidence.
The contract language secured three forward protections. First, the digital-access entitlement was contractually capped at the 2024 rate card for the duration of the bridge agreement, removing the pricing uplift exposure. Second, the named-user reband included a documented classification methodology referenced as the measurement standard for future USMM runs, preventing reclassification challenge in subsequent audits. Third, the engine-metric definitions were appended to the contract as a measurement schedule, removing the interpretation risk on HANA Enterprise CPU and BW LSA++ scope.
Total elapsed time from receipt of the opening proposal to signature was twenty-two weeks. The conversion programme completed on its original schedule with the bridge agreement in place. SAP’s account team was briefed in writing on the new measurement standard before the engagement closed.
Section V · Lessons Applicable
What others can use
Five takeaways from the matter that apply to any organisation in or approaching S/4HANA conversion.
- Refuse the combined proposal. SAP presents conversion as a single number to limit the negotiation surface area. Insist on four separately-numbered components — named user, digital access, engines, services — each with its own evidence file.
- Run a parallel USMM with evidence-based classification before accepting the SAP-proposed reband. The SAP-proposed reband uses role-collection mapping; activity-based classification typically moves 25-40% of users to a lower tier.
- Lock the digital-access rate card to the schedule in effect at engagement start, not the schedule that takes effect during the conversion window. SAP raises rates annually; the conversion is the moment to fix them.
- Document engine-metric definitions in a contract schedule. HANA Enterprise CPU and BW LSA++ scope are interpretation-heavy — SAP’s default interpretation is always more expensive than the contract requires.
- Run the conversion timeline on your fiscal year, not SAP’s. The end-of-quarter and end-of-fiscal-year pressure is on the SAP account team. Run the calendar in writing and the conversation slows down.
