ERP Implementation: The Missing Ingredient in Success
pjoeckel • March 5, 2024
ERP Implementation: The Missing Ingredient in Success
I recently found myself engrossed in yet another white paper, this one promising to reveal the secrets of successful ERP software implementation. As I delved into the document penned by respected ERP experts, I asked: Did I gain any new insights? Did I find any valuable takeaways? The answer, unfortunately, was a resounding no.
Like countless others I’ve read, this white paper echoed the same advice circulating in the ERP community for years. It was reminiscent of the numerous “Top XYZ” lists that claim to hold the keys to ERP project success. Yet, ERP implementations fail alarmingly despite the abundance of advice available with a simple Google search.
So, what constitutes an ERP project failure? If a project fails to meet three fundamental criteria for success, it should be classified as a challenged or failed project. These criteria are:
With so much expert advice readily available, why do ERP implementations continue to stumble? In my experience, the advice offered is often academic, rehashing the same guidance that has previously led to significant cost and time overruns and failure to deliver the promised functionality.
When I peruse this advice, I find nothing innovative or practical. Generic, oft-repeated academic guidance is abundant, but there is a shortage of helpful tips you can immediately apply to your project to make a meaningful impact.
Even more frustrating is when this unhelpful advice is hidden behind paywalls, requiring you to shell out hundreds or thousands of dollars. And let’s not forget the consulting and implementation firms that charge exorbitant fees only to lead projects to repetitive failures.
Interestingly, I'm met with enthusiastic agreement whenever I highlight these issues in speaking sessions or during consultations with individual teams. It seems everyone has firsthand or secondhand knowledge of how these projects fail. Yet, no one seems willing to challenge the status quo as the same flawed processes are used repeatedly.
In conclusion, the ERP implementation landscape is in dire need of a shake-up. We must move away from regurgitated academic advice and towards practical, actionable strategies that can drive project success. Only then can we hope to improve the success rate of ERP implementations.
Like countless others I’ve read, this white paper echoed the same advice circulating in the ERP community for years. It was reminiscent of the numerous “Top XYZ” lists that claim to hold the keys to ERP project success. Yet, ERP implementations fail alarmingly despite the abundance of advice available with a simple Google search.
So, what constitutes an ERP project failure? If a project fails to meet three fundamental criteria for success, it should be classified as a challenged or failed project. These criteria are:
- On-time delivery
- On-budget delivery
- On-spec delivery
With so much expert advice readily available, why do ERP implementations continue to stumble? In my experience, the advice offered is often academic, rehashing the same guidance that has previously led to significant cost and time overruns and failure to deliver the promised functionality.
When I peruse this advice, I find nothing innovative or practical. Generic, oft-repeated academic guidance is abundant, but there is a shortage of helpful tips you can immediately apply to your project to make a meaningful impact.
Even more frustrating is when this unhelpful advice is hidden behind paywalls, requiring you to shell out hundreds or thousands of dollars. And let’s not forget the consulting and implementation firms that charge exorbitant fees only to lead projects to repetitive failures.
Interestingly, I'm met with enthusiastic agreement whenever I highlight these issues in speaking sessions or during consultations with individual teams. It seems everyone has firsthand or secondhand knowledge of how these projects fail. Yet, no one seems willing to challenge the status quo as the same flawed processes are used repeatedly.
In conclusion, the ERP implementation landscape is in dire need of a shake-up. We must move away from regurgitated academic advice and towards practical, actionable strategies that can drive project success. Only then can we hope to improve the success rate of ERP implementations.
Avoid ERP project failure! With a GYDE365-Discover assessment, you'll r eceive an in-depth analysis report pack that includes:
- Recommended modules based on your company's processes
- Defined list and analysis of your company's requirements
- Gap/fit analysis to Dynamics Business Central and FSCM (easily benchmark to non-Microsoft ERP solutions if desired)
- Implementation project estimates, including timeline, budget, and licensing costs
- RFP/RFI-ready documents
- ...and much more!
HandsFree ERP is dedicated to supporting clients with their ERP initiatives, enabling companies to seamlessly connect users with their ERP partners. By utilizing skilled professionals, streamlined processes, and cutting-edge tools, HandsFree ERP significantly boosts the success rates of ERP projects.

By Peter Joeckel
•
September 11, 2025
Most organizations think data migration is about moving records from A to B. They're wrong. It's about transforming business information into operational truth. Get it wrong, and you're just digitizing your problems at enterprise scale. If you’re a distributor or manufacturer, your business runs on inventory. Simple as that. Everything else, sales, purchasing, operations, revolves around making sure your inventory data is accurate. And yet, so many companies struggle with messy, outdated, or outright incorrect data, setting themselves up for major headaches when it comes time to implement or upgrade an ERP system. For manufacturers and distributors, inventory is the heart of the business. Everything revolves around managing it effectively. In ERP terms, this involves three core processes: 1. Procure-to-Pay – Bringing inventory in from suppliers. 2. Manufacturing or Handling – Transforming or repackaging inventory. 3. Order-to-Cash – Shipping inventory out to customers. At the heart of the problem are three core data sets: customers, suppliers, and inventory . Clean and accurate data here isn’t optional. It’s essential. Let me paint you a picture of what poor data quality really costs: - Financial processes failing because customer master data is inconsistent - Supply chain grinding to a halt because item masters don't match across systems - Month-end closing taking weeks because nobody trusts the numbers - Compliance risks because audit trails are incomplete or incorrect I've seen implementations declare success after migrating millions of records, only to discover they've built a perfect system running on garbage data. The result? Unreliable reporting, broken processes, and users creating shadow systems to track "real" data. Here's what your implementation partner isn't telling you: Data quality issues compound over time. Every day you operate with poor data, you're creating new problems that will need to be fixed later. It's like trying to build a skyscraper on quicksand - no matter how perfect your architecture, IT IS GOING TO SINK. The hard truth: No amount of system optimization can fix bad data. You're either managing data quality now, or you're managing data problems forever. And in D365 F&O, forever gets expensive very quickly. Bills of Materials: The Science That Trips Everyone Up For manufacturers, one of the biggest trouble spots is the Bill of Materials (BOM) . Think of the BOM as a recipe: it defines exactly how components come together to make a finished product, like a “little red wagon.” Each part must be accounted for, structured correctly, and contain only inventory items. Here’s where things go wrong: Many BOMs have too many levels or include non-inventory items like labor and overhead. Legacy systems often force companies to create Frankenstein part numbers that are confusing and error-prone. Process manufacturers with “recipes” face additional complexity because ingredient quality can fluctuate, affecting output consistency. Moving this messy data into a modern ERP without cleaning it first can turn your new system into a nightmare rather than an improvement. Routing: Where Art Meets Science Beyond the BOM, there’s routing , the step-by-step instructions for manufacturing a product. Routing data is critical for understanding capacity, scheduling, and cost management. Capturing work center setup times, labor, material, and overhead costs is key. Most companies simply don’t have this data organized, which means ERP projects often start off on the wrong foot. Planning Ahead: The Key to ERP Success Waiting until the ERP project is live to clean and organize your data is a recipe for disaster. By then, your best engineers and data experts are fully occupied, leaving little time to fix deep-rooted issues. Forward-thinking manufacturers and distributors start data workshops well before the ERP implementation . These workshops: Identify issues in customer, supplier, and inventory data Clean and structure BOMs and routings properly Establish proper part numbering and chart of accounts setups Doing this ahead of time dramatically increases the chances of a smooth, successful ERP deployment—regardless of which system you choose. Bottom line: messy data doesn’t just slow you down, it can completely derail your ERP implementation. Start early, clean it up, and structure it correctly. Your future self (and your new ERP system) will thank you.