Yes, SAP is one of the largest ERP vendors in the world, and SAP ERP is the name of its core system. SAP now sells three main ERP lines: SAP S/4HANA for large and mid-size firms, SAP Business One for small firms, and the older SAP ECC. SAP is retiring ECC support by 2027, according to Ramp's research.
This matters most for IT and finance leaders still running SAP ECC, since that old system loses mainstream support soon and needs a migration plan. It also matters for small firms sizing up SAP Business One against lighter tools, since SAP's own cost and setup effort often outgrow what a small team needs.
🏢 Which SAP products count as ERP, and which one fits your size
🔍 How SAP S/4HANA, SAP ECC, and SAP Business One differ
📊 What a real SAP ERP rollout costs and how long it takes
💡 A worked walkthrough for sizing your own decision
✅ The mistakes that turn a SAP rollout into a public failure
What Counts as SAP's ERP Lineup
SAP sells more than one ERP product, and the differences between them decide whether a project succeeds or turns into a costly mess. SAP S/4HANA is SAP's current flagship system. It launched in 2015 on the HANA in-memory database, and it comes in cloud and on-premise versions. SAP ECC, sometimes called plain SAP ERP, is the older system most large firms still run today, and Wikipedia lists its last major update in 2016.
SAP Business One is built for small firms that want core accounting, stock, and sales tools in one place. It has no deep production or multi-entity layer, and it is not meant to run a global firm. Each of these three products asks a different question of a buyer: how much room do you need to bend the system, and how much can you spend to get it.
Pricing and setup details reflect SAP's current ERP pages as of 2026. SAP does not publish flat pricing for S/4HANA or ECC. Every quote depends on modules, users, and deployment type, so confirm current terms with an SAP partner before you plan a budget around any figure here.
The line between these three products matters because ECC is on a clock. SAP is ending mainstream ECC support by 2027, according to Ramp's research, which means most firms still on ECC are actively planning a move to S/4HANA right now. A firm that waits too long risks running unsupported software past that date, with no new vendor patches for tax-rule changes or security holes.
S/4HANA itself splits further into Public Cloud and Private Cloud editions, and the choice between them shapes both cost and speed. The Public Cloud edition uses SAP's standard, preset steps and goes live fast. The Private Cloud edition allows deep custom work but takes longer to set up and costs more to run over time. A firm picking between these two editions is picking between speed and fit, not between two products with the same trade-offs under different names.
How SAP's Three ERP Products Differ From Each Other
Naming three products does not explain them, so here is the real gap that matters: how much custom work each one allows, and at what cost. SAP ECC allows deep custom work but is now old technology. Wikipedia notes it has been superseded by S/4HANA as SAP's lead product. A firm still on ECC keeps its old custom code running, but it gets no new features and faces a hard support cutoff.
S/4HANA Cloud Public Edition trades some of that custom room for speed. It runs on SAP's standard steps, and a focused rollout can go live in three to six months, according to Ramp's own research on SAP timelines. S/4HANA Cloud Private Edition and full on-premise S/4HANA keep more room for custom work, but a heavy, on-premise build with real custom code can stretch well past a year.
SAP Business One sits in a different class entirely. It has no deep production or multi-entity layer, and it is not built to run a global firm. Ramp's research notes that cost and setup effort still make SAP a heavier lift than many small firms need, even on Business One, which is why lighter rivals often win in that segment.
The deployment choice also changes who owns the tech behind the scenes. Cloud editions put SAP in charge of servers, security patches, and upgrades. On-premise ECC and on-premise S/4HANA put that load on the firm's own IT staff, a real cost most buyers underrate before they sign a contract.
That underrated cost shows up fastest in staffing, not software. A firm that picks on-premise S/4HANA needs its own database and security staff on call, year-round, not only during the rollout itself. A cloud edition removes that staffing need entirely, since SAP's own team handles patching and uptime behind the scenes, day and night, all year.
Which SAP ERP Situation Applies to You?
The right starting point depends on what system you run today and how much custom work your operation truly needs, not on company size alone. Use the four cases below to find the one closest to your own, then read the linked detail for that fit. Each case names a specific signal to watch for, not only a company profile, since the signal is what tells you when to move.
A Large Enterprise Still Running SAP ECC
If your firm still runs SAP ECC, the 2027 support deadline is the fact that should drive your timeline, not a vague sense that a migration can wait. Start by mapping which ECC custom code you rely on each day, since many firms find years of custom work nobody now remembers building. A full on-premise S/4HANA move with real custom work can run well past a year, so a firm starting to plan in 2026 is already working against the clock.
Bring in a small team early to answer one question: what would break if we turned this custom code off tomorrow. Most firms find the honest answer is far shorter than the list of code sitting in the system. That shorter list is what drives the timeline and cost of a real migration plan.
A Mid-Size Company Evaluating Cloud ERP
If you are picking your first real ERP system, or replacing a patchwork of spreadsheets and smaller tools, S/4HANA Cloud Public Edition is usually the starting point SAP steers you toward. It runs on SAP's standard, preset steps, which is why a focused rollout can go live in three to six months instead of a year or more. The trade-off is less room to bend the system around a workflow that does not match SAP's standard model.
Watch for one early warning sign during the sales process: a partner who promises a fully custom fit on a Public Cloud timeline. That combination rarely holds up once real data and real workflows enter the picture, so a firm hearing that promise should ask hard questions before signing anything. A partner who welcomes those questions, instead of brushing past them, is usually the safer choice for the whole project.
A Small Business Weighing SAP Business One
If your business has a small finance team and modest complexity, SAP Business One can work, but weigh the real cost and setup effort against your needs first. Many small teams find that cost and setup effort outweigh the benefit, since a smaller platform covers the same core accounting and stock tasks with less setup. Ask what SAP Business One would replace, and whether a lighter tool already handles that job well.
A useful gut check: count how many of SAP's deeper features, multi-entity reporting, advanced production planning, a small team would use in its first year. If the honest count is close to zero, that gap is the clearest sign a lighter platform fits the business better today. Revisit that count once a year, since a firm that grows into a second entity or a larger warehouse footprint may outgrow the lighter tool later on.
A Company That Needs Deep Customization
If your business has workflows so specific that a standard cloud process cannot fit them, on-premise S/4HANA or the Private Cloud edition is built for that case. This fits makers with unusual production steps or firms with reporting rules that a plain module cannot cover. The cost of that flexibility is a longer, pricier rollout, so weigh the real need for custom work against a faster, cheaper Public Cloud path first.
Test that need honestly before you commit to the slower path. Write down every workflow you believe cannot run on a standard system, then ask a partner to show you why. Only a handful of workflows are truly hard to replace at most firms, and sorting those out is what keeps a custom project from growing past its budget. Firms that skip this step often learn, well into the project, that half their "must-have" list was never truly needed.
Sizing the Decision: A Worked Example
Real dollar figures make this choice easier to picture than percentages alone. Wikipedia's summary of SAP costs says a Fortune 500 firm's software, hardware, and outside help can run from $50 million to $500 million, with big upgrades adding $50 million to $100 million more on top. A mid-size firm under 1,000 staff tends to spend closer to $10 million to $20 million for a like-for-like rollout, per that same summary.
Take a 700-employee maker weighing S/4HANA Cloud Public against a full on-premise build. The cloud path fits near the low end of that mid-size range, and its 3-to-6-month timeline lets finance staff plan around a known go-live date. The on-premise path would let the firm keep old custom code from its ECC system, but at a much higher cost and a rollout that could run past a year. Neither path is wrong on its own; the right fit turns on what that custom code truly does for the business each day.
The real question is not "can we afford the bigger number," but "do we need the extra work badly enough." A firm whose old code turns out to be five reports nobody uses does not need the pricey path. A firm whose old code runs its whole production line may have no real choice but the slower route. Write both paths down side by side before anyone signs, since seeing them on paper makes the trade-off far easier to defend to a finance team later.
Run this same logic before signing anything. List every custom workflow your team believes it needs, then price each one against the time and cost of the faster, standard path. Most companies find that only a handful of workflows are genuinely irreplaceable, and that discovery alone can shift a project from the expensive tier to the cheaper one.
Where SAP ERP Rollouts Go Wrong
Two sourced accounts, from people who have lived through SAP rollouts, teach different lessons about the same broad risk. One is about overselling at the start, and the other is about under-scoping the legacy mess a migration has to clean up. Read both before assuming your own project only faces one of these two risks.
One SAP builder with 15 years on the job told a common story. A firm under new leadership wants to grow fast, calls in SAP, and gets sold on a pitch where the sales team oversell the SAP features with a slick demo. Go-live day comes, the promised scope proves harder than sold, the timeline stretches, and the budget grows right along with it. That gap between the pitch and the real system is a common complaint in first-hand accounts of big ERP rollouts.
A second voice made a related but separate point. It takes real work to detangle legacy enterprise systems built up over decades, most of all once the staff who wrote that code have left the firm. This is the specific risk for any firm still on SAP ECC, since years of old, unwritten-down code can turn a planned move into an open-ended hunt. The lesson differs from the overselling problem: even an honest SAP partner cannot make old, unwritten-down code vanish on schedule.
| Risk pattern | What it looks like in practice |
|---|---|
| Overselling at the pitch stage | Promised features do not survive contact with real data and workflows |
| Undocumented legacy customization | Nobody left at the company can explain what the old code does |
Public, well-known cases echo both patterns at real firms. One detailed case study tells how Revlon's own shareholders sued the firm over a rough S/4HANA rollout in 2018, with real costs on top of the suit itself. Computerworld reported that Waste Management sued SAP too, saying SAP showed a mock-up, not real, working software, during its sales process. Both cases teach the same lesson: a rollout can look fine on paper right up until real users and real data expose the gap.
| Company | What went wrong |
|---|---|
| Revlon (2018) | Shareholders sued the company over a troubled S/4HANA rollout |
| Waste Management | Lawsuit alleged sales demos did not reflect real, working software |
SAP ERP Products at a Glance
The comparison below covers the four editions most buyers choose between. Read "best fit" as a starting point, not a rule carved in stone. A firm that sits between two rows should weigh its real need for custom work over its size alone, the same lesson the four segments above walk through in more depth.
Notice that customization room, not company size, is the real axis running through this table. S/4HANA Cloud Public and SAP Business One both trade deep custom work for a faster, cheaper path. S/4HANA Private and on-premise ECC both keep that room, at real cost in time, money, and IT staffing.
| Product | Best fit | Deployment | Typical timeline |
|---|---|---|---|
| SAP S/4HANA Cloud Public | Mid-size to large firms wanting speed | Cloud, SAP-managed | 3 to 6 months |
| SAP S/4HANA Private/on-premise | Large firms needing deep custom work | On-premise or private cloud | A year or more |
| SAP ECC | Legacy, still common at large firms | On-premise | Support ends 2027 |
| SAP Business One | Small firms with simple needs | Cloud or on-premise | Weeks to a few months |
Use this table to narrow your shortlist, then weigh it against the real cost of custom work from the worked example above. The two practitioner lessons above matter more than the table alone. A fast timeline only holds if the sales pitch matches what the system can truly deliver, and an old ECC system only migrates smoothly if someone on staff can still explain its custom code.
Treat this shortlist as the start of a talk with a partner, not the end of your search. Bring your own real trigger into that talk: a support deadline, a small team weighing SAP against a lighter tool, or a firm with work no standard system can fit. Waiting on that talk has its own cost, since each month on the wrong-sized system is a month of manual work or risk a better fit would remove.
Mistakes to Avoid
- Waiting too long on an ECC migration. SAP's mainstream ECC support ends by 2027, and a company that starts planning in the final year risks running unsupported software with no security patches.
- Trusting a sales demo without a pilot on real data. A polished demo can promise features that real workflows and real data volumes cannot support once the project moves to delivery.
- Underestimating undocumented legacy customization. Years of custom ECC code built by staff who have since left the company can turn a planned migration into months of unplanned discovery work.
- Choosing SAP Business One when a lighter tool would do. SAP's own cost and complexity often outweigh the benefit for a small team with simple accounting and stock needs.
- Picking on-premise S/4HANA by default. A full custom on-premise build can take a year or more, when a large share of "must-have" custom workflows often turn out to be unnecessary once reviewed.
- Skipping a clear list of required customizations before scoping the project. Without that list, a company cannot tell whether the faster Public Cloud edition would have worked all along.
- Ignoring who owns infrastructure after go-live. On-premise deployments shift server maintenance and security patching onto the company's own IT team, a cost that is easy to miss during initial planning.
- Signing a contract before checking references from a similarly sized company. A reference from a much larger or smaller company tells you little about your own project's real risk and cost.
Rollout Guidance
Do
- List every custom workflow before scoping the project. This tells you whether the faster, cheaper Public Cloud edition can cover your real needs.
- Ask for a pilot on your own data. A pilot exposes gaps a polished demo will never show you.
- Check the ECC support deadline against your own timeline. Starting a migration years ahead of 2027 avoids a rushed, risky final-year scramble.
- Get references from a company your size. A Fortune 500 reference tells a 200-person company little about its own real costs and risks.
- Budget for infrastructure ownership, not only software cost. On-premise deployments carry ongoing IT costs that a cloud edition removes.
Don't
- Don't accept a sales pitch as a delivery guarantee. Ask specifically how the promised features will be tested against your own data before you sign.
- Don't assume old customizations are simple to migrate. Confirm someone on staff can still explain what each custom process does today.
- Don't default to SAP for a small business without comparing lighter tools first. SAP's own research shows cost and complexity often outweigh the benefit at small scale.
- Don't skip a realistic timeline estimate. A rushed schedule is a common thread in the public failures tied to SAP rollouts.
- Don't treat the cheapest quote as the safest choice. A cut-rate implementation partner with no experience in your industry can cost more in delays than it saves upfront.
Pros and Cons of Choosing an SAP ERP System
Pros
- A genuine product tier for every company size. S/4HANA, ECC, and Business One give buyers a real range, from small business to global enterprise.
- Deep customization available where it is genuinely needed. On-premise and Private Cloud editions support workflows a standard system cannot.
- A fast, standard path exists too. S/4HANA Cloud Public Edition can go live in three to six months for companies that do not need heavy customization.
- A large, established partner and support network. Decades of SAP implementations mean experienced partners are easier to find than for newer ERP entrants.
- Clear signals for when to move on from ECC. The 2027 support deadline gives planners a concrete date to work backward from.
Cons
- Cost and complexity can outweigh the benefit at small scale. SAP's own research points to lighter tools serving small businesses better in many cases.
- On-premise and heavily customized builds run long. A full custom rollout can take a year or more, tying up budget and staff for an extended stretch.
- The gap between sales pitch and delivery is a well-documented risk. Practitioner accounts and public lawsuits both point to overselling as a recurring failure mode.
- Legacy ECC customization is a genuine migration risk. Years of undocumented custom code can turn a planned project into an open-ended one.
- Infrastructure ownership shifts to the company on-premise. Server maintenance and security patching become an ongoing internal cost, not a vendor-managed one.
What to Do Next
- Identify which SAP product you run today, or are evaluating, and check it against the segments above.
- If you are on ECC, confirm your internal timeline against the 2027 mainstream support deadline.
- List every custom workflow your team believes it needs, and price each one against the faster, standard cloud path.
- Request a pilot on your own real data before signing any implementation contract.
- Ask for references from a company close to your own size and industry, not the vendor's biggest success story.
- Budget for who will own infrastructure, security patching, and upgrades after go-live, not only the initial software cost.
Frequently Asked Questions
Does SAP make its own ERP software?
Yes. SAP builds and sells SAP ERP directly, including the legacy SAP ECC system and its current flagship, SAP S/4HANA, rather than reselling a third party's platform.
What is the difference between SAP ECC and SAP S/4HANA?
SAP ECC is the older, legacy system, and SAP S/4HANA is the current flagship. S/4HANA runs on an in-memory database and adds embedded AI, while ECC is being retired from mainstream support by 2027.
Can a small business use SAP ERP?
Yes, through SAP Business One, but it is not always the best fit. SAP's own research notes that cost and complexity often outweigh the benefit for small teams with simple accounting and stock needs.
How long does a typical SAP ERP implementation take?
Three to six months for a focused S/4HANA Cloud Public Edition deployment, according to Ramp's research, while a heavily customized on-premise build can take a year or more.
How much does a SAP ERP rollout typically cost?
It varies widely by company size. One account puts Fortune 500 costs at $50 million to $500 million, and mid-size companies under 1,000 employees closer to $10 million to $20 million.
Is SAP ECC still supported?
Only for a limited time. SAP is ending mainstream support for ECC by 2027, which is pushing most remaining ECC customers to actively plan a migration to S/4HANA now.
What is the difference between S/4HANA Cloud Public and Private editions?
Public Edition uses SAP's standard processes and deploys faster, while Private Edition allows deeper customization at a higher cost. Most companies without unusual workflow needs start with the Public Edition.
Does SAP ERP include payroll and HR tools?
Yes, in most of its major products. SAP ECC includes a human capital management module for training, payroll, and recruiting, and S/4HANA carries comparable HR capability.
What are the alternatives to SAP for mid-market companies?
NetSuite is a common alternative. It is a cloud-native ERP covering financials, inventory, and CRM in one platform, generally with less complexity than a full SAP deployment.
Why do SAP ERP rollouts sometimes fail publicly?
A mismatch between the sales pitch and real delivery is a recurring cause. Public cases, including a lawsuit alleging SAP demonstrated software that was not fully built, show this is a known industry risk, not a rare fluke.
Can a company keep using SAP ECC past 2027?
Technically, yes, but without mainstream vendor support. Running unsupported software means no new security patches or tax-rule updates from SAP, which raises real operational risk over time.
Does moving from ECC to S/4HANA require starting over?
Not entirely. SAP offers migration paths that can carry over data and some configurations, though heavily customized ECC systems often need real rework rather than a simple lift-and-shift.