Most S/4HANA budgets start as one number from a vendor or integrator, and then they grow. You avoid that by building the budget line by line, knowing what drives each line, and sizing contingency to risks you can actually see. This guide walks through the eight lines a mid-size company should expect and where each one tends to break.

The short answer

  • Third-party benchmarks put an all-in S/4HANA migration at $2M–$5.5M for a company with 300–1,000 SAP users, and $5M–$14M when the landscape is complex.
  • Integrator fees are the biggest line, but data migration and schedule slip are where budgets break.
  • Size contingency from your own risks, not a flat percentage, and remember your current SAP fees keep running until cutover.

Start with the range, then take it apart

VendorBenchmark, which sells SAP pricing benchmarks, puts an all-in migration for a mid-size organization (300 to 1,000 SAP users) at $2M–$5.5M for standard complexity and $5M–$14M for more complex landscapes. LeverX, an SAP implementation partner, is lower, at $1.5M–$4M for a mid-market brownfield conversion. ERP Research offers a different rule of thumb: 1.5 to 3 times what your original ECC implementation cost.

Those ranges are wide because the total is the sum of eight lines that move independently. If you're still deciding whether to migrate at all, start with our comparison of your options after ECC maintenance ends in 2027. This post assumes you're pricing the migration.

What an S/4HANA migration costs a mid-size companyAll-in migration cost ranges, $M
$0M$5M$10M$15MMid-market brownfield (LeverX)Mid-market brownfield (LeverX): $1.5M–$4M$1.5M–$4M300–1,000 users, standard300–1,000 users, standard: $2M–$5.5M$2M–$5.5M300–1,000 users, complex300–1,000 users, complex: $5M–$14M$5M–$14M

Sources: VendorBenchmark and LeverX planning estimates, not SAP prices.

View the data
ScenarioRange
Mid-market brownfield (LeverX)$1.5M–$4M
300–1,000 users, standard complexity$2M–$5.5M
300–1,000 users, complex landscape$5M–$14M

The eight budget lines

LineWhat drives itBenchmark to anchor on
1. Licenses or RISE subscriptionUser types, modules, perpetual conversion vs. subscription15–30% uplift on existing license value to convert; new users $1,500–$4,200 each
2. Integrator servicesScope, day rates, delivery model, deviation from standard45–60% of total project spend
3. Data migrationData quality, number of sources, history keptAbout $570K–$1.53M for a mid-size enterprise
4. Custom code remediationVolume of custom objects and how many are still used15–40% of custom code unused for 24+ months
5. TestingEnd-to-end processes and interfaces, not users$1.0M in one partner's sample $7.55M budget
6. Internal staffExperts pulled off their day jobs, and backfill20–35% of total in large migrations
7. Parallel runningMonths of overlapping fees and systemsYour monthly maintenance × overlap months
8. ContingencyRisks you can nameBuilt from data and schedule risk (below)

Lines 1–4 and 6 from VendorBenchmark; line 5 from LeverX's hypothetical 2,500-user sample, larger than most mid-size companies. These are planning estimates from firms that sell benchmarks or services, not SAP price lists.

What drives each line

1. Licenses or RISE subscription

If you stay on-premise, VendorBenchmark reports a 15–30% uplift on existing license value to convert. On an illustrative $5M net license value, that's $750K to $1.5M ($5M × 15% and $5M × 30%).

If you go to RISE, you're pricing a subscription instead. In 2025 SAP replaced its RISE package with one called SAP Cloud ERP Private, priced on full-use equivalents (FUEs). The Register reported Gartner's warning that some volume tiers may see higher list prices per FUE, and its advice to revisit budgets built on earlier RISE estimates. If your business case uses an older quote, refresh it.

2. Integrator services

This is the largest line. VendorBenchmark's consultant day rates run $2,200–$3,600 at Big 4 and top-tier firms, $1,600–$2,600 at tier 2 SAP specialists, and $600–$1,200 for offshore-led teams. Offshore delivery cuts cost 35–55% but runs 15–25% longer. Fixed-price contracts typically land 10–18% below time-and-materials estimates, and staying close to SAP's standard processes cuts consulting by 20–35%, by the same source.

3. Data migration

Price four pieces separately: discovery and quality assessment ($120K–$280K for a mid-size enterprise), cleansing ($200K–$600K), tooling and execution ($150K–$400K), and validation ($100K–$250K). Data quality is the driver you control least, which is why this line overruns most.

4. Custom code remediation

Every custom object has to be analyzed, adapted, or retired, and VendorBenchmark calls this the most time-consuming and expensive part of a brownfield migration. Find out what's still used before you pay to fix it. The same source estimates a 3–4 month rationalization can cut $500K–$3M from consulting on mid-to-large projects.

5. Testing

Budget for several cycles: integration, user acceptance, and at least one full cutover rehearsal. Testing doesn't stop at go-live, either. Under RISE, SAP executes technical upgrades, but SAP's own training material says planning, preparation, and testing remain the customer's job.

6. Internal staff

Your best finance, supply chain, and operations people will spend months on design and testing. If you don't backfill them, the cost shows up as slower closes and missed targets instead of on the project ledger. Count it either way.

7. Parallel running

Your ECC maintenance doesn't stop when the project starts. At 22% of net license value, which ERP Research cites as standard, a $5M license costs about $1.1M a year, or roughly $92K a month ($1.1M ÷ 12). If a new subscription starts before cutover, you pay both.

8. Contingency

Covered below, because it should be built from your risks, not picked.

Why projects overrun

Panorama Consulting's 2026 ERP Report, as summarized by TechTarget, found about three in ten respondents went over budget, citing scope growth, technical and organizational problems, underestimated staffing, and extra technology purchases. SAP migrations add their own pattern:

  • Data. VendorBenchmark says organizations often spend 2–3 times their initial data migration budget.
  • Schedule. Brownfield programs benchmarked at 9–15 months commonly run 3–6 months over, for an actual median of 14–20 months. Every extra month adds integrator burn and parallel fees.
  • Custom code. Discovery finds more objects, or harder ones, than the estimate assumed.
  • Staffing. Internal experts are double-booked, so design decisions slip, and so does everything downstream.

A contingency you can defend

A flat 10% looks tidy and means little. Build contingency from the two risks with the best data behind them:

  1. Data risk = initial data budget × 1. That's the gap between budgeting once and spending twice, the low end of VendorBenchmark's 2–3x finding.
  2. Schedule risk = expected overrun months × (monthly integrator burn + monthly parallel fees).

Illustrative example: a $900K data budget, a four-month overrun, $150K a month of integrator burn, and $92K a month of ECC maintenance. Data risk is $900K. Schedule risk is 4 × ($150K + $92K) = $968K. Contingency comes to about $1.87M. That's large on a $4M program, and that's the point. If the number feels unaffordable, reduce the risk (profile data early, retire unused code, freeze scope) rather than the contingency.

Compare the total, not the first invoice

Once you have all eight lines, add five years of post-migration subscription or maintenance and compare that total with the alternatives: staying put for a while, third-party support, or replacing the workflows that carry most of your custom code. We offer that last option, so weigh our view accordingly. The comparison only means something with your own contract figures in it.

Seven questions before you approve the budget

  1. What's our net license value, maintenance rate, and renewal date? Parallel running and conversion costs both start here.
  2. How many custom objects do we have, and how many ran in the past 24 months?
  3. Has anyone profiled our master data? If not, your data line is a guess.
  4. Is the integrator proposal fixed-price or time-and-materials, and what's excluded?
  5. Which internal people are on the project, and who backfills them?
  6. How many months of overlapping fees does the plan assume?
  7. Is our RISE or license quote current under SAP's 2025 packaging?

Where to go from here

Build your eight lines before you sign a statement of work. If you'd like a second set of eyes on the numbers, tell us what you run and what you've been quoted, and we'll give you an honest read. To see how a staged alternative works, visit our Escape SAP page.

Sources