The S/4HANA migration is positioned to most boards as a technical modernisation programme. Contractually, it is the most consequential negotiation an SAP customer will conduct in twenty years. The CVA-3 conversion mechanism, the choice between RISE and customer-managed S/4HANA, the FUE sizing, the Digital Access true-up — each is a multi-million-dollar decision that compounds across the contract life. In 340+ engagements, the median S/4HANA conversion conducted with independent advisory landed 18–34% below the SAP-led proposal.
SAP's Contract Conversion Agreement version 3 (CVA-3) is the standard mechanism that translates the existing Business Suite (ECC) license footprint into S/4HANA license footprint. The conversion is not mechanical. Each Named User class is mapped to an S/4HANA Named User class — but the mapping ratios are negotiable. Each Package License is mapped to an S/4HANA Package License — but the modules bundle differently in S/4HANA, creating choice points. Maintenance is restructured — and the credit for prior maintenance against new entitlement is a negotiation lever, not a formula.
The customer-friendly approach to CVA-3 is to enter the conversion with a clean entitlement baseline (compliance position established, indirect access mapped, shelfware identified), a target S/4HANA footprint independently sized from the actual user and transaction pattern, and a counter-proposal that prices the gap between the ECC baseline and the target footprint as a credit against new entitlement. The SAP-led CVA-3 typically takes the existing entitlement at face value and prices the conversion as an upgrade.
The conversion economics are still moving up to signature. The earlier the independent baseline is established, the larger the credit.
RISE with SAP bundles S/4HANA Cloud (private or public edition), hyperscaler infrastructure, BTP credits and base support into a single FUE-based subscription. Customer-managed S/4HANA (on-premises or private cloud) keeps licenses and maintenance separate from infrastructure. The TCO comparison is fact-pattern dependent.
RISE economics generally favour: organisations consolidating multiple SAP instances; organisations undergoing material business transformation alongside the technical migration; organisations with limited internal SAP Basis depth; organisations valuing predictable subscription cost over depreciated CapEx. On-premises / customer-managed S/4HANA economics generally favour: organisations with stable, optimised SAP estates; organisations with strong internal SAP Basis teams; organisations with already-negotiated hyperscaler commitments (Azure MACC, AWS EDP, GCP CUD); organisations holding meaningful Oracle Database licenses or IBM Power AIX infrastructure with running depreciation.
The Full Use Equivalent is SAP's consumption unit for RISE. One FUE corresponds approximately to one Professional Named User, with conversion ratios for other user classes (typically 5 Limited Professional = 1 FUE, 30 Employee = 1 FUE). Package License consumption converts into FUE-equivalents at module-specific ratios. The sizing exercise is consequential: a 10% FUE over-sizing on a 1,000 FUE contract is a $300K–$500K annual over-commit.
Includes the CVA-3 conversion model, the FUE sizing framework, and the RISE vs on-premises TCO model.
SAP's fiscal year ends December 31. The strongest negotiation windows for material discount on S/4HANA conversions are Q4 (October–December) and the closing weeks of Q2 (May–June). SAP account teams operate on calendar-aligned quotas, and conversion approval authority for materially below-list pricing expands in the last 45 days of any quarter. The strategic implication is that the substantive conversion negotiation should land in SAP Q4 — which means the preparatory work (baseline, RISE-vs-on-premises analysis, FUE sizing, indirect access mapping) needs to begin no later than May.
The conversion economics are decided in the preparatory work, not at the negotiating table.
S/4HANA conversion advisory is one of the highest-stakes SAP specialisations. The firms most consistently recommended:
We have run S/4HANA conversions from $2M to $60M in baseline maintenance.
Weekly compliance intelligence for IT leaders.