Migrate from CDK Global to Odoo CRM

CDK customer records (name, email, phone, address) map directly to Odoo res.partner. CDK supports both individual buyers and business entities; the is_company flag on res.partner distinguishes them. CDK customer IDs are stored in a custom field (cdk_customer_id) on the partner for delta-run tracking.

CDK vehicle records (VIN, year, make, model, trim, stock number) have no direct Odoo CRM equivalent. We map VIN to a custom char field (x_vin) on res.partner and optionally create stock.vehicle records for dealerships that want full inventory tracking in Odoo Inventory app. The primary vehicle association is stored as x_primary_vehicle_vin on the contact.

CDK allows one customer to be linked to multiple vehicles (buyer of Vehicle A, co-signer on Vehicle B, previous owner of Vehicle C). Odoo res.partner is one record per person. We preserve the full vehicle-association history as a JSON field (x_vehicle_links) on the primary res.partner, with type, role, and dates per vehicle link. Dealerships can optionally split these into Account Contact Relationships if Odoo Enterprise.

CDK F&I deals track finance applications, approved products (GAP, wheel & tire, maintenance contracts), reserve amounts, and lender info. We map these to crm.lead with custom fields: x_fi_product_type (Selection), x_fi_reserve_amount (Monetary), x_fi_lender (Char), and x_fi_deal_number (Char). The lead name reflects the customer + vehicle. Product line items become sale.order.line after opportunity conversion.

CDK F&I product catalog entries map to Odoo product.product records. Each product type (GAP, tire protection, paint sealant) becomes a product with type=service. CDK product pricing maps to Odoo list_price. Products are linked to the crm.lead via x_fi_product_ids (Many2many) and materialize as sale.order.line after the opportunity converts to a quotation.

CDK service ROs are first-class records with RO number, vehicle, line items, technician, and close date. Odoo CRM has no native service RO object. We map RO data as activities on the linked crm.lead (log note with x_ro_number, x_ro_technician, x_ro_total), or as a separate crm.lead per RO with stage='Won' if the dealership wants full RO history visible as records. The mapping choice is confirmed during the pre-migration discovery call.

CDK leads and internet leads (from CDK CRM or third-party sites via CDK integration) map directly to Odoo crm.lead. Source of lead (website form, phone inquiry, walk-in) is preserved in x_lead_source. CDK lead status maps to crm.stage: New → New, Working → Qualified, Sold → Won, Lost → Lost. Probability is set per stage in Odoo's pipeline configuration.

CDK pipeline stages (Lead, App Started, Submitted, Funded, Booked) map to Odoo crm.stage records. Each stage gets a probability value matching the CDK close probability for accurate forecasting. New stages can be created in Odoo Settings → CRM → Stages before migration to match CDK's exact stage names.

CDK users (salespeople, F&I managers, service advisors) are matched to Odoo res.users by email address. CDK role (salesperson, finance director, service manager) maps to Odoo res.users groups: salesperson → Sales / User, manager → Sales / Manager. Unmatched CDK users are flagged as a pre-migration action item — the dealership must create Odoo user accounts before migration so owner fields resolve correctly.

CDK sold deals represent a finalized vehicle sale with customer, vehicle, F&I products, and payment details. We map the sold unit to a crm.lead in Won stage (preserving create date and close date) and optionally generate a sale.order for the F&I product bundle. The sale.order links the customer (res.partner), the product/services sold, and the salesperson (user_id).

CDK file attachments (credit applications, service invoices, vehicle photos) stored in CDK's document management export as files. We re-upload these to Odoo's ir.attachment table linked to the corresponding res.partner or crm.lead record. Odoo Cloud has a 115MB attachment limit per file; files larger than this are flagged for manual delivery.

CDK parts inventory records (part number, description, cost, list price, bin location) map to Odoo product.product with type=product for parts and type=service for labor. CDK bin location maps to x_bin_location (Char) as a custom field. Parts not intended for Odoo Inventory app (i.e., reference-only) are stored as x_cdk_part_number on the contact record.