When a company decides to replace its ERP system, it’s tempting to think of it as a technology project: swap out the old software, turn on the new, and carry on. In reality, it’s more like open-heart surgery.
High stakes, complicated, and risky — but if it’s done well, the business emerges healthier and better equipped for growth.
Why companies undertake ERP change
There are usually two reasons. The first is that the current system is no longer fit for purpose — the platform is reaching end of life or losing vendor support, or it simply no longer keeps up with the business (designed for a smaller company, a different industry, or a different era). The second driver is growth: the business needs capabilities the old ERP can’t deliver, like operating across multiple countries, integrating acquisitions, or improving customer visibility.
I worked with one client facing the end-of-life challenge. Their provider announced support was ending, so they moved quickly to keep the lights on. The good news: they kept running. The bad news: it took much longer than expected to build out the new capabilities and benefits they really needed.
The biggest mistake — treating it like a tech swap
Too often, leaders treat ERP as an IT upgrade and hand it to the technology team to “make it happen.” That couldn’t be further from the truth. ERP changes business processes, the way teams work together, and even how customers experience the company. It’s not a Band-Aid. It’s open-heart surgery — and it has to be treated with the same seriousness.
Define success before you start
One of the most dangerous traps is chasing the shiny object. A vendor demo looks slick; a trade-show presentation makes it seem like every problem will disappear. But new features aren’t the same as new capabilities. The first step isn’t software selection — it’s defining success. What do we want this system to enable? More efficient operations? Integration across acquisitions? Better customer experience? When leadership aligns on these outcomes, the project has a clear compass. When they don’t, it drifts — or stalls.
Focus on what’s critical, not everything
Trying to document every single process in detail is a recipe for delay and exhaustion. The smarter path distinguishes between two categories:
- Mission-critical or differentiating processes — these make the company unique, improve customer intimacy, or give a competitive edge. Document, protect, and embed them in the new ERP.
- Commodity processes — essential but not differentiating, like accounts payable. Here, efficiency and consistency matter more than uniqueness, and the new ERP standard is often good enough.
The real challenge comes when you’re not just shifting from one standard process to another, but consolidating multiple ways of working into one — especially in acquisitive businesses where five companies all run the same process differently. That’s harder than moving from an old standard to a new one, but it’s also where the biggest gains are made.
People make it work
Technology won’t save you without the right leadership in place. Successful ERP implementations have two leaders working side by side:
- A business lead accountable for outcomes — efficiency, revenue growth, customer experience.
- A technology lead accountable for system build, configuration, and integration.
These two roles must be joined at the hip. Vendors and consultants can help, but ownership has to stay inside the business.
ERP isn’t IT’s project. It’s the company’s transformation — treat it with the seriousness of open-heart surgery. The health of your business depends on it.
