ERP integration is where most ERP value either lives or leaks. A perfectly selected ERP system that never connects cleanly to Xero, HubSpot, Shopify, 3PL and payroll is a stranded asset — finance still re-keys, operations still exports, and the "single source of truth" promise quietly dies. This guide walks through the architecture patterns, tools and pitfalls for ERP integration in the Australian mid-market.

What ERP integration actually means

ERP integration is the two-way movement of data between your ERP system and the rest of your stack — CRM, ecommerce, 3PL, payroll, expense management, marketing automation. Done properly, it means the ERP holds operational truth, Xero or MYOB hold the statutory ledger, HubSpot or Salesforce hold the customer relationship, Shopify holds the storefront — and they all agree.

Done poorly, it means spreadsheets, copy-paste, and "let me check which system is right."

The six integration patterns you will actually build

Across hundreds of ERP integrations we have seen across Australia, the same six patterns cover most of the work:

1. ERP ↔ General ledger

The ERP runs operational finance — inventory, job costing, manufacturing, projects — and posts clean summary journals to Xero or MYOB for statutory reporting. AP and AR can flow in either direction depending on where the team wants to work. For multi-entity groups, each trading entity keeps Xero and the group consolidates in the ERP or a finance-first platform like Sage Intacct.

This is our most common pattern. See our ERP integration service and Xero integration service for specifics.

2. ERP ↔ CRM

Customers, contacts, opportunities, orders and invoice status sync between the ERP and HubSpot, Salesforce, Dynamics 365 Sales or Zoho. Sales sees aging; finance sees pipeline. One customer record per customer, not three.

3. ERP ↔ Ecommerce

Shopify, Shopify Plus, WooCommerce or marketplace orders flow to the ERP. Stock levels sync back to the storefront. Fulfilment status, refunds and chargebacks all reconcile. Channel-level revenue and fees flow through to Xero or MYOB.

4. ERP ↔ 3PL / WMS

Orders hand off to StarTrack, CouriersPlease, ShipStation, Starshipit or a warehouse management system. Tracking writes back. Inventory reconciles. Returns handled in the ERP rather than a separate spreadsheet.

5. ERP ↔ Payroll

Employment Hero, KeyPay, Dayforce or ELMO post hours, leave and pay run journals cleanly into the ERP. Intercompany allocations handled at the source.

6. ERP ↔ Expense and AP automation

Weel, Expensify, Dext, Lightyear and similar capture spend and bills, which flow to the ERP for approval and posting. Bank feed reconciliation closes the loop.

Architecture choices: n8n, native, or middleware

There are three sensible architectural choices for ERP integration. Each has a place.

Native ERP connectors

Most cloud ERP platforms ship with vendor-supplied connectors — NetSuite's SuiteScript and SuiteFlow, Business Central extensions, MYOB Advanced's integration services, Sage Intacct's SmartConnect. These are well suited to flows that stay inside one platform's scope, are business-critical, and need vendor support.

When to use: High-volume, business-critical flows where vendor support matters and the integration stays inside one platform's scope.

Middleware platforms

Boomi, MuleSoft, Celigo, SnapLogic, TrueCommerce and SPS Commerce are integration platforms that sit between ERP and partner systems. They are particularly common for EDI with major Australian retailers (Bunnings, Woolworths, Coles), for complex multi-system orchestration and for businesses with existing middleware investment.

When to use: EDI, multi-system orchestration, businesses with existing middleware standards.

n8n and custom orchestration

n8n is an open-source workflow automation platform that has become our default for ERP integration work across the Australian mid-market. It has native connectors for Xero, MYOB, HubSpot, Salesforce, Shopify, WooCommerce, Employment Hero, Slack, plus generic HTTP, Postgres and event triggers. It runs self-hosted (Australian data residency), supports AI-enriched workflows, and keeps integration code in one place.

When to use: Multi-system orchestration, AI-enriched flows, businesses that want Australian data residency and transparency. See our n8n automation service.

In practice most mid-market businesses use a mix — native connectors for one-to-one flows, n8n for orchestration, occasional middleware for EDI.

The pitfalls that break ERP integration

Most failed ERP integration projects fail the same way. Watch for these:

1. Treating integration as an afterthought

If integration is scoped after ERP implementation starts, it will be rushed, under-tested and brittle. Scope integration up-front, with its own phase and budget.

2. No monitoring

An integration that runs silently for six months before anyone notices a broken flow is common — and expensive. Every integration should have a dashboard, alerts on failed runs, and a response SLA. If you don't monitor it, you don't have it.

3. No retry logic or dead-letter queues

APIs fail. Vendors throttle. Networks drop. Integrations without retries and dead-letter queues lose data quietly. Build retries in from the start.

4. Ignoring edge cases in data

The edge cases — unusual tax codes, split shipments, multi-currency refunds, terminated employees with final pay — are where integration breaks. Map them in discovery, not at go-live.

5. No human-in-the-loop for ambiguous records

Some records will always need human judgement — unusual supplier invoices, mismatched customer names, ambiguous GST treatment. Build a review queue for these, don't pretend the automation will handle 100%.

6. No plan for API changes

Vendor APIs change. Xero, Shopify, HubSpot, Salesforce — all have deprecated endpoints periodically. A managed integration includes API change monitoring and planned upgrades.

ERP integration cost in Australia

Ranges vary with scope but a fair 2026 guide:

Discovery: $3,000–$8,000 to map current state and scope the build
Build per integration flow: $5,000–$25,000 depending on complexity and volume
Managed operations: $1,500–$8,000 per month for ongoing monitoring, maintenance and enhancement

Total mid-market ERP integration program (4–8 flows): typically $40,000–$150,000 one-off plus $3,000–$6,000 per month managed. Pricing scales with number of flows, not with vendor brand.

See our ERP integration service for a fixed-fee scoping call.

Industry-specific integration patterns

Different industries need different integration patterns. Deeper playbooks:

Construction ERP integration — job costing, subcontractor, field apps
Manufacturing ERP integration — BOM, shop floor, MES, ecommerce
Distribution ERP integration — multi-warehouse, 3PL, EDI, marketplace
Ecommerce ERP integration — Shopify, WooCommerce, Amazon, 3PL
Finance ERP integration — multi-entity, consolidation, banking
Professional services ERP integration — PSA, time, billing

Frequently asked questions

Can I integrate my ERP with Xero?

Yes — this is our most common pattern. NetSuite, MS Dynamics 365 Business Central, SAP Business One, MYOB Advanced, Cin7 and most industry ERPs integrate cleanly with Xero. Journals, AP, AR and payroll can all flow through.

How long does ERP integration take?

Typical integration flow takes 4–10 weeks from scope to production, depending on complexity. A full mid-market integration program (6–8 flows) runs 3–6 months, usually in parallel with ERP implementation.

Do I need middleware for ERP integration?

Only for specific cases — EDI with major retailers, multi-system orchestration where n8n or native connectors are not sufficient, or where existing middleware investment dictates. Most mid-market ERP integration in 2026 is done with native connectors plus n8n.

What happens when a vendor API changes?

If the integration is managed, it gets updated before the API change takes effect. If unmanaged, it breaks and is discovered when someone notices missing data. Managed ERP integration is worth the monthly cost for this reason alone.

Does ERP integration support AI agents?

Yes. An ERP integration layer is a prerequisite for AI agents — the agent needs a consistent data source to read from and a safe action surface to write to. Our Xero AI agent service builds directly on top of integration infrastructure.

The bottom line

ERP integration is not a technical afterthought — it is where ERP value is realised or lost. Treat it as a first-class work-stream, use the right architectural pattern for each flow, monitor everything, and plan for API change. The businesses that get this right run ERP and Xero (and HubSpot, and Shopify, and 3PL) as one connected stack. The businesses that get it wrong spend the next decade re-keying. Book a scoping call and we will tell you honestly which category you are in.

ERP Integration: How to Connect Your ERP to Xero, CRM and Ecommerce in 2026