CRM and ERP: how to split the data without creating duplicates
Most integrations fail for one reason: two systems are allowed to change the same piece of information. That is where duplicated customers, conflicting contract prices and stock that matches nowhere come from.
The fix is not technical but governance: for each entity, one system owns it and the other consumes it.
Splitting responsibilities
1Customer - CRM owns the relationship, ERP owns the legal identity
The CRM owns contacts, history and account ownership. The ERP stays the owner of tax data and the customer code. The join key is the tax ID, never the name.
2Product and price - ERP owns, CRM reads
The catalogue and contract price lists live in the ERP. The CRM displays them at quoting time. The acceptable exception is a negotiated price on an open opportunity, which becomes official only after approval.
3Stock - ERP owns, CRM shows with a freshness stamp
Do not replicate stock, read it. Show the last update time next to the figure; a rep who knows the number is 15 minutes old makes better decisions than one seeing a number with no context.
4Order - CRM creates it, ERP validates it
The order starts in the CRM with preliminary validations (credit limit, stock, maximum discount) and is passed to the ERP where it becomes an official document. The status returns to the CRM so the seller can answer the customer.
5Invoice - ERP owns, CRM shows the balance
Invoicing and the ledger stay in the ERP. The CRM only needs the customer's balance and overdue amounts so reps do not keep selling to a blocked account.
Avoiding duplicates at import
- Deduplicate by tax ID before the first import, not after
- Allow a single direction for creating new customers
- Log every sync and keep a visible conflict report
What to check after the first month
The number of customers created in both systems on the same day, the number of orders rejected by the ERP, and the gap between stock shown in the CRM and real stock at quoting time. Those three numbers tell you whether governance holds.
Aktualizacja:
Najczęstsze pytania
Does synchronisation have to be real time?+
For stock and balances, as close to real time as possible. For customers and products, a few minutes is enough. Orders are passed immediately, with acknowledgement.
What if the ERP has no API?+
You work with scheduled file exchange or controlled direct database reads. It is slower, but the governance rule stays the same: one owner per entity.
Can the CRM replace the ERP?+
For small companies, sometimes. For companies with manufacturing and complex accounting, no - the CRM takes over selling and the relationship, the ERP stays the ledger.
Powiązane pojęcia ze słownika
Gdzie sprawdza się CRMconnect
Chcesz zobaczyć CRMconnect w działaniu?
Spersonalizowane demo w 30 minut - bez karty, bez zobowiązań.
Umów demoPowiązane poradniki
CRM implementation in 30 days: the week-by-week plan
A realistic four-week CRM rollout: cleaning the customer base, configuring the pipeline, onboarding reps and producing the first forecast report.
CRMHow to choose a CRM for a B2B sales team
The criteria that decide a B2B CRM: field adoption, forecast quality, stock and contract pricing at quoting time. Includes the questions to ask in a demo.