Two systems that overlap just enough to cause arguments about which one owns the customer.
A CRM manages the relationship before and around the sale: leads, opportunities, activity, pipeline and service history. An ERP manages the transaction and everything after it: the order, the stock, the despatch, the invoice and the ledger. The overlap is the customer record, which is why the integration question is really a question about which system owns which field.
Businesses frequently buy one and try to make it do the other's job. A CRM asked to manage stock and invoicing becomes a weak ERP; an ERP asked to manage pipeline and activity becomes a CRM nobody uses because it was built for transactions rather than conversations. Knowing where the boundary sits saves both the licence and the disappointment.
CRM territory. Pipeline stages, activity logging, forecasting — none of which an ERP models naturally.
The handover. Often raised in CRM against ERP pricing, so the quote reflects real cost and availability.
ERP territory. Stock allocation, credit check, despatch and invoicing.
Usually CRM, reading installed-base and invoice history from the ERP.
One system owns it — usually the ERP, because finance depends on it — and the other subscribes.
A sales team works entirely in CRM. A rep builds a quote from a price list exported to a spreadsheet three weeks earlier, promises a four-day lead time based on what was true last month, and wins the deal.
The order reaches the ERP and two things are wrong. The price has changed, so the quoted margin does not exist. The item has a six-week lead time because the supplier moved. Neither was visible to the rep, because the CRM held a snapshot rather than a connection. Someone now has to go back to the customer, which costs credibility that the discount offered to recover it does not fully buy back.
The integration that prevents this is narrow rather than total: the quote screen reads live prices and available-to-promise from the ERP, and the won order writes through as a sales order. Nothing else needs to move. The common overreach is synchronising everything in both directions, which creates two systems that both believe they own the customer master and a reconciliation job that lasts forever.
| Term | What it means |
|---|---|
| Lead | An unqualified contact. Lives in CRM and should never reach the ERP. |
| Opportunity | A qualified potential deal with a value and an expected close date. |
| Quote | The point where CRM and ERP meet, because a quote needs real prices and real stock. |
| Account | The CRM view of an organisation, which becomes a customer master record in the ERP only once it transacts. |
| Write-back | Pushing ERP data — order status, invoices, outstanding balance — back into CRM for the sales team. |
The fastest route to duplicate records and disagreement about who the customer is. Pick an owner.
Quotes built on stale price or unavailable stock get renegotiated after acceptance.
Opportunity management needs a different data model and a lighter interface than a transaction system provides.
Salespeople need to see credit status before promising. Surface it rather than making them ask finance.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Quote-to-order conversion | Sales effectiveness, and the number both systems should agree on. | |
| Quoted vs invoiced margin | Whether quotes are built on live data. A persistent gap means the price list is a snapshot. | |
| Duplicate customer records | The classic symptom of two systems both mastering the customer. | |
| Sales data staleness | How old the ERP data visible in CRM is. Stale balances make the write-back worse than useless. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.