By: Vito Evko
If you’ve been in the ERP world long enough, you start to collect stories and not the success stories (those are easy). I’m talking about the “ERP horror stories”. The kind of projects that still make CFOs twitch when you mention the word “migration.”
Over the years, our team at SOS Consulting Services has been brought in to rescue more than a few ERP implementations gone wrong. The good news? Every disaster came with a crystal-clear lesson that helped the company get back on track and can help you avoid the same pitfalls.
So grab a cup of coffee, settle in, and let’s take a short walk through the ERP haunted house… and talk about how to keep your business out of it.
Horror Story #1: The Case of the Missing Data Cleanup
A mid-sized professional services firm once rushed headfirst into a new ERP system. They were excited and looking forward to new dashboards, new automation, new workflows.
But there was one problem.
Actually, 47,000 problems.
Specifically: 47,000 duplicate vendor, customer, and item records.
When they went live, the new system didn’t magically “fix” the data. It just carried all the bad habits forward. Reporting was a mess, AP couldn’t select the right vendors, and leadership couldn’t trust their financials.
Lesson:
An ERP is only as clean as the data you bring into it.
Do the cleanup now or live with the cobwebs forever.
Horror Story #2: The “We’ll Figure Out Processes Later” Catastrophe
Another business — a fast-growing distributor, implemented their system exactly as their old one worked. No process redesign. No discussions about how they could improve inventory accuracy or streamline purchasing.
They wanted “same thing, new system.”
Well, that’s exactly what they got.
A shiny new ERP… with the same old inefficiencies.
Within months, they called us.
They didn’t have an ERP problem. They had a change management problem.
Lesson:
Implementing a new ERP without improving your processes is like buying a luxury car and never leaving first gear.
Use your implementation as a chance to rethink how your business should run.
Horror Story #3: The Ghost of the Abandoned Consultant
This one still shows up in my nightmares.
A client hired a consultant (not us!) who dazzled them in the sales cycle. Great presentation. Smooth talking. Gold watch. You know the type.
But after the contract was signed?
Vanished.
He outsourced everything to a junior team with no experience in their industry. The configuration didn’t fit the business, workflows broke constantly, and users abandoned the system within weeks.
By the time we were called in, morale was low and trust was gone.
Lesson:
It is a fact that the success of your ERP actually depends more on who implements it than the software itself. I stress this constantly.
Choose a partner who understands your industry, your data, and your people, not just someone who can finish a demo the fastest.
Horror Story #4: The Rushed Go-Live
A healthcare organization was determined to go live before year-end. Their reasoning made sense: clean cutover, fresh fiscal year, fresh start.
But there was one small issue: they weren’t ready.
Training wasn’t complete.
Testing wasn’t complete.
Their chart of accounts wasn’t even finalized.
Still, they insisted: “We have to go live December 1.”
Well…
On December 2, panic ensued.
Nothing reconciled.
AP couldn’t cut checks.
Leadership couldn’t get reports.
We pushed for an immediate stabilization plan, retrained their users, and rebuilt key pieces of their configuration.
Lesson:
A go-live date should be based on readiness, not the calendar.
No one remembers a go-live that was pushed back a month.
Everyone remembers one that went live too soon. Our method includes a detailed project plan that works backwards from the projected go live date. If every task isn’t listed as completed before the go live date, then the go-live date needs to be amended to insure a successful go live.
How to Avoid Becoming the Next Horror Story
Here’s the good news: every one of these nightmares is preventable. Here’s how:
Start with clean, structured, validated data
Garbage in → garbage out. Always.
Redesign your processes, don’t just replicate old ones
Use your implementation as an opportunity to modernize.
Choose an implementation partner you trust
And who will actually be there after the kickoff meeting.
Don’t rush — go live when ready
A solid go-live is worth more than a fast one.
Train your users early and often
Adoption is the heartbeat of ERP success.
Final Thought
ERP projects don’t have to be scary. They can (and should) be transformative, empowering, and energizing for your whole business.
At SOS Consulting Services, we’ve seen what happens when companies try to do it alone, or when they put their faith in the wrong partner. And we’ve also seen what happens when it’s done right: clarity, confidence, and control.
If you’re planning a new ERP project, or recovering from a past one, we’re here to help you write a very different kind of story.
Until next time,
Vito Evko
Managing Partner
SOS Consulting Services, Inc.
in your business right now?
