8 Common Problems With Legacy Business Systems (And How to Fix Them)

The software that runs your business — your ERP, your business system, your system of record — is probably the most important technology investment you have ever made. It holds your financial data, your inventory, your customer records, your supply chain. It is the operational backbone of your organisation.

It is also the software your team hates using the most.

This is a strange tension that plays out in thousands of mid-market manufacturers, distributors, and wholesalers across the UK. The core business system is simultaneously indispensable and infuriating. It is the source of truth and the source of friction. How did we get here?

The answer is not that you chose the wrong system. Nor is it that your team is resistant to technology. The answer is that most enterprise software was designed in a different era — an era of data entry, not task completion. An era of rigid role centres, not flexible workflows. An era when "mobile strategy" meant a laptop you could carry to a meeting.

In this guide, we walk through the eight most common problems that legacy business systems create for UK manufacturers and distributors — and, more importantly, what you can do about each one. The fixes do not require a full ERP replacement. They do not require a six-figure budget or an eighteen-month implementation. They are practical, achievable, and proven.

Problem 1: Terrible User Experience

This is the problem that sits at the root of almost everything else. Your business software was built for functionality, not usability. It was designed by developers for data entry clerks, not by UX researchers for the modern knowledge worker.

Walk through your warehouse or your sales office and watch someone use your ERP. Watch them navigate a role centre crammed with tiles, lists, and fact boxes that compete for attention. Watch them click through six to twelve screens to reach a function they use ten times a day. Watch them search for a field that is logically placed somewhere no user would ever think to look.

This is not a training problem. It is an interface problem. A 2020 study published in MDPI Applied Sciences identified 27 distinct usability issues in enterprise resource planning systems, including excessive navigation depth, poor error feedback, and interface complexity that overwhelms the user. The research is clear: ERP user interfaces consistently underperform against modern usability standards.

The fix: Build a role-specific interface layer.

Instead of asking every user to wrestle with the same generic interface, build purpose-built screens for each role in your organisation. A warehouse operator sees a pick list and a barcode scanner — nothing else. A salesperson sees customer orders and stock availability — not the chart of accounts. A production manager sees job status and material requirements — not the general ledger.

This is not a customisation of your ERP. It is a separate interface layer that connects to the existing business system via its API. Your underlying system of record stays exactly as it is. The interface is rebuilt from scratch, for each role, with modern UX principles.

Problem 2: Spreadsheet Workarounds

Export to Excel. It sounds innocent enough. Someone needs a report, or a quick view of data, or a way to combine information from two screens. They click the export button, open the spreadsheet, and carry on with their day.

But this innocent act is costing your business real money. Every time a member of staff exports data from your operational platform into Excel, they create a shadow copy of your business information. That copy is stale the moment it is created. It sits on a local machine, outside your security controls. It gets emailed around the organisation as an attachment. Someone edits it, saves it, and now you have multiple versions of the truth.

The real problem is that your staff are not exporting data because they enjoy spreadsheets. They are exporting because the business software is too slow, too complex, or too rigid for the task they need to complete. Excel is not the workaround — Excel is the symptom. Your legacy system is the cause.

Multiple studies have quantified the cost of this. One report from Salesforce found that sales teams spend an average of four hours per week on data entry and administrative tasks inside their core business systems — time that could be spent selling. In manufacturing environments, the cost of spreadsheet-based inventory management alone has been estimated at 1–3% of stock value in write-offs, write-downs, and expedited shipping caused by data errors.

The fix: Purpose-built screens that surface only the data each role needs.

When a warehouse operator opens a purpose-built picking screen that shows exactly the current pick list — no navigation, no extra tiles, no fact boxes — they have no reason to open Excel. When a salesperson can see live stock availability, customer pricing, and order history on a single screen, they have no reason to export data into a spreadsheet. The workaround disappears when the interface is no longer the obstacle.

Problem 3: No Mobile Access

Your desktop ERP was built for, well, a desktop. It assumes a large screen, a keyboard, a mouse, and a stable desk. But a significant portion of your workforce does not work at a desk.

Warehouse staff need to check stock levels and bin locations while walking the aisles. Delivery drivers need to confirm shipments and capture signatures from the cab of a truck. Field service engineers need to view job details and update work orders from a customer site. Senior managers want to check revenue and order pipeline from their phone on the train home.

Some ERP vendors offer mobile apps, but these are typically the desktop interface squeezed onto a phone screen — smaller versions of the same clunky experience. Microsoft Business Central’s mobile app, for example, shrinks the web client rather than rethinking the workflow for a handheld device. It works, technically. It is not pleasant to use.

The fix: A purpose-built mobile application connected via API.

Rather than trying to make your desktop ERP work on a phone, build a dedicated mobile experience. A warehouse app that shows pick lists in a single tap. A driver app that guides delivery confirmation in three steps. An executive dashboard that shows the KPIs that matter, optimised for a phone screen. All connected to your existing business system via its REST API. Same data. Same system of record. Radically different experience.

Problem 4: Customers Phone for Data

One of the most persistent problems we hear from manufacturers and distributors is the volume of phone calls from customers asking basic questions: "What is the status of my order?" "When will stock arrive?" "Can you send me the invoice for last month?" "Is item X-472 in stock?"

Each of these calls costs your team time. A salesperson who spends two to three minutes per call answering a stock-check query, twenty times a day, loses an hour of productive selling time — every single day. Scale that across a team, and you are losing days of productivity per week to questions that a customer could answer themselves.

Worse, these calls create a bottleneck. When a customer cannot get through, they email. When the email is not answered promptly, they call again. Your customer service team becomes a manual data retrieval service rather than a relationship-building function.

The fix: A branded customer self-service portal.

A customer portal gives your clients 24/7 access to the information they need, directly from your existing business system. Order status, invoice download, stock availability, pricing, delivery tracking — all surfaced through a branded web interface that looks like your company, not like your ERP.

Customers log in, see their own data, and self-serve. Your team gets back hours of time every week. Your customers get faster answers and a better experience. And because the portal connects to your core platform via API, the data is live — not a nightly export or a stale spreadsheet.

Problem 5: Reporting Is Painful

"Can I get the sales figures for last month?" is a question that should take thirty seconds to answer. In many organisations running legacy business software, it takes half a day.

The native reporting tools in most ERP systems are functional but limited. They produce standard reports that serve general needs, but the moment you need something bespoke — a margin analysis by customer group, a delivery-performance trend, a production-efficiency breakdown — you hit the limits of the built-in tools.

Power BI is the typical next step, and it works. But it adds cost, complexity, and a separate data model. You need licences, a data gateway, someone to build and maintain the data model, and someone to design the reports. For a mid-market business, Power BI can easily cost £10,000–£20,000 per year in licensing and consulting time, and the reports still rely on periodic data refreshes rather than live data.

The fallback position is the one that hurts most: someone in finance or operations manually exports data to Excel, builds a pivot table, formats it, and emails it around. By the time the spreadsheet arrives, the data is already twenty minutes old. By the time the recipient acts on it, it might be hours or days stale.

The fix: Live dashboards pulling data directly from your business system.

Build real-time dashboards that connect directly to your existing software via its API. Live revenue figures. Order pipeline status. Stock health indicators. Production throughput. All updated every thirty seconds, all accessible from any device, all pulling data straight from your system of record with no intermediate export or data model.

These dashboards are part of the interface layer, so they share the same authentication, security, and data access rules as your other applications. Management gets the information they need, instantly, without waiting for a spreadsheet to arrive by email.

Problem 6: Slow to Adapt

Your business changes. Markets shift. Customer demands evolve. New product lines launch. Regulatory requirements tighten. And every time something changes, your business software needs to change with it.

But changing enterprise software is not quick. Want to add a field to a sales order screen? That is a change request to your ERP partner. Want a new report for a new product line? That is a scoping document, a quote, a development cycle, a testing window, and a deployment. A four-week turnaround for a two-hour development job is not unusual. For larger changes, you are looking at months.

This slowness creates a perverse incentive: teams stop requesting changes. They adapt their processes to fit the software rather than adapting the software to fit the processes. They build workarounds. They develop shadow systems. The cost of this rigidity is invisible on a balance sheet, but it is enormous — lost efficiency, missed opportunities, and processes that drift further from best practice with every passing month.

The fix: An interface layer that can adapt independently.

When your user interface is decoupled from your system of record via an API, you can change the interface without touching the core platform. A new field on a screen becomes a frontend change — days, not weeks. A new report becomes a component addition, not a customisation of the underlying ERP. A new workflow for a new product line becomes a configuration change in the interface layer, not a modification to the business system.

This agility is the single biggest advantage of the interface-layer approach. Your core platform stays stable and upgradeable. Your interface evolves at the speed of your business.

Problem 7: Low User Adoption

You have invested hundreds of thousands of pounds in your enterprise software. You have paid for licences, implementation, training, and ongoing support. And yet, a significant portion of your team avoids using it.

We see this across almost every business we work with. Staff log into the system because they have to, but they do the real work somewhere else. They keep notes in a notebook. They track order status in a personal spreadsheet. They communicate updates via WhatsApp or email. They print screenshots and write on them with a pen.

Low adoption is not a sign of a lazy team. It is a rational response to a poorly designed system. When the effort required to complete a task in the software exceeds the effort required to complete it outside the software, people will choose the path of least resistance every time. This is not a failing of your staff. It is a failing of your interface.

The consequences are serious. When users avoid the system, data quality suffers. Orders are entered late. Stock levels are inaccurate. Customer records go unupdated. Decisions are made on incomplete or incorrect information. Your system of record becomes a system of fiction.

The fix: Interfaces designed for how people actually work.

Stop expecting your team to adapt to the software. Build software that adapts to your team. Study how they actually complete their tasks — not how the process manual says they should. Watch a warehouse operator for a morning. Sit with a salesperson while they take orders. Understand the friction points, the shortcuts, and the mental models they use.

Then build an interface that matches those mental models. A screen that surfaces the information they need, in the order they need it, with the actions they need to take front and centre. When the interface fits the workflow, adoption follows naturally.

Problem 8: Fear of Replacement

We have saved the most painful problem for last. You know your existing business software has problems. You can see the inefficiencies, the workarounds, the frustration. But the obvious solution — replacing the whole system with a modern ERP — feels impossible.

And for good reason. A full ERP replacement for a mid-market UK manufacturer or distributor costs £300,000 to £400,000. Gartner reports that more than 55% of these projects fail to meet their objectives. Panorama Consulting puts the figure closer to 60%. Even if your replacement succeeds, you are looking at nine to eighteen months of operational disruption, data migration, retraining, and business process redesign.

The risk is real. The cost is real. The disruption is real. So most businesses make a rational decision: they do nothing. They tolerate the problems because the alternative is too expensive and too dangerous.

But doing nothing has a cost too. It is the cost of daily inefficiency. The cost of low adoption. The cost of Excel workarounds. The cost of customer frustration. The cost of slow adaptation. These costs accumulate year after year, quietly eroding your margins while the ERP replacement decision sits in an endless cycle of deferral.

The fix: Modernisation without replacement.

There is a third option between "do nothing" and "rip and replace." Build a modern interface layer over your existing business system. Keep your current platform as the system of record. Keep your data, your integrations, your licensing, your upgrade path. Replace only the interface — the part your team interacts with every single day.

This approach delivers roughly 80% of the benefit of a full ERP replacement at about 20% of the cost. The 80% is the part your team sees and feels every day: the user experience, the mobile access, the customer portal, the live dashboards, the role-specific interfaces. The 20% cost saving comes from keeping the core platform — no data migration, no process redesign, no retraining, no eighteen-month implementation.

An interface layer is typically built in four to twelve weeks. It is fixed-price. It connects to your existing system via its REST API. Your core platform is untouched. If you ever decide to replace your ERP in the future, the interface layer comes with you — only the API adapter needs to be rewritten.

Summary: The Eight Problems and Their Fixes

How to Break Free From Legacy Software Without the Risk

The eight problems above share a common root cause: your interface is tightly coupled to your system of record. When the interface is embedded in the core business system, any improvement to the interface requires a change to the core platform. That is expensive, slow, and risky.

The solution is to decouple them. Build a modern interface layer that sits between your team and your existing business software. The interface layer reads and writes data in real time via your system’s API. Your core platform stays untouched. Your data stays where it is. Your upgrade path stays clear.

Here is what the architecture looks like in practice:

Your Existing Business System (ERP)
         │
         │  REST API — authenticated, real-time read/write
         ▼
Sysgraft Interface Layer
React · Next.js · TypeScript
         │
         ├── Role-Specific Staff Portals
         │   · Warehouse: pick lists, barcode scanning
         │   · Sales: orders, stock, pricing
         │   · Production: job status, materials
         │
         ├── Customer Self-Service Portal
         │   · Order status, invoices, stock checks
         │
         └── Management Dashboards
             · Live KPIs, revenue, pipeline, stock health

This approach works with almost any modern ERP that exposes a REST API — Business Central, Sage 200, OrderWise, SAP Business One, Epicor, IFS, Infor, and many others. If your system has an API, we can build an interface layer on top of it.

A Note on Terminology: What We Mean by Legacy

When we say "legacy business system" or "legacy enterprise software" in this guide, we are not necessarily talking about a thirty-year-old mainframe running COBOL (though that might apply too). We are talking about any business platform whose user interface has not kept pace with modern expectations.

That includes relatively modern ERP systems. Dynamics 365 Business Central was released in 2018, but its web client still carries UX patterns from the Dynamics NAV era. Sage 200 is still widely used and actively developed, but its interface still reflects design conventions from the early 2000s. Even cloud-native platforms often prioritise functional depth over usability, because they are designed to serve every possible customer rather than the specific needs of your team.

Legacy is not about the age of the software. It is about the gap between what the software offers and what your team needs. And that gap is what an interface layer closes.

---