CRM and ERP integration: designing the sync with SAP, Business Central or a custom system

Nearly every CRM project eventually meets the ERP. The integration fails not because of connectors but because nobody decided which system owns each field, what happens when both change, and who is alerted when a sync breaks silently. Designing ownership before choosing a tool is the difference between one clean interface and two years of reconciliation work.

Who asks this question

• Companies where sales and finance report different revenue numbers.
• Teams re-keying customer master data into two systems.
• IT owners inheriting a fragile point-to-point integration.

How to implement it

1. Write a field ownership matrix: for every shared field, name the system of truth and the direction of sync.
2. Keep the integration narrow at first: accounts, contacts, closed-won deals, invoice status. Resist syncing everything.
3. Choose the mechanism deliberately: native connector, iPaaS, or custom middleware, based on volume, latency and error visibility.
4. Design failure handling explicitly: retries, dead-letter queue, and an alert to a human who is accountable.
5. Run a reconciliation report weekly for the first quarter, comparing record counts and totals across both systems.

What to measure

• Sync error rate and mean time to detection.
• Number of fields with duplicated manual entry, which should trend to zero.
• Revenue reconciliation variance between CRM and ERP.
• Lead time to add a new synced field, a good proxy for architectural health.

Common mistakes

• Two-way syncing a field that both systems can edit, without conflict rules.
• Integrating before cleaning duplicate accounts, which multiplies the mess.
• Silent failures with no alerting, discovered at month-end close.
• Using the CRM as an ERP reporting tool instead of a commercial system.

Frequently asked questions

Native connector or custom integration?

Native connectors are the right default when field mapping fits. Custom middleware becomes worthwhile with complex transformations, high volumes or strict audit requirements.

Should the ERP or CRM own the customer master?

Usually the ERP for billing entities and the CRM for commercial relationships, linked by a stable external ID.

How long does a typical integration take?

A focused first phase is often three to six weeks; the timeline expands with custom fields, legacy data quality and approval cycles.

Piceci Services is a HubSpot Solutions Partner and ISO 27001 certified consultancy operating from Milan and Dubai. If you want this reviewed against your current setup, book a call and we will walk through it with your data.