SAP S/4HANA Migration Cost Estimator: What Enterprises Actually Spend

Why Your First Migration Estimate Will Be Wrong

In our experience across more than 80 SAP S/4HANA migration engagements, the initial cost figure presented to a customer's board or CFO is almost always materially understated. The gap between that first number and the actual outturn cost is typically 30 to 40 percent — and in complex environments with significant custom code or extensive integration landscapes, overruns of 50 to 70 percent are not unusual.

The reasons are structural. SAP's commercial model depends on closing the migration deal. System integrators' revenue model depends on scope expansion after the contract is signed. Neither party is incentivised to present a conservative total cost of ownership at the point when you are making the commitment decision.

An independent cost estimator — built from the buyer's perspective — needs to capture all eight cost layers that typically appear in a migration, including those that vendors routinely understate or omit entirely from their initial proposals.

The Eight Cost Layers of an S/4HANA Migration

Layer 1: Licence Conversion or New Subscription

The first decision in any migration cost estimate is whether you are converting existing SAP ECC perpetual licences to S/4HANA equivalent licences, or whether you are entering into a new subscription arrangement — most commonly RISE with SAP.

Under licence conversion, SAP typically offers a credit of 70 to 80 percent of the net licence value you have paid historically. This credit is applied against the cost of the new S/4HANA licence baseline. The critical calculation here is establishing your true net licence value — not the list price SAP may cite, but the actual amount your organisation paid at the time of the original purchase, as evidenced by the contracts and invoices you hold. SAP has a well-documented tendency to overstate the base against which credits are applied. An independent validation before entering conversion negotiations is essential.

Under RISE with SAP, you are exiting the perpetual licence model entirely and entering a multi-year subscription. RISE bundles SAP S/4HANA Private Cloud, the underlying infrastructure, SAP Business Technology Platform (BTP) credits, and SAP Signavio Process Insights into a single per-user-per-year fee. The headline subscription figure typically increases at 5 to 7 percent per year on renewal unless you negotiate a cap at signing. Over a five-year RISE contract, that escalation alone adds 25 to 35 percent to your Year 1 commitment on a compounded basis.

Layer 2: Annual Support and Maintenance

Under the perpetual licence model, SAP annual support is approximately 22 percent of net licence value. This is a known, ongoing cost. When migrating to S/4HANA under a licence conversion path rather than RISE, the annual support obligation continues on the new licence baseline — which, because of the migration, may be materially different from your ECC baseline. The migration is an opportunity for SAP to reset the support baseline upward, particularly if they can argue that newly activated functionality has increased your licence entitlement.

Under RISE, support is bundled into the subscription fee. However, organisations often underestimate the cost of support for customisations, interfaces, and BTP workloads that sit outside the core RISE bundle. These can add 8 to 15 percent to the RISE subscription year-on-year.

Layer 3: Implementation Partner Fees

Implementation consulting costs are the single largest cost line in most migration budgets, typically representing 45 to 60 percent of total project expenditure. For mid-market organisations, this translates to $800,000 to $3 million in consulting fees. For large enterprises, the figure routinely exceeds $10 million and can reach $50 million or more for Fortune 500 programmes.

The SAP consulting market exceeded $16 billion globally in 2025, and with the majority of large enterprises now live on S/4HANA, the remaining organisations face a constrained talent pool in 2026 and 2027. Consulting day rates for experienced S/4HANA specialists have risen 30 to 50 percent compared to 2022 levels. Any budget built on 2023 or earlier consulting rate benchmarks needs to be recalibrated.

Layer 4: Custom Code Remediation

ABAP custom code that runs on ECC does not automatically run on S/4HANA. The new simplified data model (notably the merge of the BKPF/BSEG financial tables into the Universal Journal, the MATDOC material document table, and the redesigned logistics data model) means that many custom programmes that read or write directly to these tables need to be rewritten or decommissioned.

SAP's Custom Code Migration Worklist (CCMW) and the SAP Readiness Check tool can give you an estimate of the volume of custom objects requiring adaptation. In our experience, organisations with 500 to 2,000 custom ABAP objects should budget $150,000 to $600,000 for custom code remediation. Organisations with 5,000 or more custom objects are looking at $1 million to $3 million or more. Custom code that has been migrated to BTP-based extensions (BTP ABAP environment or SAP Build) carries additional licensing and operational cost.

Layer 5: Integration Landscape

Most large enterprises have 50 to 200 or more integration points connecting SAP ECC to third-party systems — warehouse management, manufacturing execution, e-commerce, CRM, HR platforms, and dozens of custom interfaces. Each of these needs to be validated, updated, or rebuilt against the S/4HANA APIs.

Organisations that have previously used SAP Process Integration (PI) or SAP Process Orchestration (PO) face an additional decision: SAP has announced end of mainstream maintenance for SAP PO in 2027, effectively mandating migration to SAP Integration Suite on BTP. This migration is not bundled into typical RISE commitments and carries its own licensing and implementation cost. Budget integration work as a standalone workstream with its own cost envelope, not as a line item within the general implementation estimate.

Layer 6: Dual-Run Period

Most production S/4HANA migrations require a period of parallel running — maintaining ECC in production while S/4HANA is being stabilised — lasting 12 to 24 months. During this period, the organisation is paying for both the legacy ECC infrastructure (or the RISE subscription that has already started) and the costs associated with managing two ERP environments simultaneously. The additional operational cost during dual-run is often not modelled in migration business cases. For a mid-market organisation, this adds $200,000 to $800,000 in incremental annual cost.

Layer 7: BTP and Additional Cloud Credits

RISE with SAP includes a BTP credit allocation, but it is rarely sufficient for real-world BTP consumption. BTP pricing is consumption-based across multiple service units — Cloud Platform Units (CPUs), integration calls, analytics compute, and workflow automations. BTP overages appear in Year 1 for organisations that take SAP's recommendation to move integrations, extensions, and analytics workloads onto BTP.

Separately, SAP Signavio is increasingly positioned as a mandatory component of RISE-assisted migrations. Signavio's Process Transformation Suite carries its own subscription, with enterprise licences typically priced at £2,500 to £4,000 per annum for the enterprise licence plus per-collaboration-user fees. SAP includes a limited Signavio entitlement in some RISE bundles, but full process mining and governance capability requires a separate Signavio contract.

Layer 8: Training, Change Management, and Post-Go-Live Stabilisation

Training and change management are consistently underbudgeted in migration business cases. A meaningful change management programme for an S/4HANA migration involving a redesigned user experience (SAP Fiori replacing SAP GUI for most users) and restructured business processes typically costs 8 to 12 percent of implementation fees. For a $3 million implementation, that is $240,000 to $360,000 in training and change management budget.

Post-go-live stabilisation — the three to six months of hypercare support following production cutover when issues are highest and team productivity is lowest — adds a further 10 to 20 percent of implementation cost in real-world budget terms.

Building Your S/4HANA Migration Cost Estimate: A Framework

The following framework provides a structure for building a credible, buyer-side S/4HANA migration cost estimate. Each layer should be estimated independently before combining into a total cost of ownership model.

Step 1: Establish Your Licence Baseline

Pull all SAP contracts and invoices from your SAP licence history. Calculate the net licence value paid — the amount actually invoiced and paid, not list prices. This is your baseline for credit negotiations. If you are moving to RISE, get a written breakdown of the RISE bundle: which S/4HANA modules, which infrastructure tier, how many BTP credits, and what Signavio entitlement is included. Do not accept a bundled RISE price without this breakdown — you cannot negotiate what you cannot see.

Step 2: Model the RISE Escalation Trajectory

SAP's standard RISE contracts include an annual price escalation clause. Negotiate a cap at contract signature. Model the Year 1 through Year 5 subscription cost at the proposed escalation rate versus a negotiated cap rate. The difference is often $500,000 to $2 million over a five-year term for a mid-market organisation. This is negotiable at signing and almost never negotiable at renewal.

Step 3: Validate Custom Code Volume

Run the SAP Readiness Check and review the Custom Code Migration Worklist output before finalising any implementation estimate. The volume of custom objects requiring remediation is the single biggest unknown in most migration cost models. Validate the output independently — the Readiness Check categorises objects by complexity, and complexity drives cost. Get independent estimates for the remediation effort from at least two parties who have no stake in the migration implementation contract.

Step 4: Map and Cost the Integration Landscape

Document every integration point connecting SAP to non-SAP systems. Classify each as standard interface (low remediation cost), custom interface (medium cost), or PI/PO-dependent (high cost, requires migration to BTP Integration Suite). Get an independent integration migration estimate separate from the system integrator's general project proposal.

Step 5: Budget the Dual-Run Period Explicitly

Determine your realistic go-live timeline and add 12 months of dual-run cost to your model. Dual-run cost includes the infrastructure cost of both environments, the incremental headcount required to manage two ERP systems, and the productivity loss during the stabilisation period.

Step 6: Apply a Contingency Reserve

Based on our portfolio of S/4HANA migration projects, a contingency reserve of 25 to 30 percent of the total estimated cost is appropriate for complex migrations and 15 to 20 percent for greenfield or relatively clean brownfield migrations. Organisations that budget without a contingency reserve will almost certainly breach their budget approval before go-live.

Red Flags in Vendor Migration Estimates

Several specific patterns in SAP and system integrator migration estimates are consistent indicators that the budget presented is understated and that the true cost is materially higher.

Watch for implementation estimates that do not separate custom code remediation from standard implementation, integration migration not listed as a separate workstream, BTP costs presented only as credits included in RISE rather than a full BTP consumption model, training and change management as a percentage of implementation fees below 8 percent, no dual-run period in the project plan, and a contingency reserve below 15 percent.

Each of these patterns is a signal that the estimate has been constructed to pass a business case approval rather than to represent the actual expected cost.

Five Principles for an Accurate Migration Cost Estimate

Drawing on our experience across the 80-plus SAP S/4HANA migration engagements we have supported as independent advisors, five principles consistently separate accurate migration cost estimates from optimistic ones that cause budget crises mid-project.

Estimate all eight layers independently. Never allow the system integrator to bundle custom code, integration, and change management into a single implementation figure. Each layer has different cost drivers and different uncertainty ranges.

Model the RISE subscription over five years, not Year 1. The annual escalation clause in RISE contracts means that Year 3 to Year 5 costs are materially higher than Year 1. TCO models that focus only on Year 1 subscription cost systematically understate the financial commitment.

Get independent custom code and integration estimates. The system integrator who wants to win the implementation contract has a commercial incentive to understate complexity at the bid stage. Independent estimates from parties with no stake in the implementation contract are more reliable.

Include S/4HANA licence baseline changes. S/4HANA migration frequently changes the licence baseline — through the introduction of new digital access scenarios (particularly if third-party systems will access S/4HANA data via APIs), changes in named user classifications, or the activation of modules not previously licensed under ECC. The Digital Access Licence Count (DDLC) metric — SAP's document-based metric for indirect access scenarios — needs to be modelled for any S/4HANA environment that will be accessed by non-SAP systems. Failure to model DDLC exposure accurately is one of the most consistent sources of cost surprises in S/4HANA migrations.

Commission an independent pre-migration assessment. A structured, independent pre-migration assessment covering licence baseline, custom code volume, integration landscape, and RISE contract terms typically identifies $500,000 to $3 million in avoidable cost before the implementation contract is signed. This is the highest-return investment available in the migration planning phase.