"How much will it cost?" is the first question every S/4HANA migration sponsor asks, and the honest first answer is "it depends" — which is exactly why so many of these projects go over budget. The cost of an S/4HANA migration is driven less by SAP's license price than by the state of your existing system, the path you choose, and how disciplined you are about scope. This guide breaks down what actually drives the number, gives realistic ranges, and explains the line items that quietly blow up budgets so you can plan for them instead of discovering them.
Want a rough number before you read further? Try our free S/4HANA migration cost estimator — no signup — to see how approach, scale, and custom-code volume move the range.
Why There Is No Single Price
Two companies of similar size can have S/4HANA migration costs that differ by a factor of five. The difference is rarely SAP licensing. It is the accumulated complexity of fifteen or twenty years of customization, integration, and data.
The variables that move the number most:
- The migration approach. Brownfield conversion, greenfield reimplementation, and selective data transition have very different cost profiles, covered below.
- Custom code volume. A system with a few hundred custom objects is a different project than one with tens of thousands, because every custom object is a candidate for remediation.
- Integration footprint. The number of interfaces to other systems often drives more effort than the SAP work itself.
- Data quality and volume. Years of accumulated, poorly governed data costs money to clean, archive, or migrate.
- Target platform. On-premise, hyperscaler, or RISE with SAP each carry different infrastructure and licensing economics.
Anyone who quotes a firm price before assessing these is guessing. The purpose of a proper assessment is to turn these unknowns into a defensible estimate.
Cost by Migration Approach
The path you choose sets the baseline cost structure. We compared the approaches in depth in our brownfield vs greenfield guide; here is how they map to cost.
| Approach | What drives the cost | Relative cost profile |
|---|---|---|
| Brownfield conversion | Custom code remediation, technical conversion, testing | Lower upfront, higher technical-debt carry |
| Greenfield reimplementation | Process redesign, configuration, data migration, change management | Higher upfront, cleaner result |
| Selective data transition | Hybrid scoping, data extraction tooling, dual expertise | Variable, often mid-range |
Brownfield is frequently assumed to be the cheap option because it preserves the existing system. That is true for the technical conversion, but it carries forward your custom code and technical debt, which then has to be remediated for the Clean Core target. Greenfield costs more upfront in process and change work, but you stop paying interest on old technical debt. Selective transition tries to capture the best of both and is priced accordingly.
The lesson is that the cheapest-looking path is not always the lowest total cost. A brownfield conversion that defers remediation can cost more over five years than a greenfield project that resolves it once.
The Cost Components Nobody Itemizes Up Front
When migrations go over budget, it is usually because the original estimate covered the obvious work and missed the rest. The components that get underestimated:
- Custom code remediation. Identifying, prioritizing, and fixing custom objects for HANA and Clean Core compatibility is often the largest single effort, and it is the one most often underscoped.
- Testing. Functional, integration, regression, and performance testing across a complex landscape consumes far more effort than teams expect. Test data management alone is a project.
- Integration rework. Every interface to a non-SAP system is a potential rework item, and middleware changes (for example PI/PO to Integration Suite) may run in parallel.
- Data cleansing and archiving. Deciding what data to bring, clean, archive, or leave behind is effort-intensive and politically fraught.
- Change management and training. For greenfield especially, the cost of getting people to adopt new processes is real and routinely omitted from technical estimates.
- Cutover and hypercare. The go-live weekend and the stabilization period afterward need staffing that the build-phase estimate may not include.
A credible budget has a line for each of these. An estimate that only covers "the migration" and treats these as afterthoughts is the leading cause of overruns.
Why S/4HANA Projects Go Over Budget
The query data is clear that "why do S/4HANA migrations go over budget" is something people search for after the fact. We wrote a dedicated playbook on recovering an at-risk migration in SAP migrations over budget: how to fix it. The root causes almost always trace to a small set of decisions made early:
- Fixed-price bidding on an unscoped project. When the scope is genuinely uncertain, a fixed price forces the integrator to either pad heavily or absorb risk they will later claw back through change requests.
- Skipping or rushing the assessment. The assessment is where you discover the custom code volume and data problems. Cutting it short does not remove the cost; it defers it to the most expensive phase.
- Scope creep disguised as "while we're in here." Process improvements that get bolted onto a technical migration expand the project without expanding the budget.
- Underestimating testing and data. The two most consistently underscoped areas, as above.
None of these are SAP problems. They are estimation and governance problems, which means they are preventable with the right approach to scoping and contracting.
How to Get a Defensible Estimate
The way to avoid the over-budget trap is to invest in the assessment before you commit to a number. A proper S/4HANA readiness assessment produces the inputs an estimate actually needs:
- A custom code inventory with a remediation classification, so you know how much of your code needs work and how much can be retired.
- An integration map of every interface and its migration disposition.
- A data assessment that quantifies volume, quality, and archiving opportunity.
- A landscape and sizing analysis for the target platform, whether on-premise, hyperscaler, or RISE.
- A path recommendation with the cost trade-offs of brownfield, greenfield, and selective transition made explicit.
This is why we advise clients to structure the engagement in two stages: a time-and-materials assessment that produces these inputs, followed by a build phase scoped against real data rather than assumptions. Going to market with a single fixed-price RFP covering assessment through go-live front-loads risk into a number that no one can yet stand behind.
You can start much of this analysis yourself. Our S/4HANA readiness checklist walks through the inputs above so you arrive at the estimate conversation with evidence rather than guesses.
What About RISE with SAP?
RISE changes the cost conversation by bundling infrastructure, some services, and licensing into a subscription. For many organizations this shifts capital expenditure to operating expenditure and simplifies the vendor relationship. It does not, however, make the migration itself free. The conversion or reimplementation effort, the custom code remediation, and the testing still have to happen and still have to be paid for.
The right way to evaluate RISE is on total cost of ownership over the contract term, not the headline subscription price. We model that trade-off as part of our SAP RISE migration work, because the answer depends heavily on your current infrastructure costs and your appetite for managing the platform yourself.
Budgeting With Clear Eyes
An S/4HANA migration is a significant investment, and the organizations that stay on budget are the ones that treat the estimate as a deliverable to be earned through assessment, not a number to be guessed at the start. Choose the path that minimizes total cost rather than upfront cost, itemize the components that usually get missed, and contract in a way that matches commercial structure to scope certainty.
If you want a defensible number for your landscape, our S/4HANA migration services begin with exactly the assessment described here, and if you are not ready to commit to a full migration, our ECC extended support planning can model the cost of waiting against the cost of moving now. Either way, the deadline is approaching, and the cost of a rushed, unscoped migration is always higher than the cost of a well-assessed one.