Connecting the Dots: How to Integrate ERP With the Systems Your Business Already Runs On

The Myth of the Clean Slate

Ask any mid-sized manufacturer in Brabant or a logistics firm outside Gothenburg how many business applications they run, and the honest answer is usually "more than we'd like to admit." There's the CRM sales insisted on, the WMS that came with the warehouse expansion, a Nordic payroll system that handles local tax rules no global vendor supports properly, an e-commerce platform, a BI dashboard, and — inevitably — a set of Excel files that quietly hold the business together.

ERP implementations are often sold as the cure: one system, one source of truth, everything else retired. In reality, that rarely happens. Some systems are too specialised to replace. Others are contractually locked in for another three years. And a few are genuinely better than what the ERP offers out of the box.

This is why ERP integration — not ERP replacement — is the defining challenge for most European SMBs. Getting the integration architecture right determines whether your ERP becomes the backbone of the business or just another expensive data island.

Why Integration Makes or Breaks the Business Case

The financial case for ERP almost always rests on eliminating manual work and improving decision-making speed. Both depend entirely on data flowing automatically between systems.

Consider a typical scenario: a Belgian wholesaler implements a modern ERP but keeps its existing e-commerce platform. Without integration, every online order is re-keyed into the ERP. Stock levels shown to customers are updated once daily. Credit checks happen after the fact. The ERP works perfectly — and the business sees almost none of the promised benefit.

Now consider the same firm with proper integration: orders flow in within seconds, stock availability is live, customer credit status is checked at checkout, and finance sees revenue in real time. Same ERP, same e-commerce platform, radically different outcome.

The lesson is uncomfortable but important: the value of an ERP is largely realised at its edges, where it touches the rest of your technology landscape.

Mapping Before Building: The Integration Audit

Before any technical work begins, you need a clear picture of what actually exists. In our experience, most SMBs discover 20–40% more integration points than they initially assumed — usually hidden in departmental tools, partner portals and automated email flows.

A useful audit covers four questions for every system:

What data does it own? Identify the system of record for each data domain — customers, products, prices, stock, employees, invoices. Two systems claiming ownership of the same data is the single most common cause of integration chaos.

How often does data need to move? Not everything needs to be real-time. Nightly batch synchronisation is perfectly adequate for general ledger postings or product catalogue updates, and it's dramatically cheaper to build and maintain than event-driven streaming.

What does the system support technically? Modern SaaS tools offer REST APIs and webhooks. Older on-premise systems may only support flat-file exports or direct database access. Knowing this early prevents architectural surprises.

Who depends on it? Integration projects fail when a "minor" legacy tool turns out to be critical for a regulatory report that only one person knows how to produce.

Choosing an Integration Approach

There are broadly three patterns European SMBs use, and the right choice depends on scale and complexity rather than fashion.

Point-to-Point Connections

Direct connections between two systems are quick to build and easy to understand. For a business with three or four applications, this is often entirely appropriate. The risk is combinatorial: ten systems connected point-to-point can require up to 45 separate interfaces, each needing maintenance when either side changes.

Integration Platform (iPaaS)

Middleware platforms — Azure Integration Services, MuleSoft, Boomi, or lighter-weight tools like Make and n8n — act as a central hub. Each system connects once to the platform, which handles routing, transformation and error handling. For SMBs running six or more connected applications, this usually becomes the economical choice within 18 months.

API-Led Architecture

The most mature approach exposes standardised APIs around core business capabilities, allowing new applications to plug in without bespoke work. It requires more upfront design discipline but pays off for companies growing through acquisition or expanding across multiple Nordic and Benelux markets with differing local requirements.

The European Complications Nobody Mentions in the Demo

Integration projects in Europe carry constraints that generic vendor documentation glosses over.

GDPR and data residency. Every integration that moves personal data creates a processing activity that must be documented. If your ERP is hosted in Ireland and your HR system in Germany, transfers need a lawful basis and appropriate safeguards. Building data minimisation into your interfaces — sending only the fields genuinely required — is both good practice and good compliance.

E-invoicing mandates. Belgium's B2B e-invoicing obligation from January 2026, the Peppol network across the Nordics, and evolving requirements in the Netherlands and France mean your ERP-to-finance integration must handle structured invoice formats natively. Retrofitting this later is far more expensive than designing for it now.

Multi-country, multi-entity complexity. A Dutch parent company with Swedish and Danish subsidiaries faces three VAT regimes, three chart-of-accounts conventions and three payroll systems. Integration design must accommodate local variation without fragmenting group reporting.

Language and character handling. Danish, Swedish, Norwegian and Finnish characters still break poorly configured interfaces with remarkable regularity. Test with real data, not placeholder names.

Practical Steps That Reduce Risk

Start with the highest-friction process. Don't integrate everything at once. Identify where manual re-keying costs the most hours — usually order-to-cash or procure-to-pay — and prove the model there first.

Insist on error handling from day one. Integrations fail. Networks drop, APIs rate-limit, data arrives malformed. The question is whether failures are visible and recoverable, or whether they silently corrupt data for weeks. Every interface needs logging, alerting and a defined retry or escalation path.

Build a data governance layer. Agree, in writing, which system owns which data and how conflicts are resolved. This is organisational work, not technical work, and it's where most projects under-invest.

Plan for total cost of ownership. A custom-built interface costs roughly 15–25% of its build cost annually to maintain. Factor this in when comparing bespoke development against platform-based solutions.

Test with production-scale volumes. An interface that handles 50 orders in testing may collapse at 5,000 on Black Friday.

Where External Expertise Earns Its Keep

Integration is one of the few areas where experience genuinely shortens the path. Consultants who have connected the same combinations of systems across multiple clients recognise the failure modes early — the API that throttles unexpectedly, the ERP module that doesn't expose the field you need, the local tax rule that requires a workaround.

Just as valuable is the outside perspective on ownership disputes. When sales and finance both believe they own customer master data, an independent party can broker a decision faster than internal negotiation typically allows.

The goal isn't dependency on external help. It's arriving at an architecture your own team can operate confidently — documented, monitored and understood.

At GEC Business Growth Services, we help SMBs across the Benelux and Nordics design integration architectures that connect ERP with the systems they've already invested in — without disruptive rip-and-replace programmes. If you're planning an ERP rollout or struggling with a landscape that doesn't quite talk to itself, we'd be glad to review your current setup and map the practical route forward.