Back to Blog

CRM ERP Integration: Architecture, Methods and a First Flow You Can Build

Decide which system owns each field, pick the integration method that fits your ERP's interface, and ship one reliable event before you sync anything else.

Benjamin WagnerBenjamin Wagnerby Benjamin Wagner
CRMERPIntegration

A CRM ERP integration passes a small set of identifiers and statuses between the system where you sell and the system where you deliver and bill. The CRM owns people, relationships, deals and conversations. The ERP owns the customer account used for billing, items, orders, stock and payments. The integration fires on defined business events, such as "deal won", and writes each system's reference number back into the other.

Most small teams should start with one one-way flow: a won deal creates the customer and an order in the ERP, and the ERP order number comes back to the deal. Build that through a native connector if your two systems have one, otherwise through the ERP's REST API and webhooks, using an automation platform such as n8n or a small service you run.

Customermates, an AI-native CRM, publishes this guide. Customermates is a CRM only, with no ERP functions and no native ERP connector; the section on it below shows how it connects through its REST API and webhooks. ERP vendor details were checked on 8 October 2026 on the vendors' own pages, linked at the end.

For a fixed integration and an AI client, compare MCP versus API on the same customer-record task. Tool discovery changes how the client finds an operation; authentication and permissions still apply.

For an n8n workflow, the n8n MCP route comparison and version-pinned example distinguish connecting n8n to a customer-data server from exposing n8n itself to an AI client. Choose the direction before configuring credentials.

At a glance

What moves
Identifiers and a few statuses per business event. Not every field, and not in both directions by default.
Methods
Native connector, automation platform (iPaaS or n8n), direct API integration, or middleware. Or one suite whose ERP includes a CRM app.
Decide first
One owning system per field, a stable ID strategy, and what happens when an event arrives twice or fails.
Check your ERP
Whether its API is in your plan, whether it sends webhooks, and its rate limits. They differ a lot between vendors.
Customermates
REST API on every Cloud plan, webhooks on every paid plan, and both when self-hosted. ERP references live in custom Text fields.

Which system owns each field in the integration architecture?

Write this table for your own systems before you compare tools. Ownership is decided per field, not per object: the organization can live in both systems while its billing address belongs to the ERP and its account notes belong to the CRM.

DataUsually owned byWhat the other side keeps
Contacts, relationship history, conversationsCRMThe ERP keeps a contact person only if its documents need one
Deal, stage, next stepCRMNothing, or a reference on the order
Customer account for billing (legal name, VAT ID, billing address, payment terms)ERPERP customer number; the integration treats it as ERP-owned
Items and pricesERPItem number on the CRM's product or service record
Orders, delivery, stockERPOrder number and one customer-facing status
Billing documents and paymentsERPDocument number and a coarse payment status, if account managers need it

If two systems both write the same field, you have a conflict waiting to happen. Pick one owner and route corrections there. Enforce that rule in your integration; a CRM may not offer a field-level permission that makes just this field read-only.

Four ways to connect a CRM and an ERP

MethodFits whenWatch for
Native connectorBoth systems come from vendors that ship a connector for each otherWhich objects, fields and directions it covers, which editions it needs, and who supports it when it breaks
Automation platform (iPaaS, n8n, Make, Zapier)You need a few flows between two systems with REST APIs and want visual logicIdempotency, error queues and secrets are still your job. A visual flow is production software
Direct API integrationOne narrow, valuable flow between two stable APIs, and someone on the team writes codeYou own authentication, retries, API version changes and monitoring
Middleware or integration serviceSeveral systems or high volume, with a shared data model and queuesMore moving parts. Too heavy for moving five fields

There is a fifth answer that some readers searching "CRM ERP Komplettlösung" or "can CRM be part of ERP" are after: one suite. Odoo, for example, ships a CRM app alongside its ERP apps, so the customer record is shared and there is nothing to sync. The tradeoff is that you use the suite's CRM. Note that Odoo makes its external API available only on its Custom plan, so connecting any outside system to Odoo needs that plan.

Sync patterns and when to use them

PatternHow it worksUse it for
Event-driven, one wayA change in the owning system triggers a write in the otherThe first flow. Direction and ownership stay obvious
Scheduled reconciliationA job compares cross-references and lists or repairs gapsA safety net under every event flow
Lookup at read timeOne system asks the other for current data without storing a copyStock or payment status shown on demand
BidirectionalBoth systems update related dataOnly when the business really changes the data in both places, with per-field ownership and conflict rules

"Real time" is rarely the requirement it sounds like. An account manager who sees a payment status a minute late loses nothing; a duplicate order in the ERP costs real money. Design for retries and duplicates first, speed second.

What your ERP's interface actually offers

The ERP side usually decides how hard the integration is. Four examples show how much the interfaces differ:

ERPInterface, according to the vendorWhat it means for the integration
Microsoft Dynamics 365 Business CentralREST API v2.0 with entities such as customers, items, salesQuotes, salesOrders and salesInvoices, plus webhook subscriptionsSubscriptions expire after three days unless renewed, and notifications wait 30 seconds after the first change. More than 1,000 changes in that window arrive as one "collection" notification that you must resolve with a query
OdooXML-RPC external API in version 18; version 19 documents the JSON-2 API and a migration path from XML-RPC and JSON-RPCAvailable only on the Custom plan. Check which API your Odoo version runs before you build
Lexware OfficeREST API for contacts, articles, quotations, order confirmations, delivery notes and other vouchers, with event subscriptionsUp to 2 requests per second per client, so batch jobs need throttling
XentralREST API for customers, products, sales orders, purchase orders, delivery notes and invoices, with webhooks and a list of webhook event typesSeveral API versions exist side by side, so pin the version in your mapping

Two questions save the most time: is the API included in the plan you pay for, and does the ERP push changes by webhook or do you have to poll it?

Events, idempotency and reconciliation

An integration that only handles the happy path will create duplicates within weeks. Webhooks get retried, people click twice, and a timeout can hide a write that actually succeeded.

  • Idempotency. Before creating anything in the target, check whether it already exists. The simplest check is the cross-reference itself: if the deal already holds an ERP order number, do not create another order.
  • Stable IDs. Store the other system's ID after the first match. Never match companies by name on every run; names change and subsidiaries share them.
  • Retries. Retry timeouts, rate limits and server errors with backoff. Stop on validation errors and put the event in a repair queue with the reason.
  • Conflicts. Decide them as business rules: the owner wins, or a person decides. Never apply "last write wins" across the board.
  • Reconciliation. Run a scheduled check that lists records missing a cross-reference or showing different statuses on both sides. It catches whatever the event flow missed.
  • Logging. Record event, source record, target reference, attempt count and result, without copying more customer data into logs than diagnosis needs.

Building the first flow

  1. Pick one business event

    "Deal won creates the ERP customer and order" is a good first event. "Sync CRM and ERP" is not an event.

  2. Define the preconditions

    List the fields that must be filled before the event may fire: billing address, VAT ID, items, quantities. Decide what blocks the event and who fixes it.

  3. Write the field map

    For each field: source, target, type, owner, transformation, and what happens when it is missing or invalid. Keep the map versioned next to the integration.

  4. Choose the method

    Native connector if one covers the flow; otherwise an automation platform or a small service against both REST APIs.

  5. Build idempotency and the write-back

    Check the cross-reference before creating, then write the ERP number back to the CRM record in the same run.

  6. Test the awkward cases

    Existing customer, two companies with the same name, missing address, unknown item, ERP timeout, the same event delivered twice, deal reopened after "won".

  7. Roll out with reconciliation

    Start with one team or one deal type, compare both systems by hand for the first weeks, then switch on the scheduled reconciliation and name the person who handles failures.

Example: won deal to ERP order with Customermates

This is the setup in Customermates for the first flow above. It uses the REST API and webhooks, which work in a self-hosted installation and on Customermates Cloud: the REST API on every plan, webhooks on every paid plan. The receiver in the middle is yours: an n8n workflow or a small service.

Fields. In Data model, add custom fields of type Text: "ERP customer no." on organizations, "ERP order no." on deals, and "ERP item no." on services. A deal's line items each hold a service and a quantity, so the line items and their services' item numbers become the order lines. If account managers need delivery or payment state, add a Single choice field such as "ERP status" on deals and make ERP ownership an explicit rule in your adapter. Customermates has list and role permissions, not field-level permissions that reserve this field for the integration.

Trigger. This assumes your deals list has a Stage Single choice field with a "Won" option (stages are not preset). Under Settings → Webhooks, subscribe a URL to record.updated for the Deals list, optionally with Stage under Changed fields, and set a secret. Each delivery is signed with HMAC-SHA256 in the X-Webhook-Signature header, and for update events data.record.fields lists each changed field with its before and after value. Your receiver acts only when the stage changed to "Won".

Idempotency. Every event carries an id that stays the same on retries and resends, so deduplicate by it. As a second check, use the cross-reference: if the deal's "ERP order no." is already filled, stop.

Customer match. Look up the organization's "ERP customer no.". If it is empty, search the ERP by VAT ID or create the customer, then write the number back. To find a CRM organization by ERP number later, call POST /api/v1/records/query for Organizations with an eq filter on that field's ID (filter syntax).

Write-back. After the ERP accepts the order, send an update mutation for the deal to POST /api/v1/records/mutate with the new "ERP order no." and the deal's current version. Fields you leave out stay unchanged.

Failures. Customermates retries a failed delivery automatically for timeouts, network errors, 5xx responses and 408, 425 and 429. Other 4xx responses are not retried, because they would fail the same way. Every delivery appears under Settings → Webhook log, where you can resend it after fixing the cause.

Reconciliation. Save a deal view filtered to Stage "Won" and "ERP order no." empty. Share it with the person who handles integration failures, or with the whole team. Anything that shows up there was missed by the event flow.

The reverse direction. If your ERP sends webhooks, point them at the same receiver, look up the deal by "ERP order no." and set "ERP status". If it does not, poll the ERP on a schedule. The n8n guide lists the REST calls an n8n workflow needs; a community node also exists.

In Customermates Cloud, Mate can work with these fields too, for example "list won deals from this month without an ERP order number". Mate uses hosted AI credits. An AI client of your own can do the same through MCP.

What did the small integration example actually prove?

Download the CRM and ERP field-ownership map and the bounded example result. The example uses the fictional customer C-001 and ERP reference ERP-C-001. Keep your own mapping beside the adapter:

ValueAuthorityCheck after writing
Customer display nameCRMRead the current CRM record before sending
CRM record IDCRMStore the unchanged ID in the mapping
ERP customer IDERPWrite it back only after the receiver confirms the saved customer
Billing and tax policyERPDo not overwrite it from a CRM note

Checked on 29 October 2026 against a disposable local Customermates workspace and a loopback mock ERP. A small, manually invoked adapter read the real CRM REST endpoint, sent one customer to the mock, and wrote the returned ERP ID into a custom Text field using the current record version. We deliberately dropped the first response after the mock had saved the customer. Retrying the same event produced two attempts, one ERP write. A read from each side then matched the CRM record ID, customer name and ERP ID.

This proves the ID map, retry rule and CRM read/write/readback in that example. It does not prove a production ERP connector, automatic webhook delivery, invoice creation or a deployed reconciliation job. Before using your own ERP, repeat those checks against its sandbox, verify authentication and signatures, and test its actual validation and rate limits. The integration options explain where an adapter or separately run n8n fits.

What drives cost and effort

No honest benchmark covers all CRM ERP integrations; a one-way event between two documented APIs and a two-way sync of orders and stock are different projects. Estimate from these drivers:

  • whether the ERP's API is in your current plan, or needs an upgrade;
  • whether both systems send webhooks, or one has to be polled;
  • the number of objects, fields, directions and transformations;
  • how messy existing customer data is, and how many duplicates need matching once;
  • rate limits and volume;
  • who runs the automation platform or service, and who answers its alerts.

On the CRM side, the REST API needs no particular Customermates plan and webhooks come with every paid plan. A three-person team on Starter pays €36 per month. The unified inbox, which brings email, LinkedIn and WhatsApp conversations to the same records, starts with Pro (€29 per user per month).

Before a won deal becomes an ERP order, the conversation that won it sits on the client record, with a reply and a next step drafted by Mate or your own AI client for you to review and send. To see that part on your own clients, start your 14-day trial. No credit card.

Common mistakes

  • syncing every field before one event works end to end;
  • letting both systems own the same field;
  • matching companies by name instead of stored IDs;
  • no repair queue, so failed events vanish into logs;
  • ignoring cancellations, reopened deals and corrections;
  • launching without a reconciliation check or a named person for alerts.

For the difference between the two system types, and when a small team needs an ERP at all, read CRM and ERP compared.

FAQ

What is CRM ERP integration?

It is the automated exchange of selected identifiers and statuses between the CRM, where you manage relationships and deals, and the ERP, where you manage orders, items, stock and billing. Done well, it moves only what a defined business event needs and keeps one owner for every field.

How do you integrate a CRM and an ERP?

Define field ownership, pick one business event such as "deal won", and choose a method: a native connector if your systems have one, otherwise the ERP's API and webhooks through an automation platform or a small service. Add idempotency checks, a write-back of the other system's ID, and a scheduled reconciliation before you go live.

Are CRM and ERP the same, and can a CRM be part of an ERP?

They are different systems: CRM covers selling and customer relationships, ERP covers delivery, purchasing, stock and finance. Some suites include both. Odoo, for example, offers a CRM app next to its ERP apps, which removes the need for an integration between the two.

Should CRM and ERP sync in both directions?

Usually not at first. A one-way event from CRM to ERP, plus a returned order number and one status field, covers most needs of a small team. Add a second direction only for fields that really change in both places, with per-field ownership.

Can you integrate CRM and ERP without code?

Often yes, with a native connector or an automation platform such as n8n, Make or Zapier. You still have to decide field ownership, handle duplicates and failures, and check whether your ERP plan includes API access.

Does Customermates integrate with ERP systems?

Through its REST API and webhooks, yes, using an automation platform or service you run. There is no native ERP connector, and Customermates itself holds no ERP data such as orders or payments. ERP references go into custom fields on organizations, deals and services.

ERP vendor details checked on 8 October 2026 against Microsoft's Business Central API v2.0 and Business Central webhooks, Odoo's external API for version 18, external API for version 19 and pricing, the Lexware API documentation and the Xentral developer documentation.

Start from one description

One description. A workspace your agent built.

This is what setup builds from one sentence. Sample data, the real product.

  1. Describe your business

    One sentence about your team, your clients and how you sell.

  2. Mate builds it

    It asks a few questions, then creates the lists, pipeline, dashboard and playbook.

  3. Work in it

    Connect LinkedIn and email. Click through a finished example below.

Your description to Mate

We're a four-person strategy consultancy. Track clients, engagements and proposals, and help us follow up with prospects on LinkedIn.

Widgets built from the workspace's own lists and fields

Customermates for consultants

Every client conversation from email, LinkedIn and WhatsApp in one place. Mate sets up your workspace and drafts the follow-up, you review and send. Works with Claude, ChatGPT or any agent that speaks MCP.

Customermates

Follow up on every client conversation

Start with one channel and one client on Customermates Cloud, or self-host the open-source core.

✓ No credit card required ✓ First 14 days free