CRM and CDP integration guide

CRM–CDP connections must preserve lead activity, identity, consent, audience and activation state without turning the CDP into an uncontrolled second CRM.

Start with CRM & sales enablement, Customer data platforms (CDP), Data integration & middleware. The exact stack depends on the dealer’s OEMs, market, rooftops, current systems and operating model.

Require the provider to demonstrate: Identity and system-of-record rules Activity and status scope Audience write-back Suppression and deletion Use representative dealer records and include exceptions, not only the ideal path.

Identify every system that creates, reads or changes the same customer, vehicle, deal, repair-order, payment or marketing record. Confirm products, fields, direction, timing, fees and support on both sides.

Compare the same rooftops, users, volumes, modules and term. Include implementation, migration, hardware, usage, communications, data, integrations, annual increases and offboarding.

Document routine access, exports, identifiers, history, attachments, retention, deletion and transition assistance. Test a representative export before depending on it.

Identify scope, dependencies, service responsibilities, change rights, renewal, increases, suspension, termination and exit obligations for qualified dealer and professional review.

Choose a baseline, operational outcome, quality guardrail and adoption measure before launch. Reconcile reported results to source systems and disclose exclusions.