Think Build Implement Repeat
Data & Scraping

Working With the ERP You Have Rather Than Replacing It

Last updated:

Replacement is the expensive default

When an ERP frustrates people, the proposal that arrives is replacement: a multi-year, seven-figure programme with a high failure rate and a period of degraded operations in the middle.

Sometimes that is right. Often the actual complaints — no mobile access, poor reporting, no customer portal, rigid workflow — are gaps that can be filled around the system rather than by replacing it.

What is usually fixable around the edges

  • Mobile capture for warehouse, field or shop floor, writing back into the ERP
  • Customer or supplier portals reading and writing through an integration layer
  • Reporting, by replicating data out to somewhere designed for querying
  • Workflow and approvals, handled outside and recorded inside
  • Document handling and extraction feeding structured data in

Each of these is weeks rather than years, and each addresses a specific complaint.

Find out what the ERP actually exposes

The feasibility question is what interfaces exist: a documented API, a supported integration layer, database access, or only file import and export. All four are workable; they differ in cost.

Ask your ERP vendor in writing what integration is supported and what it costs. The answer changes the project price more than any design decision, and vendors sometimes charge for API access.

Protect the ERP as the record of truth

Everything built around it should treat the ERP as authoritative for the data it owns. The failure mode is a satellite system that starts holding its own version of stock or orders, and then the two disagree.

Read freely, write deliberately, and never let a peripheral system become a second source of truth by accident.

When replacement is genuinely unavoidable

  1. The vendor has ended support and security updates have stopped
  2. The data model cannot express what the business now does, whatever you build around it
  3. Integration is impossible or priced punitively by the vendor
  4. The total cost of workarounds now exceeds the replacement over a realistic horizon

Note that three of those four are commercial rather than technical, which is usually the case.

Frequently asked questions

Is building around an ERP just delaying the inevitable?

Sometimes, and delay has value: it spreads cost, it keeps the business running, and it produces a much clearer specification if replacement does eventually happen.

What does an integration layer cost?

A layer with a couple of connected applications typically £25,000–£60,000. Considerably less than an ERP replacement, and deliverable in months rather than years.

Will the vendor support us doing this?

Attitudes vary. Some provide good integration support; others discourage it commercially. Establish the position early because it shapes what is viable.

What about reporting performance?

Replicate data out rather than running heavy reports against the production ERP. It is faster, safer and it stops reporting load affecting operations.

Keep reading

Being quoted for an ERP replacement?

Tell us what the actual complaints are. Frequently three of the four can be solved around the system for a fraction of the price.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Web ScrapingData Science