ERP Integration Mistakes to Avoid

The biggest businesses can get major programmes horribly wrong. Here are 4 famous examples, the fundamental reasons for failure and how that might have been avoided. Hershey: Sought to replace its legacy IT systems with a more powerful ERP system. However, due to a rushed timeline and inadequate testing, the implementation encountered severe issues. Orders worth over $100 million were not fulfilled. Quarterly revenues fell by 19% and the share price by 8% Key Failures: ❌ Rushed implementation without sufficient testing ❌ Lack of clear goals for the transition ❌ Inadequate attention and resource allocation Hewlett Packard: Wanted to consolidate its IT systems into one ERP. They planned to migrate to SAP, expecting any issues to be resolved within 3 weeks. However, due to the lack of configuration between the new ERP and the old systems, 20% of customer orders were not fulfilled. Insufficient investment in change management and the absence of manual workarounds added to the problems. This entire project cost HP an estimated $160 million in lost revenue and delayed orders. Key Failures: ❌ Failure to address potential migration complications. ❌ Lack of interim solutions and supply chain management strategies. ❌ Inadequate change management planning. Miller Coors: Spent almost $100 million on an ERP implementation to streamline procurement, accounting, and supply chain operations. There were significant delays, leading to the termination of the implementation partner and subsequent legal action. Mistakes included insufficient research on ERP options, choosing an inexperienced implementation partner, and the absence of capable in-house advisers overseeing the project. Key Failures: ❌ Inadequate research and evaluation of ERP options. ❌ Selection of an inexperienced implementation partner. ❌ Lack of in-house expertise and oversight. Revlon: Another ERP implementation disaster. Inadequate planning and testing disrupted production and caused delays in fulfilling customer orders across 22 countries. The consequences included a loss of over $64 million in unshipped orders, a 6.9% drop in share price, and investor lawsuits for financial damages. Key Failures: ❌ Insufficient planning and testing of the ERP system. ❌ Lack of robust backup solutions. ❌ Absence of a comprehensive change management strategy. Lessons to be learned: ✅ Thoroughly test and evaluate new software before deployment. ✅ Establish robust backup solutions to address unforeseen challenges. ✅ Design and implement a comprehensive change management strategy during the transition to new tools and solutions. ✅ Ensure sufficient in-house expertise is available; consider capacity of those people as well as their expertise ✅ Plan as much as is practical and sensible ✅ Don’t try to do too much too quickly with too few people ✅ Don’t expect ERP implementation to be straightforward; it rarely is

I’ve seen $10,00,000+ ERPs break down because one warehouse team used the word “Box”… while the other said “Carton.” That’s it. Master data is the real killer in most ERP projects. But nobody wants to talk about it because it’s not “attractive” It’s not the software. It’s what you feed into it. And here's the stuff actually wrecking your ERP: 1. 𝐔𝐧𝐢𝐭 𝐨𝐟 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 𝐫𝐨𝐮𝐥𝐞𝐭𝐭𝐞 – “PCS” vs “Pieces” vs “Nos.” – Finance gets confused. Inventory gets misaligned. 2. 𝐃𝐮𝐩𝐥𝐢𝐜𝐚𝐭𝐞 𝐯𝐞𝐧𝐝𝐨𝐫𝐬 𝐰𝐢𝐭𝐡 𝐚 𝐬𝐩𝐚𝐜𝐞 𝐚𝐭 𝐭𝐡𝐞 𝐞𝐧𝐝 – Vendor A – Vendor A␣ – Congrats, now you have two aging reports and no idea who’s overdue. 3. 𝐒𝐊𝐔 𝐧𝐚𝐦𝐢𝐧𝐠 𝐥𝐨𝐠𝐢𝐜 𝐭𝐡𝐚𝐭 𝐜𝐡𝐚𝐧𝐠𝐞𝐬 𝐛𝐲 𝐭𝐞𝐚𝐦 – Sales calls it “1L Oil Bottle” – Warehouse calls it “OIL1L” – Finance sees two lines and overpays freight. 4. 𝐆𝐋 𝐚𝐜𝐜𝐨𝐮𝐧𝐭𝐬 𝐬𝐞𝐭 𝐮𝐩 𝐛𝐲 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐩𝐞𝐨𝐩𝐥𝐞 – 4010-Admin vs 401A-AdminExp – Good luck finding out why your reports don’t reconcile. 5. 𝐂𝐨𝐮𝐧𝐭𝐫𝐲 𝐟𝐨𝐫𝐦𝐚𝐭𝐬 𝐭𝐡𝐚𝐭 𝐜𝐥𝐚𝐬𝐡 – “US” vs “USA” vs “United States” – Then one team can’t file GST because the country code doesn’t match the statutory system. You don’t need another ERP module. You need a data governance spine. If you're migrating, consolidating, or upgrading fix this first:  → Unified naming logic → Approved master data owners → Clean-up workflows → Real UOM and GL dictionaries → Vendor & SKU de-dupe policies Your ERP isn’t broken. Your data is wild. And if you don’t fix it, every report, every dashboard, and every decision will quietly rot from the inside. Seen something worse? Drop your horror story in the comments. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 𝐬𝐨 𝐨𝐭𝐡𝐞𝐫𝐬 𝐜𝐚𝐧 𝐥𝐞𝐚𝐫𝐧.

McKinsey's ERP warning for CFOs: 1. 70% of ERP transformations fail     Most ERP projects run over budget and underdeliver. Why? Because companies underestimate complexity. Finance expects a big bang switch. Instead, they get endless data cleanups, mismatched chart of accounts, and broken workflows. In finance, a 90% rollout isn’t a win. If one close process breaks, the whole system stalls.     2. It's your design, not your tech     CFOs blame vendors. But the real issue is design. Too many teams lift-and-shift old processes into new systems. That hardcodes inefficiency. The 30% who succeed don’t copy the past. They redesign approvals, reconciliations, and controls before go-live. ERP isn’t a tool migration. It’s an operating model redesign.     3. Finance feels the pain first     In sales, if CRM misses a field, people workaround. In finance, if ERP misses a journal entry, you misstate results. Month-end closes, audits, and compliance magnify every flaw. That’s why ERP failures show up in finance before anywhere else. Unless you engineer accuracy and reliability from day one, the CFO’s credibility is at risk.     4. The gap turns critical     McKinsey calls it out: 70% stuck, 30% pulling ahead. The stuck companies run digital systems that replicate legacy pain. The winners embed automation, shared data models, and continuous improvement. Over time, that gap compounds into faster closes, lower costs, and better decision-making.     TAKEAWAY ERP failures don’t just cost money at go-live. They lock in inefficiencies for years. Every close takes longer. Every audit is harder. Every board deck gets delayed. The reverse is also true. When ERP is designed right, benefits compound: - Faster closes free capacity - Automation creates leverage - Cleaner data sharpens insight The real gap isn’t visible at launch. It shows up quarter after quarter, year after year.

From day one in #b2becommerce, this has been one of the biggest traps I’ve seen. Distributors: please don’t get pulled down the primrose path just because a platform says it has an “out-of-the-box” integration with your ERP. The truth no one talks about? There's really no such thing as an 'out-of-the-box' integration. Everyone uses ERP and eCom differently. So, at the least, there will be configuration. But there are several platforms still running this gig - old tech, proprietary, no ecosystem. They tempt you with a seemingly low-risk way to launch quickly. The bigger issue: What will you be left with in the end? Let’s be honest: integration sucks. But it happens successfully every day. And many ERP platforms have connectors (or other tools) to simplify this process. So chances are, you’re not starting from scratch regardless of which direction you go. But here’s the catch: That “easy” integration comes with old technology, clunky experiences, and heavy customization. And by the time you realize how much you’ve spent just to get it halfway usable, the golden handcuffs are on. You could easily be stuck with a platform your customers hate with no clear path forward. Don’t do that to your eCommerce business - or, more importantly, your customers. They deserve a great customer experience- modern, API-first, composable platforms that let you build the experience they actually want. At the very least, do an honest, thorough evaluation against other B2B platforms, specific to your requirements. Because in the end, it’s not about what it costs. It’s about what you can make. #B2BEcommerce #B2BPlatforms #ERPIntegration #DigitalTransformation #CustomerExperience #MidMarketDistributors #ComposableCommerce #PlatformSelection

ERP won't streamline operations effortlessly. Without planning, it creates chaos instead. Most founders assume an ERP implementation will automatically fix revenue leakage and improve decision-making. The reality? Without proper planning, you get tangled data and frustrated teams. I've watched a founder plug in their ERP expecting magic. Instead: → Data became a mess → Employees grew frustrated → Decision-making got worse, not better The gap between expectation and execution comes down to three things: • No clear strategy before implementation • Lack of team buy-in from day one • Underestimating the complexity of system integration ERP systems are powerful tools for reducing revenue leakage and enabling better decisions - but only when you treat implementation as a strategic project, not a plug-and-play solution. The best founders don't assume technology will solve their problems. They build the strategy, align the team, and execute with precision. That's how you turn an ERP from a headache into a competitive advantage.

Here are few mistakes that you avoid as a Business Analyst while doing interface analysis. ✅ One of the most common mistakes is not fully understanding both the existing system and the system with which it will interface. This includes not only the technical aspects but also the business processes they support. ✅ Not involving all relevant stakeholders — including end-users, IT staff, and third-party vendors — can lead to missing critical requirements and expectations. It's essential to engage stakeholders early and often in the process. ✅ Inadequate documentation of the interface requirements can lead to misunderstandings and incorrect implementations. Detailed specifications, including data formats, protocols, and error handling procedures, are necessary. ✅ It's easy to focus on what the systems will do and overlook how they should perform. Non-functional requirements such as performance, security, and reliability are just as crucial as functional specs. ✅ Interfaces can fail, and without a robust plan for managing errors and exceptions, systems can suffer from increased downtime and data inconsistency. Planning how to handle these scenarios is essential. ✅ Interfaces might require changes to existing systems that can affect more than just the areas directly connected to the new interface. Failure to manage these changes carefully can disrupt business operations. ✅ Interface testing should cover all possible scenarios, including failure modes, to ensure the interface can handle real-world use and exceptions. Skimping on testing can lead to failures when the system goes live. ✅ As business needs evolve, interfaces may need to scale or be modified. Designing interfaces without considering future needs can lead to costly reworks. ✅ Integration projects can be complex and time-consuming. Underestimating the time, effort, and resources needed can lead to rushed deployments and quality issues. ✅ Every interface should have a clear business purpose and be aligned with the organization’s overall goals. Without this alignment, the interface may fail to deliver expected benefits. BA Helpline

I’ve led several implementations (HRIS, payroll, benefits etc), and if there’s one thing I’ve learned, it’s this: vendors sell you a vision, you’re the one who has to make it real. If you're about to roll out a new system, from my experience, these are 7 common (and costly) pitfalls to avoid, plus tips to get it right from the start: 1. Believing the demo = your reality. 🔍 Pitfall: Vendors will often show you a polished flow that glosses over limitations. ✅ Tip: Walk into demos with real use cases and ask: “Can you show me exactly how this works for our org structure/policy?” 2. Not reviewing legal + order forms closely (trust me, this one has saved me a lot of times). 🧾 Pitfall: Hidden fees, vague SLAs, and missing features are often buried in the fine print. ✅ Tip: Treat the MSA and order form like project-critical docs. Loop in legal or procurement. Ask, “What happens if…?” (delays, bugs, compliance issues, etc.) 3. Skipping internal alignment. 🤝 Pitfall: You pick a tool that IT, Finance, or Legal can’t support—or that doesn’t align with internal policy. ✅ Tip: Bring in key stakeholders early. Make sure the tool meets your data, security, and compliance needs. 4. Forgetting the less glamorous stuff. 🧠 Pitfall: The flashy dashboards are great, but no one talks about backend admin struggles. ✅ Tip: Request a full admin walkthrough. Understand what’s manual, what’s automated, and where support is needed, what features are in the pipeline, what will be implemented in the next couple of months if you choose to go with the vendor. 5. Assuming integrations will “just work”. 🧩 Pitfall: APIs might be outdated, undocumented, or simply incompatible. Seen this happen too many times. ✅ Tip: Ask for technical docs up front. Share with IT to confirm feasibility before signing anything. 6. No clear success metrics. 🎯 Pitfall: You launch… but can’t prove impact. ✅ Tip: Define KPIs for each stakeholder group before implementation. I want you to think: adoption, time savings, ticket volume, fewer errors, improved employee experience and many more. 7. Underinvesting in change management. 📣 Pitfall: You train the People Team, but forget everyone else. ✅ Tip: Build guides, host Q&A sessions, and roll out in phases. Treat this like a product launch, because it actually is. 🎁 Bonus Tip: Vendors will highlight what works. It’s your job to uncover what doesn’t. If you're gearing up to implement a new system and want to avoid these traps, feel free to DM me, I’m happy to share templates or rollout strategies. #PeopleOps #HRTech #SystemImplementation #HRIS #ProjectManagement #DigitalTransformation #ChangeManagement #LessonsLearned

A $200M mistake every ERP leader should avoid. Here’s what happened: In 2020, Metcash set out to replace 9 systems with a single Microsoft ERP for their grocery, liquor, and hardware divisions. Their goal? Standardization. Their mistake? Underestimating the change needed to get there. They tailored processes too early, before aligning teams on a unified approach. The result? → $200M over budget. → 2 years behind schedule. → Resistance at every level. ERP success isn’t about tailoring everything from the start. It’s mostly about driving change to achieve alignment first. And in this case, standardization isn’t optional. It’s essential. → Start with processes everyone can align on. → Tailor only where absolutely necessary: ↳ Legal requirements. ↳ Critical business cases bringing strategic advantages. Skip the alignment, and here’s what happens: - Teams resist the change. - Processes grow more complex. - Timelines and budgets spiral out of control. My advice? Think global: Standardize first to set the foundation. Act local: Tailor thoughtfully, only where it’s truly needed. Change doesn’t start with customization. It starts with alignment. ♻️ Repost if you found value. 👋 Follow Mariya Koteva for ERP change management insights.

SAP S/4HANA didn’t fail. The implementation did. A friend of mine, a CFO at an insurance company, called me yesterday. This wasn’t a casual check-in. It wasn’t a “congrats on go-live” call. And then he said the five words every team dreads. “We can’t close our books.” They’d just finished a year-long migration from Oracle ERP to SAP S/4HANA. Millions invested. Dozens of consultants. Everyone exhausted. Now? Month-end was broken. Finance was buried in manual fixes. Auditors were waiting. The board was anxious. It’s a train wreck I’ve seen before. When big projects go off the rails, everyone points fingers. Consultants say the business didn’t give clear requirements. The company says they expected more guidance, especially on SAP vs. Oracle. Consultants always say they’ve delivered “dozens of successful projects.” Just not this one. So, what actually goes wrong? ✖️ Finance comes in too late ✖️ Data gets moved but not harmonized or owned ✖️ Old processes get copied instead of redesigned ✖️ The project turns into a tech upgrade, not a real business change This isn’t about SAP. It’s about leadership, alignment, and strategy. You’ve heard the saying: “Culture eats strategy for breakfast.” In ERP? Leadership eats technology for dinner. S/4HANA can deliver huge value. But only when: ➡️ The business steps up from the start ➡️ Consultants work as true partners ➡️ The focus stays on real business needs What do successful teams do differently? ✅ Own the outcome from day one ✅ Question every assumption and old habit ✅ Measure success by lasting results, not just a “go-live” date ERP doesn’t fail in the code. It fails in the conversations that never happened. Go-live is just a milestone. Getting it right is the mandate. If you’re seeing warning signs or want to avoid them, let’s talk. I’ve helped teams turn these situations around. What’s the biggest ERP or tech challenge you’ve faced? Share your story below or DM me if you want to talk. --- 📌 Save to revisit later ♻️ Repost to help your network ➕ Follow Ganesh Ariyur for insights on enterprise transformation. #ITStrategy #CIO #EnterpriseTechnology #Transformation #SAP

The ERP implementation: $600K. The integrations to make it actually work: $780K. Yeah. You read that right. The "duct tape" cost more than the engine. Here is the anatomy of a $1.4M mistake. The client wanted a clean, modern cloud ERP. But they refused to let go of their legacy baggage The custom CRM (Sunk cost fallacy). The WMS (Change aversion). The Billing System ("Accounting likes it"). I asked the CFO: "Why not consolidate these into the ERP?" His answer: "We don't want to disrupt those areas right now." Famous last words. To avoid "disruption," we built a Frankenstein monster: CRM Sync ($180K): Because sales wouldn't switch. Warehouse Middleware ($220K): Because the WMS had no API. E-commerce Bridge ($150K): Custom mods on Shopify broke standard connectors. HR & Billing Feeds ($230K): Bridging ancient systems to modern tech. Total Integration Cost: $780K. The Aftermath (6 Months Later): Three integrations failed. Not because the code was bad, but because the ecosystem changed. Shopify updated → Integration broke. WMS vendor patched → Middleware crashed. CRM team added a field → Data sync failed. I told the CFO: "You paid more to keep your old systems than you would have to replace them." If we had consolidated everything into SAP: Total Cost: ~$900K. Single point of truth. Unified support. Instead, they paid $1.475M to maintain six points of failure. Every integration you build is technical debt. It will break. It will slow you down. It will cost 3x more than you budget. If you are implementing an ERP to simplify your business, don't complicate it with eight integrations. Consolidate first. Integrate only when you absolutely must. Before you sign that SOW, run the math Cost to Integrate + Maintenance vs. Cost to Replace. If integration costs more, kill the legacy system. Don't trap yourself in integration hell just to avoid an awkward conversation with the Sales VP.