Ask any operations leader at a mid-market manufacturer what keeps them up at night, and the answer is rarely the one you'd expect. It's not competition. It's not margins. It's reporting. Specifically, it's the hours spent every week extracting data from systems that don't talk to each other, reconciling figures that should match but don't, and trying to make strategic decisions from a picture that's always incomplete.
This is the ERP silo problem. And it's far more common than most organisations admit.
How SMBs End Up With Multiple ERPs
No manufacturer sets out to run three ERP systems. It happens gradually — through acquisition, through organic growth into new product lines, through legacy systems that are too embedded to replace and too critical to switch off. Each system made sense in context. Together, they create a data architecture that nobody designed and nobody wants.
The consequences are predictable. Each system holds a partial view of the business. Consolidating them requires manual exports, spreadsheet manipulation, and a team of people whose primary job — unofficially — is data reconciliation. Monthly reporting takes weeks. Questions that should take minutes to answer take days. And leadership makes decisions based on data that was already out of date when it was compiled.
Case Study: A Manufacturing Firm Gets Its First Unified View
A manufacturing SMB came to us with a problem they'd been living with for years: three separate ERP systems, each running a different part of the business, and no reliable way to see the whole picture at once. Reporting was manual, slow, and constantly producing slightly different numbers depending on which system you started from. Consolidated reports required a small army of spreadsheets and took the better part of a week to produce.
Leadership had tried to solve this before — a data warehouse project that ran for 18 months before being quietly shelved, an integration middleware tool that added complexity without solving the core problem. The technology kept failing because the strategy wasn't right.
The approach that worked:
Rather than attempting to consolidate or replace the three ERPs — a project that would have cost millions and taken years — the strategy was to layer a unified analytics platform across all three. Microsoft Fabric was deployed to ingest data from each system, harmonise it into a single data model, and surface it through operational dashboards that updated in real time.
The impact was immediate. Within weeks of deployment, leadership had dashboards showing live data from all three ERPs in a single view — inventory levels, production throughput, order status, and financial performance, all reconciled and current. The weekly reporting process that had consumed days of staff time was replaced by a dashboard refresh.
For the first time, they had full visibility into their operations. And in that visibility, they discovered insights they never knew existed — production bottlenecks they'd normalised, margin leakage they hadn't been able to identify, and inventory patterns that were tying up cash unnecessarily.
What They Found When They Could Finally See
This is the part of the story that matters most. When organisations gain visibility for the first time, they rarely find what they expected. The problems they were aware of — the ones they'd been trying to manage — turn out to be symptoms. The real issues are the ones hidden in the data they couldn't see.
A production line running at 67% capacity that had been assumed to be at 80% — a normalised inefficiency nobody had questioned because nobody had accurate data
A product category with strong revenue but negative contribution margin once all costs were properly allocated across systems
Inventory holdings that were significantly higher than required, driven by ordering patterns in one ERP that didn't account for stock held in another
A supplier whose delivery performance looked acceptable in isolation but was causing cascading delays when viewed against the full production schedule
None of these were new problems. They had all been there for years. What was new was the ability to see them clearly enough to act on them.
The Strategic Lesson
The instinct when facing a multiple-ERP problem is to reach for consolidation — to pick one system and migrate everything into it. This is sometimes the right answer. More often, especially for SMBs with limited IT capacity and high operational risk, it is not.
A unified analytics layer — connecting existing systems into a single data model without replacing them — is faster to deploy, lower risk, and frequently delivers more immediate value than a multi-year ERP consolidation programme. The key is getting the data strategy right first: which data sources matter most, how they need to be harmonised, and what decisions the organisation needs to be able to make from the unified view.
Technology is the easy part. The hard part — and the part that determines whether the investment delivers lasting value — is the strategic clarity that comes before it.