Last Updated: October 23, 2026
Quick Summary
Your SAP ECC to S/4HANA migration cost depends on system complexity, custom code volume, data volume, migration approach and deployment model, so no single figure applies. For a mid-market company, a brownfield conversion is estimated at three to four times its annual ECC running cost, and ongoing ECC costs run 35-45% of the original licence investment each year until decommissioning.
- Custom code is the single most underestimated line in S/4HANA migration budgets.
- Brownfield conversion is generally the most cost-efficient route; greenfield costs more but clears technical debt.
- Budget licensing at three user-count scenarios and two deployment models, not one of each.
- Compare infrastructure on a three-to-five-year total, not a first-year cloud quote.
- The cheapest migration is the one that decommissions ECC on schedule.
Table of Contents
- Why SAP ECC to S/4HANA Migration Cost Planning Fails
- The Real SAP S/4HANA Migration Cost Factors
- Comparing Migration Approaches: Cost and Pros/Cons
- SAP S/4HANA Licensing Cost and Infrastructure Spend
- Building Your SAP S/4HANA Migration Budget Template
- How the SAP S/4HANA Migration Timeline Drives Cost
- Total Cost of Ownership and Contingency Planning
- Frequently Asked Questions
Why SAP ECC to S/4HANA Migration Cost Planning Fails
Most SAP ECC to S/4HANA migration cost estimates collapse for one reason: they price the platform and forget the data. Mid-market budgets are routinely set too low because they under-price data preparation work, according to Thinklytics’ analysis of S/4HANA migration costs, which advises planning separately for platform, data, and contingency.
In manufacturing and retail estates, the licence quote often arrives quickly, the custom-code remediation quote arrives late, and the budget breaks in between.
The scale of the gap is not marginal. Archon Data Store’s 2026 cost comparison estimates a brownfield conversion for a mid-market company at three to four times its annual ECC running cost. And ECC itself is not cheap to keep: the same analysis puts ongoing ECC costs at 35-45% of the original licence investment each year until decommissioning.
The Real SAP S/4HANA Migration Cost Factors
SAP S/4HANA migration cost factors fall into two groups: what your system contains, and how you choose to move it. Organisation size, migration strategy, and custom-code volume drive most of the variance, per Quinnox’s 2026 ECC to S/4HANA roadmap.
System Complexity, Custom Code, and Data Volume
Custom code is the single most underestimated line. Thirty years of ABAP enhancements, user exits, and bespoke interfaces all need triage: keep, remediate, or retire. Every object you keep carries conversion and testing effort; every object you retire carries a business conversation.
Data volume compounds it. Data migration and cleansing sit alongside implementation, technical conversion, consulting, custom-code remediation, and process work in the full cost picture documented by TJC Group’s S/4HANA cost driver breakdown.
Migration Approach and Deployment Model
Your path choice sets the shape of the budget before a single consultant is booked. Brownfield conversion is generally the most cost-efficient route, while greenfield rebuilds cost more but clear technical debt. Deployment model, public cloud versus private cloud versus on-premises, then shifts the balance from capital spend to subscription and hosting spend.
Estimating custom code from a spreadsheet count of objects rather than from an actual usage assessment can be an expensive mistake. Teams might budget remediation for a certain number of objects, only to discover a much larger scope and lose a quarter of contingency before testing begins.
Comparing Migration Approaches: Cost and Pros/Cons
Three routes dominate: system conversion (brownfield), new implementation (greenfield), and selective data transition. Each trades upfront cost against risk, speed, and how much historical data and customisation you carry forward.
| Approach | Relative Cost | Pros | Cons | Best For |
|---|---|---|---|---|
| System conversion (brownfield) | Lowest | Keeps processes and history; fastest path; least retraining | Carries technical debt; custom code must be remediated | Estates with clean cores and limited bespoke code |
| New implementation (greenfield) | Highest | Clean process design; drops legacy debt; standardised data model | Longest timeline; heaviest change management; full data rebuild | Organisations rethinking processes, not just platforms |
| Selective data transition | Middle | Keeps chosen data and config; selective cleanup | Complex scoping; specialist tooling; migration design effort | Multinationals consolidating several ECC instances |
For many mid-market manufacturers, brownfield often wins on cost unless the custom code ratio is genuinely high. For groups running different legacy versions across plants in several countries, selective data transition can often beat both on total risk.
SAP S/4HANA Licensing Cost and Infrastructure Spend
SAP S/4HANA licensing cost depends on your contract model and user count, not on a public price list, so treat any single figure you read online as illustrative at best. What you can plan for is the structure: subscription or licence fees, infrastructure and hosting, and the support transition. The practical way to budget is to separate these three lines and model each against your own user classification, deployment choice, and support end date.
Licensing mechanics that move the number
SAP prices S/4HANA through named-user and engine-based models, and the classification of users is where budgets drift most. A common pattern is that organisations count total ECC users but may fail to reclassify them for S/4HANA, where developer, professional, limited, and self-service users carry different price points. Model licensing at three user-count scenarios, not one, and record the classification assumption behind each.
Infrastructure and hosting by deployment model
Deployment model changes the infrastructure line more than any other decision. Public cloud consumption scales with workload and shifts responsibility to the provider, so the budget line is variable and tied to usage.
| Cost element | Public cloud | Private cloud | On-premises |
|---|---|---|---|
| Compute and storage | Consumption-based, scales with workload | Reserved capacity, fixed contract | Capital purchase, depreciation |
| Operating responsibility | Provider-managed platform | Shared, depends on contract | Internal basis and operations team |
| Network and data egress | Metered, watch cross-region traffic | Contracted bandwidth | Internal network and hardware refresh |
| Scaling profile | Elastic, pay for peak | Pre-provisioned headroom | Hardware refresh cycle |
| Cash profile | Operating expense | Mixed | Capital expense |
A common pattern is that public cloud may look cheapest in year one and drift upward as consumption grows, while on-premises may look expensive upfront and cheaper in later years once hardware is depreciated.
Support transition and the ECC carry cost
ECC extended support carries a premium that disappears once you move, which offsets part of the migration spend in the business case.
Kagool’s no-code SAP-to-Azure data ingestion approach exists precisely because hosting the platform is only half the infrastructure story; getting ECC and non-SAP data into a usable cloud foundation is the other half, and that data-movement work belongs in the infrastructure line, not buried in implementation.
Model licensing at three user-count scenarios and two deployment models, not one of each. User classification changes and deployment choice are the two most common causes of a licensing or infrastructure line moving by double digits between business case and contract signature.
Budgeting public cloud from a first-year consumption estimate without modelling peak workload and data egress can be an expensive infrastructure mistake. Teams might sign a contract on a low baseline, then discover that month-end processing and cross-region data movement push consumption well above the modelled figure.
Building Your SAP S/4HANA Migration Budget Template
A defensible SAP S/4HANA migration budget template itemises seven lines and attaches an assumption to each one. Populate it with your own assessment outputs, then add contingency at the end, not inside each line. The unique angle here is that the template is reusable: the same seven lines apply whether you are a mid-market manufacturer running one ECC instance or a multinational consolidating several, and the assumptions column is what changes between them.
| Budget Line | What It Covers | Assumption to Record |
|---|---|---|
| Platform and licensing | Subscription or licence, user tiers | User count by category |
| Implementation partner | Consulting, system integrator fees | Scope and duration in weeks |
| Technical conversion | System conversion, tooling, downtime | Downtime window per cycle |
| Data migration and cleansing | Extraction, transformation, quality fixes | Data volume and % to archive |
| Custom code remediation | Triage, rewrite, retire | Object count from usage assessment |
| Testing and training | Test cycles, user training, change management | Number of business roles affected |
| Contingency | Overrun buffer | Percentage held centrally |
How to populate the template by company size and migration approach
The template is only useful if you can fill it in. Use these three scenario profiles as starting assumptions, then replace each with your own assessment output. They are illustrative structures, not quotes.
- Small ECC estate, brownfield conversion: one instance, limited custom code, single country. The implementation partner and technical conversion lines dominate; data migration is modest because historic data volume is low. Contingency can be held at the lower end of your risk range because scope is contained.
- Mid-market manufacturer, brownfield or selective transition: several plants, moderate custom code, multi-country. Custom code remediation and data cleansing become material lines, and testing grows with the number of business roles. This is the profile where budgets most often break, because the licence quote arrives early and the remediation quote arrives late.
- Large multinational, greenfield or selective transition: multiple ECC instances, heavy bespoke code, consolidation scope. Implementation partner, data migration, and change management all scale up, and contingency must be held centrally at a level the risk assessment justifies because scope changes are most likely.
For each profile, the method is the same: cost every line from an SAP-specific assessment output rather than a vendor benchmark, and ring-fence contingency so scope changes draw on it visibly.
Linking the template to total cost of ownership
The template covers the one-off migration spend. To turn it into a board-ready number, add the recurring lines over three to five years: post-go-live application management, cloud consumption growth, and the ECC costs you stop paying. The difference between the one-off total and the lifecycle total is where the business case is actually won or lost, because a cheaper migration that runs ECC longer can cost more overall once the 35-45% annual ECC carry cost is added on top of the new platform spend.
The budget template is only as good as its assumptions column. A line item without a recorded assumption cannot be defended in a steering committee, and it cannot be re-forecast when reality changes. Populate it by scenario, link it to TCO, and hold contingency centrally.
How the SAP S/4HANA Migration Timeline Drives Cost
Timeline and cost move together, but not linearly. A compressed SAP S/4HANA migration timeline raises cost through parallel resourcing and overtime; an extended timeline raises cost through prolonged dual-running, extended support fees, and team attrition.
Plan in phases: assessment and business case, explore and design, conversion and remediation, test cycles, cutover, then hypercare.
Resource requirements deserve their own line. Your best ABAP and functional people are needed for remediation while still running ECC, and backfilling them is a real cost that rarely appears in the initial estimate.
Total Cost of Ownership and Contingency Planning
Total cost of ownership over three to five years is the number your board should approve, not the migration invoice. It combines the one-off migration spend with post-go-live application management, cloud consumption growth, and the ECC costs you stop paying.
Contingency planning is where credible budgets separate from optimistic ones. Cost overruns cluster in custom code, data quality, and integration testing. Hold contingency centrally at a level your risk assessment justifies, and release it only against a named risk.
The contrarian point: the cheapest migration is not the one with the lowest quote.
If your business case still hinges on a licence quote and a partner estimate, the number is not yet defensible.
Frequently Asked Questions
How much does an SAP ECC to S/4HANA migration cost?
There is no single standard figure. Migration cost varies widely with organization size, custom-code volume, data complexity, and migration approach. Archon Data Store estimates a brownfield conversion for a mid-market company runs 3 to 4 times its annual ECC cost, while ECC itself is estimated at 35 to 45 percent of the original license investment each year. Anecdotal Reddit discussions cite ranges from $250,000 to $500 million. Build your own estimate from itemized components rather than relying on a headline number.
What factors affect the cost of migrating from SAP ECC to S/4HANA?
The main SAP S/4HANA migration cost factors are organization size, migration strategy, custom-code volume, and data complexity. Quinnox identifies these as the primary cost variables and notes brownfield is generally the most cost-efficient approach. Add consulting support, data preparation and cleansing, custom-code remediation, testing, user training, change management, and downtime. Deployment choice (public cloud, private cloud, on-premises) also shifts infrastructure and licensing spend. Under-pricing data work is a common reason mid-market budgets fall short.
Is system conversion or a new implementation more cost-effective?
Brownfield system conversion is typically the most cost-efficient path because it preserves your existing configuration and historical data. A greenfield new implementation costs more upfront but can reduce long-term complexity by dropping unused modules and custom code. Selective data transition sits between them, moving only chosen data and processes. The right choice depends on how much of your current ECC setup still serves the business. If a large share of custom code is obsolete, greenfield or selective transition can pay back over three to five years.
How can organizations reduce SAP S/4HANA migration costs?
Start by auditing custom code and retiring what no longer earns its keep. Return to standard where possible, since accelerators and dropping unused modules reduce scope. Price data preparation realistically rather than treating it as an afterthought. Choose the migration approach that matches your actual complexity instead of defaulting to the most thorough option. Build a contingency line into the budget to absorb overruns, and sequence the work in phases so spend tracks value delivered. A structured budget template keeps every cost component visible.
