Home / Case Studies / SAP RISE Migration
SAPManufacturingRISE MigrationIndirect Access

SAP RISE migration with $22.4M structurally protected.

A global manufacturer had a decade of legacy ECC investment, a S/4HANA deadline approaching, and an opening RISE proposal that quietly reset both the indirect-access boundary and the credit treatment for existing entitlement. Twenty-two weeks later, the migration signed with credits preserved, indirect access defined in contract and a five-year run-rate $22.4M below the opening.

Manufacturing operations centre
$22.4M
Five-year saving
100%
Legacy credits preserved
22 wk
Kick-off to signature
Defined
Indirect access scope
The contract going in

Decade of ECC. Hard deadline ahead.

The client had invested in SAP ECC, Business Suite and a wide custom development estate over eleven years. The internal migration plan for S/4HANA was real but uneven across business units. SAP's mainstream maintenance horizon had become the forcing function.

  • ECC core plus six adjacent SAP products, multiple regional shells.
  • Indirect-access exposure surfaced in two prior audits, settled but not contractually re-papered.
  • Substantial existing entitlement value, with no agreed credit framework for a RISE move.
SAP's opening position

RISE Premium Plus, credit at SAP's discretion.

The opening package proposed RISE Premium Plus with a metered consumption model, an FUE conversion that quietly reset legacy entitlement, and an indirect-access reference that pointed at SAP's contemporary digital-access pricing rather than the client's existing position.

What we flagged

Three distinct issues sat under one cover sheet: the RISE pricing model, the credit treatment for existing investment, and the indirect-access scope. Each had to be negotiated independently, or the headline number would have hidden the structural cost.

The work

Twenty-two weeks. Six workstreams.

1. Entitlement inventory

Built a defensible inventory of existing SAP entitlement, mapped to the RISE FUE conversion table, and flagged every line where the conversion was unfavourable to the client.

2. Indirect-access definition

Worked with the client's enterprise architecture team to document every system that touched SAP data. The output was a contractually defined indirect-access scope, not a unilateral SAP definition.

3. Credit treatment

Modelled three credit shapes against existing entitlement: full credit, weighted credit by product, and time-decay credit. Negotiated the structure that preserved a decade of investment.

4. Consumption shape

Re-sized the FUE commitment against a realistic adoption ramp aligned to the client's migration plan, not SAP's preferred adoption curve.

5. Exit and continuity

Negotiated continuity clauses covering S/4HANA on-premise optionality and data extraction terms.

6. Commercial position

Position paper drafted, executive sponsor presented, and our team supported the five follow-up rounds.

Lesson

A RISE move is three negotiations in one: pricing, credits and indirect access. Run them in parallel but document the position on each separately. Vendors prefer them blended; buyers benefit from them separated.

The contract going out

Credits intact, indirect scope contractual.

The RISE agreement preserved one hundred percent of the client's existing entitlement value, defined the indirect-access boundary in a contractual schedule, and ramped FUE consumption against the client's adoption plan. Five-year run-rate landed $22.4M below the opening proposal.

$22.4M
Saved
Versus the opening RISE proposal, measured over five years.
100%
Credit preserved
Existing SAP entitlement carried forward into the RISE structure.
Defined
Indirect access
Documented in contract schedule, not subject to vendor reinterpretation.
“Without the advisor's framework we would have signed a RISE agreement that looked similar on price and was structurally worse on indirect access. The credit work alone justified the engagement. The indirect-access definition justified it twice over.”
Group CFO · Manufacturing · Anonymised by client request
Related resources

More on SAP RISE negotiation strategy.

← Back to all case studies

Considering an SAP RISE migration?

Tell us the contract horizon and the indirect-access position. We will respond within one business day with the lead and the most relevant precedent.