CRM and ERP integration: what to sync and what to leave alone

Most failed CRM–ERP projects share one mistake: nobody decided which system owns which field.

Decide the system of record per entity

Write it down, field by field. Typically: the CRM owns prospect data, pipeline, activities and forecast; the ERP owns items, stock, invoices, payments and accounting entities. Customer master data needs a single owner — usually the ERP after first invoice, the CRM before it.

Sync one direction wherever possible

Bidirectional sync doubles the failure modes. Push closed-won deals to the ERP; pull invoice and payment status back. Two-way sync is justified only for shared master data with clear conflict rules.

Keep the payload structured and minimal

Send entity, customer identifiers, line items, currency, tax, payment terms and references. Do not send free-text notes as business data. Every field in the payload should have an owner and a validation rule.

Handle failure like an engineer

Queue and retry with backoff, idempotency keys so a retry cannot double-create an invoice, dead-letter storage for records that fail validation, and an alert to a human when the queue grows. Silent integration failure is worse than no integration.

Give sales read-only visibility

Show invoice number, status, due date and payment status on the deal or company record. Read-only. This one change removes most of the internal email traffic between sales and finance.

Reporting that requires both systems

Revenue recognised vs closed-won, days sales outstanding by customer segment, margin by product line and by sales owner, repeat purchase rate. These reports are the actual business case for the integration.

Governance after go-live

Any new field in either system needs a decision: sync, ignore, or derive. Review the mapping quarterly. An integration without governance turns into two divergent databases within a year.