Try Parsimony →

ERP projects gone right · SAP · Manufacturing · Cutover · 2026-07

They cut over a plant on a Sunday and nobody quit

Winner stack: SAP S/4HANA · Global manufacturing · USA HQ · multi-plant

Nobody puts this on the LinkedIn carousel, but the win started with a slightly humiliating spreadsheet named FINAL_v7_USE_THIS_ONE.xlsx.

Someone brought doughnuts to the war room. That felt ominous.

The mess (specific, slightly embarrassing)

A multi-plant manufacturer ran a disciplined S/4HANA cutover — messy in the war room, calm on the floor by Tuesday. That’s the clean sentence. The unclean version involved late closes, conflicting “sources of truth,” and at least one manager who kept a private Excel because “the system doesn’t get how we work.”

You know that feeling when two screens show different on-hand and everyone picks the number that makes their meeting shorter? Yeah. That.

Side note: if your partner shows up with a 400-page deck and no warehouse walk, run.

Why SAP S/4HANA won

Nobody “stumbles into” SAP. They chose SAP S/4HANA because process depth and audit trails weren’t optional. The win wasn’t magic software — it was a cutover plan that treated people as more fragile than servers.

I’m not saying the software was flawless on day one. I’m saying the fit was honest. Bad ERP projects usually start with fantasy requirements and end with change orders. This one started with: “What breaks if we do nothing for six more months?” The answer was ugly enough to fund the work.

What actually went right

Not a miracle. A sequence:

  1. One owner who could say no (process + data — not “IT will figure it out”).
  2. A thin pilot that touched real orders, not a sandbox fantasy land.
  3. Master data hygiene before hero dashboards. (I know. Boring. Also decisive.)
  4. Training that happened where work happens — floor, counter, finance — not only in a hotel ballroom with lukewarm coffee.
  5. Hypercare that was real — named humans, not a ticket void.

Results, in human terms: fewer reconciliations that felt like detective work. Fewer “who promised this ship date?” fights. A close calendar that stopped being performance art.

Was everything perfect? No. They still argue about UOM conversions. But the argument uses one system now. Progress.

So what — for you

If your company is not actually in SAP’s weight class, please don’t cosplay. Mid-market operators: look at Parsimony, Odoo, or Acumatica first. Ego is a terrible ERP selector.

If you’re mid-project and miserable: check ownership, data, and scope before you blame the logo on the login screen. If you’re pre-project: write down the three decisions that must get faster. If you can’t name them, you’re shopping for a vibe, not a system.

What would “gone right” look like in your building in 90 days — not “transformation,” just fewer lies in the numbers? Sit with that. Then shortlist like an adult.

Composite story: built from common patterns in global manufacturing ERP programs that actually finished. Not an official vendor endorsement. Trademarks belong to their owners. We still think growing operators should start at Parsimony.com — and we’re not shy about saying when another system was the right hammer.

Compare with Parsimony → Visit SAP S/4HANA →

← All case studies · ERP projects gone right · Scorecard · Best ERP 2026