Ask anyone who has lived through an ERP implementation what it was like and you’ll get one of two answers. It was the best thing the company ever did, or it was a nightmare.
Both are fair, and the software is rarely the reason. What makes an ERP implementation successful is mostly decided before any configuration starts, by whether the awkward questions were asked at the beginning or six months in.
These are the ten things we’ve seen matter most, whether you are replacing a legacy system or putting in ERP for the first time.
-
01
Decide what the ERP is for
Before the first vendor demo, get the team in a room and answer one question: why are we doing this? Name the problems the system should solve, and be honest about whether they are technology problems or process problems. You’ll come back to those answers at every decision that follows.
-
02
Choose an implementation partner who will argue with you
ERP isn’t plug-and-play, and you’ll need help long after the contract is signed. Look for a firm that has done the work in your industry, and ask to see past projects as well as credentials.
One more test: do they push back? A partner who agrees with everything you say isn’t doing their job.
-
03
Bring the business in early
This is where a lot of ERP projects quietly go wrong. Sign-off from a VP is not the same as involvement. Finance, HR, Supply Chain and Operations have to help make the decisions, or they’ll have workarounds in place before you’ve said “go live”.
-
04
Write down how the work really gets done
Map your current processes as they are, including the exceptions and the manual fixes that keep things moving. Only then design the workflows you want. Skip this and you’ll rebuild the same problems in a nicer interface.
-
05
Clean the data before you migrate it
Nobody enjoys data cleanup, and it is where the most damage gets done. Bad customer records, duplicate vendors and out-of-date product information will all make the trip to the new system unless someone removes the junk, agrees on naming and checks accuracy first.
Sign-off from a VP is not the same as involvement.
-
06
Treat change management as real work
A good ERP will still fail if people don’t use it properly, and resistance rarely announces itself. You notice it in dropped tickets, spreadsheets kept on the side and frustrated team leads.
What helps is unglamorous: honest updates, training built around people’s actual jobs, and someone on call for the first few weeks.
-
07
Set the budget and the timeline together
Software is only part of the cost. Training, support and the disruption of the changeover all need a line in the budget. Then split the work into phases with milestones you can realistically hit.
-
08
Keep the training going
People learn a system by using it, so a single three-hour session before launch won’t stick. Train by role, write short how-to guides, record quick screen-share videos, and keep support going after go-live.
-
09
Test with real work before go-live
Use real tasks. Can Finance process an invoice? Can Procurement approve a purchase order? Can the warehouse track stock accurately? Have team leads try it themselves, while there is still time to fix what they find.
-
10
Plan for life after go-live
Go-live is the beginning. The system will keep changing as you add processes and integrations, so put a routine in place: a monthly check-in, a way for users to give feedback, and refresher training.
Three smaller things that help
- Start with one department.Extend to the others once that team is comfortable.
- Keep the documentation current.Update process flows and configurations as they change.
- Name a few go-to people.They can help new users and sort out small problems quickly.
Before you begin
An ERP implementation can be one of the best decisions your business makes, as long as the planning behind it is practical. Talk to your teams first.
Questions people ask about ERP implementation
What makes an ERP implementation successful?
Mostly the groundwork: clear goals, a partner who knows your industry, the business involved from the start, clean data, and proper training and testing before go-live.
Why do ERP implementations fail?
Rarely because the software doesn’t work. More often the right questions were raised too late, the people who use the system were left out of decisions, or bad data was migrated as it was.
What should happen after ERP go-live?
Keep support and training in place, hold a monthly check-in, and give users a way to send feedback.