Migrate from CDK Global to Pipedrive

CDK customer records (name, email, phone, address) map directly to Pipedrive Person. CDK customers with no vehicle association land as standalone Persons. Customers with linked vehicles have vehicle properties migrated as custom fields on the Person record, preserving the customer-to-vehicle relationship from CDK. The original CDK customer ID is stored as a custom field for reconciliation.

CDK customers flagged as business accounts or buy-here-pay-here lots map to Pipedrive Organization. Organization fields (name, website, industry) receive direct values where present in CDK; otherwise they are created from customer data and flagged for enrichment. Commercial accounts maintain their CDK dealer ID as a reference field to support post-migration validation against source records.

CDK vehicle records (VIN, year, make, model, trim, mileage, condition grade, stock number) have no Pipedrive native equivalent. We create Pipedrive custom fields on the linked Person record (vehicle properties) and on the associated Deal record (trade vehicle details). The vehicle-to-customer linkage is preserved as a custom field value.

CDK deal records (deal amount, stage, close date, sales person) map to Pipedrive Deal. CDK deal stage names are mapped value-by-value to Pipedrive stage names within the target pipeline. The vehicle and trade linked to the CDK deal are preserved as custom fields on the Pipedrive Deal.

CDK trade-in records (trade VIN, trade value, NADA value, payoff amount) have no Pipedrive equivalent. These migrate as a set of custom fields on the associated Pipedrive Deal: Trade_VIN__c, Trade_Value__c, Trade_NADA_Value__c, Trade_Payoff__c. The net trade equity calculates from these values as an additional custom field.

CDK F&I products (GAP, credit life, tire & wheel, paint protection, etching) are modeled as Pipedrive Products for catalog purposes, linked to the deal via deal_products entries. Provider, cost, selling price, and reserve rate for each F&I product migrate as custom fields on the Pipedrive Product record since Pipedrive's native product fields do not capture F&I-specific pricing tiers.

CDK finance terms (APR, term, lender, finance reserve, buy rate, sell rate, monthly payment) have no Pipedrive native equivalent. These migrate as custom fields on the Pipedrive Deal: Finance_APR__c, Finance_Term__c, Finance_Lender__c, Finance_Reserve__c, Finance_Monthly_Payment__c. Dealerships use these fields for F&I audit and compliance review.

CDK service repair orders (RO number, service type, open/closed status, labor hours, labor rate, parts lines, technician, advisor) are modeled as Pipedrive Activities tied to the Person record. Open ROs create open Pipedrive Activities with due dates; closed ROs create completed Activities with original completion dates. Parts lines and labor breakdowns are preserved as Activity notes.

CDK parts inventory records (part number, description, cost, list price, bin location, on-hand quantity, reorder point) have no Pipedrive equivalent. Parts data is exported as a CSV reference file for manual use or for integration into a separate inventory management tool. It is not imported into Pipedrive's CRM layer.

CDK internet leads and raw sales leads without a closed deal map to Pipedrive Lead. Pipedrive's Lead object is separate from Person and supports early-funnel tracking. Source attribution (lead source, campaign name) from CDK is preserved as custom fields on the Pipedrive Lead. Leads convert to Persons and Deals when they progress in Pipedrive's workflow.

CDK employee records are matched to Pipedrive Users by email address. CDK user records without an email address in the DMS are flagged for manual Pipedrive user creation before migration. CDK role and department assignments (sales, finance manager, service advisor) are preserved as custom fields on the Pipedrive User record.

CDK documents attached to deals or customers (credit applications, NADA reports, service invoices) are downloaded and re-uploaded as file attachments to the corresponding Pipedrive Activity or Person record. File size limits from Pipedrive apply (25MB per file). Inline images in service notes are extracted and hosted as separate attachments.