Challenges in Specialized ERP Solution Integration

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

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, not the business transformation it truly is. Listening to my network, there seems to be a rush to complete ERP migrations, as fast as possible, with SAP S/4HANA plans driving most of it. But an ERP system is more than just an IT upgrade. It’s a chance to redesign how your business operates and build a solution architecture that supports agility and innovation. While necessary, these migrations often become redundant without proper alignment to business goals. Something, I've seen happen! Here some get rights to consider: ◉ 𝗔𝗹𝗶𝗴𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗲𝗰𝗵 𝗴𝗼𝗮𝗹𝘀 Ensure that IT and business leaders are on the same page. ERP systems serve broader business objectives, such as innovation, improving procurement strategies, and enhancing supplier relationships. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗼𝗼𝗹𝘀. Instead of getting caught up in the technology itself, be clear about the business benefits you'd like to achieve. New ERP functionality can be of support to achieve goals like efficiency, cost reduction, and agility. ◉ 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗮𝗻𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 Don't just migrate complex, outdated processes but streamline them end-to-end. Reevaluate processes for efficiency and desired outcomes. ◉ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻 𝘁𝗿𝗮𝗶𝗻𝗶𝗻𝗴 ERP migrations often fail due to poor user adoption. Beyond training, invest in communication & ongoing support showing the value and relevance of the system to users. ◉ 𝗜𝗻𝘃𝗼𝗹𝘃𝗲 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗲𝗮𝗺𝘀 ERP impacts every area of the business, so cross-team collaboration is essential. Involve stakeholders from finance, procurement, IT, and operations ensures the system meets everyone’s needs. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 - 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗼𝗺𝗽𝗿𝗼𝗺𝗶𝘀𝗲 An ERP system is only as good as the data it processes. Ensure that data is clean, consistent, and reliable before migration. Dirty or incomplete data is one of the biggest challenges post-go-live. ◉ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘀𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 Choose an architecture which allows for future-proofing and integration of new features, scalability and integration. Business models evolve, and your ERP must evolve with them." ◉ 𝗦𝗲𝘁 𝗿𝗲𝗮𝗹𝗶𝘀𝘁𝗶𝗰 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 - 𝗶𝘁'𝘀 𝗻𝗼𝘁 𝗴𝗼𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗾𝘂𝗶𝗰𝗸 𝗶𝗳 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝘃𝗲 Don’t rush an implementation. ERP migrations are complex and require time to integrate properly. A phased approach allows for troubleshooting and mitigates a risk for failure. ❓Any other "get rights" i missed and you would add from your experience. #erp #businesstransformation #migration #sap4hana

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.

"ERP Implementation Challenges & Best Practices" The other day, I was catching up with some former colleagues about how quickly technology is changing, which led us to discuss the many ERP implementations we’ve led over the years. Each one presented unique challenges, and with technology constantly advancing, ERP projects have become even more complex. They require us to wear multiple hats, such as super user, project manager, and the bridge between the company and the ERP provider, while also ensuring business continuity and managing our day-to-day responsibilities. In one major integration, I managed a small core team that fully immersed itself in every aspect of the new system. We took a "train-the-trainer" approach: the ERP provider trained us, and we, in turn, trained the entire staff. This hands-on method ensured a smoother transition and faster adoption across the organization. One of the biggest challenges was data integrity. Aligning teams across the company was important, but ensuring clean, standardized data before integration was even more critical. I saw this as an opportunity to clean up historical data, standardize formats, and eliminate redundancies. As a team, we conducted a pre-migration audit to identify potential issues—such as special characters failing to transfer correctly; and collaborated with departments to ensure consistency and accuracy. By addressing these issues upfront, we minimized downtime and enabled teams to fully leverage the new system’s capabilities from day one. A key takeaway for me was that ERP implementation isn’t just about technology, it’s about people, processes, and data. What ERP challenges have you faced, and how did you overcome them? Let’s discuss. 

ERP transformations rarely fail because of the technology. They fail because the architecture didn’t match the business—and the warning signs usually show up long before go-live, hidden in decisions most teams assume are harmless. After more than 40 NetSuite transformations across high-growth, multi-entity environments, I’ve seen one pattern repeat over and over: companies underestimate the complexity of connecting finance, operations, data, and technology into a single scalable system. Here’s what typically causes trouble: 1️⃣ No true business architecture Teams jump into configuration without mapping future-state process flows, data models, or integration points. NetSuite becomes a patchwork of quick wins instead of a unified engine. 2️⃣ Finance and operations aren’t aligned This is the most common failure point. If R2R, O2C, P2P, and manufacturing flows aren’t designed together, the system becomes filled with workarounds, manual tasks, and conflicting rules. 3️⃣ Over-customization replaces good design SuiteScript is powerful… but it shouldn’t be used to fix gaps that architecture should have solved. Custom code should be strategic, not a crutch. 4️⃣ Integrations aren’t treated as part of the ERP Your WMS, CPQ, eCommerce platform, and billing systems are your ERP. If integrations aren’t stable, the business isn’t stable. 5️⃣ Lack of governance and data discipline No ERP can compensate for inconsistent processes, naming conventions, or data rules. But the companies that get it right follow a clear pattern: ✅ Start with a real blueprint Process maps, decision matrices, BRDs, future-state flows. ✅ Design with scale in mind Not what the business looks like today — but 2–3 acquisitions from now. ✅ Architect the ecosystem, not just Oracle NetSuite WMS, CPQ, CRM, eCommerce, tax engines, AI, data warehouse. ✅ Build using a hybrid skillset CFO logic + developer precision + operations understanding. (When those three perspectives aren’t in the same room, things break.) ✅ Hold a high bar for data quality Data is the real ERP. ERP success is never an accident. It’s the result of disciplined architecture, cross-functional clarity, and a mindset of “build it right the first time.” If you’re planning a NetSuite transformation in 2026, we are always happy to share lessons learned from the front lines. Unlock IQ (UIQ) | Trusted Oracle NetSuite Advisors #ERPTransformation #NetSuite #ERPImplementation #FinanceOps #BusinessTransformation #DigitalTransformation #Oracle #NetSuiteJobs #UnlockIQ #ProcessOptimization

Day 19 – The silent killer of most Oracle Cloud ERP integrations isn’t the API, the event, or OIC. It’s the assumptions different teams carry into the design. I’ve watched perfectly good integrations fail because the functional team, technical team, and business team were all solving different versions of the same problem. Here are the three assumptions that break projects more than anything else: 1️⃣ “Fusion will behave like our old system.” It won’t. Fusion has strict rules, strict validations, and strict ownership models. Integrations break the moment people expect legacy flexibility. 2️⃣ “Downstream systems will adapt later.” They rarely do. If the downstream isn’t ready on day one — SLAs, error handling, idempotency — the integration becomes unstable from the start. 3️⃣ “Edge cases can be handled after go-live.” No they can’t. Production volume exposes every hidden exception instantly. Rework in production is 10x more expensive than aligning assumptions in design. The toughest integrations I’ve rescued had nothing wrong technically — the teams just never aligned on the same mental model of the process. My rule: If the assumptions aren’t aligned, the integration will fail — no matter how good the tool or API is. How do you align assumptions in your projects? Would love to hear real-world tactics. — Aman Khurana Senior Solution Architect – Oracle Cloud ERP & Integration #OracleCloudERP #OIC #ERPProjects #IntegrationArchitecture #SolutionArchitecture #DigitalTransformation

After 25 years building enterprise systems, the greystar project revealed why even billion-dollar portfolios struggle with disconnected infrastructure. This integration challenge explains what separates growing portfolios from systematically scaling operations. The challenge: → Global developer managing $20b portfolio. → Disconnected systems across regions. → Manual processes throughout operations. → Financials spread across procore, yardi, and oracle with no integration. → Field teams operating blind without real-time data. The systematic approach we implemented: → Unified financials and performance data across all regions. → Built custom end-to-end development platform connecting every phase. → Launched real-time mobile app for field teams. → Integrated financials across procore, yardi, and oracle systems. The outcome that strengthened their market leadership: → Standardized data across all phases and regions. → Lower development costs with faster, agile teams. → First mobile app for remote developers in the industry. → Unified operations managing 2,600 assets globally. From $20b portfolio struggling with disconnected systems to the world's largest multi-family developer with unified infrastructure. >> If your portfolio is scaling but your systems create silos instead of integration, dm "systems" and i will show you the architecture that unified operations across a $20b global portfolio.

The Real Reason ERP Integrations Go Sideways ERP integrations don’t usually fail because of bad technology. They fail because of bad ownership. What we see most often: 1️⃣ No clear data owner When something breaks, no one knows who’s responsible for fixing it. 2️⃣ One-off logic gets hardcoded Short-term fixes quietly become permanent dependencies. 3️⃣ Exceptions turn into “requirements” Integrations start supporting edge cases instead of standard processes. 4️⃣ Nobody documents decisions Months later, teams are afraid to touch what no one understands. This is how integrations become fragile, expensive, and risky to upgrade. At Scaled Solutions Group, we design ERP integrations with governance, clarity, and upgradeability in mind — whether it’s workflows, external systems, or reporting extensions tied to platforms like Epicor Prophet 21. ERP should connect systems. Not multiply problems. 👉 What’s the messiest integration in your environment right now? Have you "SCALED"? https://lnkd.in/g3peD894 #ERP #Integrations #ERPImplementation #WorkflowAutomation #DigitalTransformation #Operations #Epicor #Prophet21 #ScaledSolutionsGroup

I've seen too many integration projects go sideways because teams skipped the most important step: opening properly. When a stakeholder says "we need to integrate ERP with MES," your first move shouldn't be scheduling a requirements workshop. It should be applying ISA-95 as an analysis framework. Four questions: 1. System levels? (L4→L3, L3→L3) 2. Domain? (production, maintenance, quality, inventory) 3. Information exchange type? (definition, capability, schedule/request, performance/response) 4. Repeatable patterns? (Work Masters vs Operations Definitions) The Amárach StackWorks article uses a production order integration to show how this works. Takes 30 minutes. Prevents months of scope creep. You know what systems are in scope, what domain you're working in, what ISA-95 models you need, and how the work decomposes—before you've written requirements or facilitated a single Event Storming session. That's opening properly. It changes everything.