The modular go-live pattern — converting to S/4HANA region by region, business unit by business unit, or module by module rather than in a single cutover — is the operationally dominant migration approach for large estates. It reduces concentration risk, distributes change-management load, and lets the organisation absorb the new operating model in tractable phases. The pattern is also, in our practice, the single most common driver of cost over-runs against the original migration business case. The reason is rarely operational. It is that the licence-contract structure underneath the migration is designed for a single cutover, and the phased implementation activates the cost in advance of the operational return. This article sets out the three contract-structure principles that keep a modular go-live inside its expected licence envelope, and the failure modes that inflate it. It pairs with our S/4HANA migration compliance advisory work and the SAP S/4HANA topic page.
Why phased go-lives cost more
The default RISE or on-premise S/4HANA contract is structured around a single conversion date. The full Full Use Equivalent commitment is active from that date forward. The legacy ECC contract is retired at that date. If the operational migration follows a phased pattern across eighteen or twenty-four months, the legacy contract remains active in the regions or business units that have not yet converted, and the new S/4HANA contract is active from day one for the whole organisation. The buyer pays both contracts concurrently for the duration of the phasing. The double-pay window is typically the largest unbudgeted cost in the migration economic case.
The arithmetic is straightforward. A two-year phased migration with a legacy contract of approximately $4M annually and a new S/4HANA contract of approximately $5M annually carries roughly $4M to $7M of double-pay cost over the phasing window, depending on the cadence of the legacy retirement. Estates that do not anticipate this in the contract structure absorb the cost as a budget variance. Estates that do anticipate it negotiate a structure that recognises the phasing. See the FUE conversion math note for the arithmetic and the global-bank phased migration case file for the pattern at scale.
Principle one — the step-up FUE commitment
The cleanest structural protection is a step-up FUE commitment in the new S/4HANA contract. The contract starts at a fraction of the full FUE entitlement — typically 25 to 40% at the contract start — and steps up to the full entitlement over the planned phasing window. SAP’s commercial team will resist the step-up structure because it depresses near-term revenue, but will frequently accept it in exchange for a longer-term commitment that gives SAP visibility on the total contract value over a five- to seven-year horizon. The step-up structure aligns the licence commitment to the operational reality of the phased rollout. The SAP RISE topic page covers the variant for RISE contracts.
Principle two — the legacy retirement schedule
The legacy ECC contract should be reframed during the conversion negotiation rather than left in place to expire. SAP’s standard position is that the legacy contract continues to its existing end date and is then non-renewed once the S/4HANA contract is in place. The buyer-side improvement is to define a phased retirement that releases legacy licences as the migration proceeds, with the cost reductions flowing to the buyer in step. The mechanic is administratively heavier but the cost benefit is material. The ECC sunset implications note covers the broader retirement landscape.
Principle three — the regional-licence structure
Where the phasing is regional — the most common pattern in our experience — the contract structure should recognise the regional sequencing. Some estates achieve this by treating each region as a separate sub-contract under a master agreement, with its own FUE allocation, its own activation date, and its own measurement scope. The structure is more complex to administer but produces a cleaner cost trajectory. Other estates achieve a comparable effect through a single global contract with regional activation triggers tied to operational go-live events. The choice depends on the legal-entity structure and the regional finance reporting requirements. The RISE private-cloud edition note covers the variant for the RISE Private wrap.
A global consumer-goods client structured a sixteen-region phased migration with a step-up FUE commitment from 30% at contract start to 100% in month thirty. The structure released approximately $11M of double-pay cost relative to the SAP-proposed single-cutover contract structure, against an unchanged total-contract-value over the seven-year term.
What fails in practice
Three failure modes recur in the modular go-live licensing work.
Single-cutover contract on a phased operational plan
The most common failure. The contract is structured around a single conversion date because that is SAP’s default proposal, while the operational programme is committed to a phased rollout from the start. The phasing is treated as an implementation detail that the contract does not need to reflect. The double-pay cost emerges as a variance against the business case during year one of the rollout.
Optimistic phasing plan
The contract anticipates a phased rollout but the phasing assumption is faster than the operational reality. The step-up commitment activates before the corresponding regions have gone live, producing a partial double-pay window that is shorter than the single-cutover case but still material. The mitigation is conservative phasing assumptions in the contract structure with optional acceleration clauses, rather than aggressive assumptions with no flexibility.
Unanchored legacy retirement
The contract addresses the new S/4HANA commitment but leaves the legacy retirement to the standard end-of-life mechanic. The legacy contract continues running for regions that have already migrated, simply because the retirement event has not been triggered. The mitigation is the linked retirement schedule discussed under Principle Two.
The cross-functional preparation
The licence-contract work for a modular go-live is not a procurement-only exercise. The phasing plan is owned by the programme office, the regional sequencing is influenced by the operational and IT leadership in each region, the finance treatment is driven by the corporate finance organisation, and the licence-contract structure is the procurement and legal output. Each function holds part of the input data, and a structure built without one of the inputs will produce one of the failure modes above. The contract negotiation pillar covers the cross-functional sequencing discipline and the S/4HANA conversion handbook covers the document template that integrates the inputs.
The renegotiation option at mid-phase
Estates that signed the contract structure before recognising the phased reality typically have a renegotiation option at mid-phase, provided the relationship and the commercial leverage support it. The leverage is the threatened deceleration of the remaining rollout, which is operationally credible because the buyer is the one executing the migration. SAP’s commercial team will resist the renegotiation but will frequently accept a structure adjustment in exchange for a re-affirmation of the long-term commitment. The RISE mid-term renegotiation note covers the parallel pattern in the RISE world.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
If your S/4HANA migration is on a phased operational plan and the contract structure is still in negotiation, the highest-leverage starting point is the phasing-economics model that quantifies the double-pay window under the SAP-default single-cutover structure versus a step-up alternative. The model is the artefact that supports the structural negotiation. The S/4HANA migration compliance service brief covers the engagement structure.