SAP in Your Company: Risks to Avoid

Rolling out an ERP like SAP is one of the most complex and strategic decisions a company can make. Done right, it can transform processes, boost efficiency, and drive growth. But if it’s not managed properly, it can lead to financial losses, operational disruptions, and serious reputational damage.

Below, we’ll go over real-world cases of companies that ran into trouble with their SAP projects, the lessons learned, and a checklist of common mistakes you’ll want to avoid.

Real Cases: When SAP Faced Major Challenges

LeasePlan, one of the top vehicle leasing companies in Europe, kicked off an ambitious project to unify 35 local systems into SAP S/4HANA. The global plan became overly complex and rigid. After sinking millions into it, LeasePlan pulled the plug. While there’s no detailed public confirmation of which systems it ultimately adopted, reports suggest it moved away from a monolithic approach and leaned toward a more hybrid architecture.

Lidl, the German supermarket chain, began its transition to SAP for Retail back in 2011. The project hit roadblocks including conflicts between its internal processes and SAP’s standard model, heavy customization, and lack of cultural fit. In 2018, Lidl shut down the implementation and stuck with its old system. The experience reinforced its focus on tech solutions that are closely aligned with its day-to-day operations.

Revlon, during its migration to SAP S/4HANA, ran into supply chain disruptions, billing and financial reporting issues, and sales drops that even led to lawsuits. While there’s no official word confirming whether Revlon still runs SAP today, some reports suggest it restructured its rollout strategy with stronger emphasis on testing, technical support, and risk management.

Waste Management, the leading waste management company in the U.S., sued SAP in 2008 over a failed implementation. It claimed the system didn’t meet the promised operational requirements. The dispute ended in a settlement, and Waste Management went looking for a solution better suited to its operations. Although the vendor it chose later was never disclosed, the case became a reference point for drafting clearer ERP implementation contracts.

Hershey’s also ran into major headaches when implementing SAP. If you want to dive deeper into that case, check out our full article on ZTalent: The Hershey SAP Case: A Lesson in What Not to Do

Checklist: Common Mistakes in SAP Implementations

• Not defining scope or aligning project goals with overall business strategy.
• Underestimating resistance to change within the organization.
• Over-customizing SAP to fit outdated processes instead of redesigning them.
• Going live without enough testing—especially integration, performance, and user acceptance tests.
• Failing to properly train employees, leaving end users unprepared to adapt.
• Lack of clear leadership and governance from top management.
• Choosing a “big bang” rollout without a solid risk mitigation plan.
• Poor handling of master data and system integrations.

SAP is a powerful tool, but its success depends less on the software itself and more on strategy, planning, and change management. These cases show that even big-name companies can stumble if objectives, processes, and teams aren’t fully aligned. Learning from their experiences is key to anticipating issues, preventing mistakes, and building a strong project from day one.