How do you connect CRM to ERP?

You connect CRM to ERP by appointing one leading system for each piece of data and letting that data flow in one direction only: customer master data, items and prices from ERP to CRM, won deals as orders or projects from CRM to ERP, and invoice and payment status back from ERP to CRM. The data model is the hardest part: a CRM thinks in accounts and deals, an ERP in debtors, items and orders. If you sort out that translation and the keys first, you get an integration that works. If you start with a two-way sync of everything, you get two systems overwriting each other.

Why are CRM and ERP hard to connect?

An integration between CRM and billing is mainly about one handover: a won deal becomes an invoice. That is covered in how to connect CRM to billing. An integration with the ERP is broader, because the ERP is more than invoicing. It manages customers, items, prices, stock, orders, projects, hours, purchasing and the financial ledger.

The two systems are built around a different picture of reality:

One account in the CRM can be five debtors in the ERP. One deal can become three orders. A freely described product has to be given an item code. Someone has to record that translation, and that is the real work of an integration. Why the two systems give a different revenue figure is explained in CRM vs ERP: where does your real revenue come from?.

Which data flows in which direction?

A workable split that holds for most B2B companies:

From ERP to CRM

• Customer master data: debtor number, legal name, company registration number, VAT number, billing address. The ERP leads here because this data has to be legally correct.
• Items and price lists: so salespeople can only quote products that exist, at prices that are right.
• Customer-specific price agreements: so a salesperson can see what price a customer has.
• Invoice and payment status: what has been invoiced, what is outstanding, what is overdue. So an account manager does not offer a new deal to a customer with three unpaid invoices without knowing it.
• Actual revenue per customer: so sales sees customer value the way finance sees it.

From CRM to ERP

• New customers: as a request, not as a final debtor record. Finance checks and completes it.
• Won deals: as an order, project or contract, with lines, item codes, prices, delivery date and a reference to the deal.
• Billing contacts: where the CRM is the best source for them.

What does not sync

• Pipeline, opportunities, notes and activities belong in the CRM and do not need to go to the ERP.
• Stock, purchasing, general ledger and hours belong in the ERP and do not need to go to the CRM, except as a summary.

The principle: every piece of data has one source, and the other side reads along. Two systems that are both allowed to change the same field is the fastest route to a conflict nobody notices.

Which keys do you need?

An integration stands or falls with the keys that connect records in both systems.

1. Customer: the debtor number from the ERP as a field on the CRM account. For groups with several entities: several debtor numbers under one account, or one account per entity with a parent relationship.
2. Item: the item code from the ERP as the product code in the CRM. No more free-text product lines in deals that go to the ERP.
3. Deal to order: the deal number from the CRM as a reference on the order in the ERP, and the order number back on the deal.

With these three keys you can always trace which deal belongs to which order and which invoice. That is the basis for bringing sales and financial data together into one picture, as described in how to connect sales data with financial data.

In what order should you build it?

1. Clean up. Merge duplicate accounts in the CRM, flag inactive debtors in the ERP. Start with the customers that bring in the most revenue.
2. Connect customers. Every active CRM account gets its debtor number. Where that fails, the account or the debtor is probably a duplicate or out of date.
3. Items and prices from ERP to CRM. So new deals only use existing items.
4. Won deals to ERP. First as a draft order that sales support or project administration confirms.
5. Status back to CRM. Invoice and payment status on the deal and the account.
6. Reconcile. Monthly: every won deal has an order, every order an invoice, and the amounts match.

This takes weeks to months, depending on the state of the data. The first two steps usually take the most time. They also deliver something straight away: a CRM in which every customer is linked to a debtor shows, for the first time, what a customer really buys.

Common mistakes

• Syncing everything both ways. Sounds complete, leads to overwrites and loops. Choose one direction per field.
• Creating new customers automatically as debtors. Then you get debtors without a VAT number, with a wrong address, or twice. Let finance confirm.
• Letting the CRM overwrite prices. A salesperson who changes the price should record it as a discount, not by changing the item price. Otherwise you can no longer see later what the list price was.
• No error handling. An order that cannot be created because the item does not exist has to reach a person, not a log file.
• No owner after go-live. Systems change. A new field, a new item, an ERP update. Without an owner, the integration breaks without anyone noticing.

Worked example

Worked example: suppose you are a technical services company with EUR 20 million in revenue, 1,200 active customers in the ERP and 1,900 accounts in the CRM. While connecting the two, you find:

• 350 CRM accounts are duplicates or out of date.
• 180 debtors, together accounting for EUR 2.1 million in revenue, have no account in the CRM. Account managers do not know these customers order through sales support.
• 45 deals won in the past year have no order in the ERP. After investigation, 12 of them were delivered and never invoiced, together EUR 95,000.

The first is clean-up work. The second is a commercial blind spot: customers worth EUR 2.1 million in revenue with nobody working on upsell or retention. The third is directly missed revenue. All figures are an example, but the pattern is common: the integration first shows how far the systems had drifted apart.

Architecture: direct or through a middle layer?

A direct integration between CRM and ERP works well if those are the only two systems. If you also have a separate billing system, time tracking, a web shop and a support system, it becomes a web of integrations. A middle layer is often better then: an integration platform or a central data layer that reads all systems and makes the connections. The trade-offs are covered in revenue data architecture for B2B.

For companies where the order cycle is central, such as wholesale and manufacturing, the ERP integration is the backbone of order-to-cash. For every company it is a building block of a single source of truth for revenue.

Frequently asked questions

Can I connect CRM and ERP without a developer?

For common combinations, such as Salesforce or HubSpot with NetSuite, Dynamics, Exact or AFAS, there are ready-made connectors or integration platforms that need no programming. For custom fields, multiple entities or complex pricing models you usually need someone with technical knowledge. The design, which data goes which way, is always business work.

Should the ERP or the CRM lead for customer data?

The ERP for legal and financial data. The CRM for contacts and commercial information. Record it field by field.

How long does it take to connect CRM and ERP?

That depends mainly on the state of your data. With clean, linked customer and item lists it takes weeks. With thousands of duplicate accounts and free-text product lines, the clean-up takes longer than the integration itself.

What if we switch ERP?

Then an integration with clear keys and a documented data model is an advantage: you know exactly which data goes in which direction, and you can take that design with you to the new system.