ERP implementation failure does not always mean abandoning the software completely. A project can technically go live and still fail to deliver its intended business value because costs exceed the business case, processes become harder to operate, employees avoid the system, integrations break, data cannot be trusted, or expected efficiency gains never materialize.
That distinction matters because ERP underperformance is common. Gartner currently predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business-case goals, with as many as 25% failing catastrophically.
ERP failures can also have direct operational consequences. Hershey documented serious order-fulfilment and shipping difficulties after the 1999 rollout of a new enterprise-wide information system, while Agilent later estimated that disruption from its 2002 ERP launch negatively affected quarterly revenue by $85 million to $110 million.
The lesson is not that ERP itself is inherently risky. Implementation becomes risky when business requirements, system design, data, people, testing, governance and go-live decisions are not aligned.
This guide explains the most common causes of ERP implementation failure, examines real cases with documented evidence, and shows what businesses can do differently before, during and after go-live.
Enterprise Resource Planning (ERP) systems are integrated software solutions that help businesses manage various functions, such as finance, HR, supply chain, POS, and customer relationship management (CRM), in one unified system. When implemented correctly, ERP systems boost efficiency, enhance reporting, and enable better decision-making across all areas of your business.
For startups and SMEs in Saudi Arabia, investing in an ERP system like HAL ERP can truly transform your operations. With real-time data access, reduced manual work, and streamlined business processes, the right ERP system can automate repetitive tasks, improve cross-departmental communication, and significantly increase operational efficiency.
With a clear understanding of ERP’s potential benefits, it's important to address why many ERP implementations fail.
The ERP failures often stem from common causes like poor planning, unrealistic expectations, lack of funding, and insufficient training and support. High-profile ERP failures make headlines, leading to bad publicity, lawsuits, and major financial losses.
The good news is that not all ERP implementations have to fail. By understanding why past projects failed, you can avoid making the same mistakes and ensure your ERP project succeeds.
However, ERP implementation can be challenging. Let’s explore the common causes behind the unsuccessful implementation of ERP.
ERP failure exists on a spectrum.
A project can fail because it is:
This broader definition is important. Gartner’s current ERP forecast refers to projects failing to fully meet their original business-case goals, not simply projects that are switched off or abandoned. (Gartner ERP research)
ERP systems promise major improvements, but many businesses struggle during their implementation. This often results in what’s called an "unsuccessful ERP implementation." Let’s explore some of the most common causes and how you can avoid them.
A common cause of ERP failure is poor planning and unclear objectives. Without a defined strategy, companies often implement ERP systems that don’t align with their actual needs, leading to scope creep, cost overruns, and missed expectations.
How to Avoid It: Set clear, measurable goals before starting your ERP project. Ensure these goals align with your business strategy. Involve key stakeholders early to gather input and ensure the system fits the company’s needs and processes.
Many businesses underestimate the changes needed when implementing an ERP system. These go beyond installing new software—they involve process updates, staff retraining, and workflow adjustments. If not managed well, these changes can lead to resistance and disruptions.
How to Avoid It: Recognize the full scope of changes that come with ERP implementation. Develop a comprehensive change management plan, which includes training programs, clear communication, and strong employee support to ensure a smooth transition.
ERP systems often fail when users aren’t adequately trained. This leads to frustration, mistakes, and underuse of the system’s capabilities.
How to Avoid It: Invest in thorough training for all users before, during, and after the system is deployed. Ensure employees know how to use the system effectively. Provide ongoing support to help users fully integrate the system into their daily tasks.
Selecting the wrong ERP vendor or software can result in poor performance and inefficiencies. Some companies choose systems based on cost or reputation without ensuring the software matches their specific needs.
How to Avoid It: Evaluate the ERP against actual business processes rather than vendor reputation or feature count. Build a requirements list, use realistic demo scenarios, identify which requirements are standard versus customized, and verify integration, scalability, implementation support, and industry fit before committing. HAL’s ERP Vendor Selection Criteria provides a more detailed evaluation framework.
Learn more about the Essential Criteria for the ERP Vendor Selection Process.
Data migration is one of the most complex aspects of ERP implementation. Poor data quality or incomplete migrations can cause significant errors and disruptions.
How to Avoid It: Assign business owners to the migration process before data is uploaded. Identify what data will be migrated, clean duplicates and obsolete records, map legacy fields to the new ERP structure, run test migrations, and reconcile opening balances and master data after upload. Integration should also be tested end to end rather than assuming that a successful API connection means the underlying business process works.
A lack of strong leadership can derail an ERP project. Without full support from senior management, the project may not get the resources and attention it needs.
How to Avoid It: Engage senior leadership from the beginning. They should champion the project, allocate necessary resources, and communicate the ERP system’s benefits. Keep stakeholders updated and maintain momentum with active leadership.
Many ERP projects fail when companies do not allocate enough resources—in terms of time and personnel. Without dedicated resources, it’s difficult to manage the complexities of the implementation process, leading to delays and mistakes.
How to Avoid It: Allocate dedicated project teams and ensure adequate resources to support the implementation process. This ensures the system is fully supported from start to finish.
ERP systems require continuous support after implementation to run smoothly. Without ongoing technical support, businesses face disruptions and missed opportunities for optimization.
Solution: Plan for post-implementation support. Ensure your team has access to technical help whenever needed, and schedule regular evaluations to optimize the system’s performance.
Setting unrealistic timelines for ERP implementation is a common pitfall. Rushed projects lead to incomplete testing, lack of user training, and improper integration, which contribute to project failure.
How to Avoid It: Develop a realistic timeline that allows for proper planning, testing, and training. Allocate enough time for each stage of the process to ensure the implementation is done right, without cutting corners.
Skipping or rushing the testing phase is a critical mistake. Without thorough testing, businesses risk launching an ERP system with bugs and issues that disrupt daily operations.
How to Avoid It: Test complete business scenarios rather than isolated screens. Cover system testing, integrations, migrated data, user permissions, financial postings, reports, exception cases and user acceptance testing (UAT). Record defects, retest fixes and define clear acceptance criteria before go-live. HAL’s public Project Governance Document similarly separates system testing, UAT, training, data migration and go-live into distinct implementation stages.
Now that we’ve explored the causes behind ERP failures, let’s take a closer look at real-world examples to better understand the consequences.
Large ERP failures rarely have one cause. They usually involve several overlapping problems across process design, cutover, testing, data, customization and change management.
Here are four better-documented examples—and one important Saudi case that should not be mislabeled as a failure.
Hershey implemented the final phase of a new enterprise-wide information system in 1999.
The company later acknowledged in its own filings that it experienced serious difficulties during the second half of 1999, including shipping and customer-service problems. Hershey said those problems affected customer confidence and contributed to sales shortfalls. (Hershey 2000 Annual Report – SEC)
Hershey also noted that limited distribution capacity exacerbated the slow and problem-ridden system startup during peak shipping demand.
Lesson: A successful technical deployment is not enough. Cutover timing, logistics capacity, user readiness and the wider operating environment all need to support go-live.
Do not retain the current “$100 million in lost orders” or “8% stock-price decline” statements unless you introduce a separate source that specifically substantiates those figures.
Agilent provides a particularly useful example because the company quantified the effect of its ERP rollout in an official SEC filing.
In 2002, Agilent implemented a new ERP system covering more than half of its volume and virtually all financial processes.
The company said implementation disruption affected its ability to provide shipment dates, process orders and maintain normal production. It estimated the quarterly negative impact at approximately:
(Agilent Technologies 2002 Form 10-Q – SEC)
Agilent also noted that employees were spending time learning and implementing the new system instead of carrying out normal business activity.
Lesson: Go-live readiness needs to account for both system functionality and the temporary productivity loss created when employees are learning an entirely new operating environment.
National Grid’s US ERP program later became the subject of litigation between National Grid and systems integrator Wipro.
Wipro publicly confirmed that the lawsuit related to an ERP implementation project begun in 2009 and that National Grid was seeking $140 million plus additional costs. Wipro disputed the allegations. (Wipro disclosure filed with the SEC)
The court docket shows that the dispute was later settled and dismissed with prejudice in August 2018. (National Grid USA Service Company v. Wipro – court docket)
The case became associated with allegations involving requirements, customization, testing and data conversion. Because these were litigated claims, they should be described as allegations rather than established facts.
Lesson: ERP governance needs clear accountability for design decisions, testing, data conversion, project documentation and vendor responsibilities.
Remove the current statement that a $75 million settlement proved the full extent of National Grid’s losses unless you intentionally retain a separate secondary source for that figure.
German retailer Lidl began an SAP-based transformation of its merchandise-management environment in 2011.
After years of work, Lidl ultimately stopped the program and returned to further development of its existing system. Contemporary reporting estimated that approximately €500 million had been invested in the project. (Computer Weekly: Lidl dumps €500m SAP project)
The case highlights a recurring ERP problem: implementing a technically capable platform does not guarantee a good fit with the organization’s established operating model. Continuing customization can eventually make the economics of the implementation unattractive.
Lesson: Evaluate process fit and customization requirements before committing to a large rollout. If the standard ERP model conflicts fundamentally with core business processes, identify that gap during requirements and prototype testing—not years into implementation.
The existing article describes King Saud University’s MADAR ERP project as a failure. That is not an accurate representation of the academic source.
A published study of the MADAR implementation at King Saud University reported that the system was approximately 85% implemented at the time of study and covered functions including HR, finance, budgets, purchasing and warehouse control.
The researchers found challenges involving:
However, the study also states that no major problems were reported with the overall progress of the implementation and describes users as expecting conditions to improve.
Lesson: ERP implementations do not need to collapse completely to reveal useful risks. The MADAR case shows how training, communication, integration and legacy-data quality can affect user satisfaction even while a system continues to be implemented.
Before go-live, confirm that the project can answer the following questions.
For a phase-by-phase breakdown, link to HAL’s ERP Implementation Life Cycle guide. That page is currently live and should own the deeper implementation-stage explanation rather than duplicating it here.
Now that you know the strategies, ERP systems like HAL ERP are here to help you implement them effectively. Let’s see how.
No ERP vendor can guarantee that an implementation will succeed. Success depends on decisions and work shared between the implementation team and the customer.
HAL does, however, publish a defined implementation process in its Project Governance Document.
After requirements gathering, HAL’s documented build process covers:
HAL distinguishes standard functionality from customization and states that new requirements outside the approved proposal or requirements document are handled as change requests.
This helps control one of the common causes of ERP failure: uncontrolled scope expansion during implementation.
HAL’s governance document makes the migration responsibilities explicit.
The customer is responsible for:
HAL is responsible for providing the migration templates and uploading agreed data using its standard migration tools.
This is an important distinction because an ERP vendor cannot correct unknown errors in a customer’s source data automatically.
HAL documents a train-the-trainer approach, where identified key users participate in the implementation and receive hands-on training.
The project process also includes system testing and formal user-acceptance testing before go-live.
HAL’s published process moves to production after training, UAT and data migration have been completed.
Its governance document currently specifies a 14-day hypercare period after go-live, after which the project moves into the standard support process.
Businesses that need to retain existing applications can also evaluate HAL’s current integration ecosystem, which documents connections across banking, ecommerce, POS, payments and other business systems.
These processes can reduce implementation risk, but the customer still needs to provide accurate requirements, clean data, available key users, timely decisions and meaningful UAT.
Successful ERP implementation demands careful planning, strong leadership, and thorough testing. By learning from the mistakes of high-profile failures like Hershey, National Grid, and Lidl, you can sidestep common pitfalls and set your business up for success.
By addressing the reasons behind the unsuccessful implementation of ERP, you can ensure your project stays on track and delivers the results you need. With the right approach, your ERP system can become a powerful tool for driving efficiency and growth.
Ready to see how HAL ERP can help streamline your operations and avoid common pitfalls? Schedule your personalized demo today, and let's discuss how HAL ERP can be tailored to your unique business needs.
ERP implementations commonly struggle when the software and business requirements are poorly aligned, executives are not sufficiently involved, scope expands without control, data quality is weak, users are not prepared, or testing does not reflect real operating scenarios.
Gartner’s current ERP guidance specifically identifies executive commitment, organizational change, end-user adoption, business alignment, project execution, data integrity and integration as major implementation risks.
The answer depends on how “failure” is defined.
Gartner currently predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business-case goals, with as many as 25% failing catastrophically. That should not be interpreted as meaning 70% of ERP projects are completely abandoned.
Yes. Incorrect, duplicated, incomplete or poorly mapped legacy data can affect reporting and operational processes after migration.
HAL’s own Project Governance Document therefore assigns explicit responsibility for extracting, cleansing, mapping and validating migration data before and after upload.
UAT allows actual business users to confirm that the ERP supports required workflows before production launch.
It can identify problems involving configuration, permissions, migrated data, integrations, calculations and reports that isolated technical tests may miss.
Hershey did experience serious implementation difficulties in 1999.
Its own annual report documents shipping problems, customer-service issues and sales shortfalls following the startup of its enterprise-wide information system. The system was subsequently stabilized and Hershey later reported that it was performing effectively. (Hershey filing – SEC)
No.
Product fit matters, but implementation also depends on requirements, governance, process design, data migration, integrations, user participation, training, testing, cutover and post-go-live support.
