ERP Insights

The 5 Most Common Reasons ERP Implementations Fail

Posted In:
Updated On:
Erp implementation failures
Adam Taylor
Author Adam Taylor

ERP implementations usually go wrong for very human reasons. Top10ERP advisory board member Adam Taylor breaks down the five most common failure points, from vague goals to messy data migrations, along with the questions that will help you plan around them.

In this article we cover

Whether you’re implementing an ERP from scratch or swapping out an existing system for a new one, there are a multitude of things that can, and often do, go wrong. Most of these aren’t failures of the software itself, but rather the humans and planning that connect the software to the business. As Eisenhower said, ​“Plans are worthless, but planning is everything.” 

Below is a brief survey of the most common failure points ERP implementations will encounter, along with ideas and questions to build a plan around them.

Erp implementation failure timeline
ERP Implementation Failure Timeline

1. No Clear, Measurable Outcome

The root cause of most failed (or more painful than necessary) ERP implementations is that they don’t start with a clearly defined, measurable outcome. Goals like ​“modernize operations” fail to define exactly what numbers or outcomes we should see to declare success. Without these defined, measurable goals, every stakeholder involved will answer questions like ​“Are we done?” and ​“Is this a reasonable trade-off?” differently. 

And outcomes don’t always have to be numbers. ​“Customers are happier within three months of implementation” is a perfectly good goal, whether you measure it through interviews or a Net Promoter Score (NPS) score. What matters is that it can be measured.

Questions to help define outcomes:

  • If you could wave your magic wand and improve the business, what things would improve and, critically, how would you know they improved?
  • What must be true at the end of this implementation to consider it a success?
  • What are you willing to compromise or ignore to support your most important outcomes?

2. Missing the Ground-Level Perspective

This brings us to the next major failure point: lack of ground-level perspective. When the C‑suite makes a purchasing decision for a tool that’s used by the people on the floor, there can be a gap between budget and day-to-day workflows. Ensure the people who will use each feature/module have had a chance to provide input on what they need.

Use the Implementation to Fix Processes

Use this time strategically. You’d be hard pressed to find a better moment for process improvement throughout the company. We frequently advise that processes be heavily scrutinized while gathering the feedback from the people who run those processes and will use the new ERP. 

For example, maybe Process X was introduced 10 years ago when the last ERP was built because it couldn’t flexibly accommodate the employees’ ideal workflow. Perhaps now it can! Or maybe Process Y only exists to support a tiny edge-case that the C‑suite agrees should be thrown out altogether. Those are business-specific questions only you can answer, but planning a new ERP implementation or migration is the ideal time to ask them. 

The worst-case scenario is to plan on implementing a new ERP without taking the time to improve any processes, as this frequently just cements ​“well-we’ve-always-done-it-this-way” processes.

These questions can help identify perspective issues:

  • If you were building your own system, whose input would you need to build the system correctly?
  • Of these requirements (features, workflows, etc.), which ones could change if you wanted them to? Which ones are set in stone due to government regulations, industry standards, etc.?
  • Does every facet of the business represented by your ERP (accounting, shipping, sales, etc.) know what you’re planning? Do they have a way to test and provide input on the new system?
  • Who has the final say when perspectives conflict? (Hint: It shouldn’t always be the CEO!)

3. Avoiding Trade-Offs

While gathering perspectives and use-cases, a common failure point is to consider them all equally important. If everything is important, then every idea, feature, or ​“Wouldn’t it be cool if?” is going to land on the roadmap, blowing up your timeline and budget. 

“Trade-off” is not a dirty word; it’s how you hit goals. Software (and business as a whole) is a game of trade-offs. While we’d all rather have our cake and eat it too, avoiding tradeoffs is how you end up over-budget, with deadlines missed by months. 

For example, on-premise ERP deployments may be a non-negotiable for you. This will force trade-offs around cost. Personnel, security, and availability are costs that cloud providers bundle into their pricing. With on-premise, these are now costs (and risks) that belong to your books, along with audits, insurance, and equipment that compound on top of the ERP’s base price.This may be the preferred arrangement, but ensure it’s an intentional trade-off and not just ​“the way we’ve always done it”.

If possible, have your ERP completely configured for one core use-case as early as possible, so it can begin delivering value within 3 – 6 months. We worked with one company that couldn’t trace an inventory lot back to the truck that delivered it without hours of manual human labor. They decided this was the first problem their new ERP should solve. They got a painful problem solved and began to use the new system in production, long before the full system was finished. 

Erp implementation quote

Cutting the time-to-value down to 3 – 6 months isn’t always possible, but simply setting this goal can act as a strong focusing function that keeps both the implementation team and your own internal teams aligned and can prevent scope creep.

Questions to help consider trade-offs:

  • If you pushed this (feature, workflow, etc.) off for 6 months, what would the effect be?
  • What painful problem could your ERP solve for you right now, that your previous system didn’t do at all?
  • What assumptions does your timeline make about staff availability and data quality? 

4. Underestimating Data Migration

A sneaky failure point that must be accounted for early in planning an implementation is data migration. Data is the lifeblood of any company and data loss or corruption are real risks that must be properly considered in the implementation and migration plan. 

Ideally, we’d want a system that can run in parallel with the existing system while data correctness is verified by the people who use it day-to-day. 

A common failure point is assuming data will transfer cleanly between the old and new system without anyone familiar enough with it to flag a discrepancy. A software vendor can see that data was transferred to a new system, but they rarely have the knowledge of your specific business to identify corruption or smaller data losses. 

Identify who is capable of verifying your data integrity, and give them the resources they need to ensure data integrity across the migration.

Questions to help design a proper data migration:

  • Where do your current backups reside?
  • When was the last time you simulated a disaster recovery? (If the answer is ​“never,” you should strongly consider this before anything touches your data.)
  • Who will verify that the migrated data is correct, and how?
  • How clean is your current data?

5. Skimping on Training and Post-Launch Support

This next failure point happens toward the end of the implementation. If you’re lucky, you’ve been running your new ERP system in parallel with your old ERP system, while staff get the chance to ask questions and learn the new system from your ERP vendor. This usually reduces the need for lengthy training sessions or elaborate documentation. 

However, this isn’t always possible. In that case, be sure to allocate time for training, documentation and most importantly, unforeseen problems. There is no perfect system. It will take time to adapt to the new system; a vendor who disappears the moment the final feature is built is failing you right when your staff are trying to build trust in the new product. Be sure to have these conversations with your vendor as early as possible!

Good questions to ask your vendor toward the end of implementation include:

  • What does support look like post-implementation? (Note any additional fees for post-implementation support)
  • How quickly can you get support for questions or issues?
Erp implementation red flags
ERP Implementation Red Flags

The tips above are applicable to any vendor, any platform, and any software. The best vendors bring their expertise and software, but are flexible to accommodate the unique needs of your business. 

Not every implementation works the same, and you should advocate to have your ERP implementation fit the needs of your business. Using these tips will help you avoid the most common and painful failures.

Pricing Request Demo Request White Paper Request

Please complete the fields below to receive your confirmation email Please complete the fields below to receive your confirmation via email To download your white paper, complete fields below. Check your inbox for the white paper link..

Add Related Systems?

Based on your selection, we recommend adding these comparable systems to your evaluation request:

Congratulations, you're a step closer to finding the right ERP System.

A confirmation email from Top10ERP.org is on its way to your inbox. This email will include information on the resources you requested.

Thank you for visiting Top10erp.org. We greatly value hearing from our visitors. Please share your comments, questions and feedback regarding your experience on Top10ERP.org.