Migrate from CDK Global to HubSpot

CDK customer records map to HubSpot contacts. HubSpot contacts do not have a native vehicle field — vehicle data links via the Vehicle custom object with junction associations. CDK customer address fields (street, city, state, postal code, country) map to HubSpot contact address properties directly.

CDK stores customer addresses as a separate sub-object (street, city, state, postal code, country). HubSpot contact records hold address fields directly on the contact. FlitStack merges CDK address fields into the contact record during migration. CDK address lat/long coordinates are not portable to HubSpot.

HubSpot has no native vehicle object. CDK vehicle records (VIN, make, model, year, color, mileage, stock number, sale price) migrate into a Vehicle__c custom object. Each vehicle record is associated to the contact record via HubSpot's association API. Vehicle status (available, sold, in-service) maps to a Vehicle_Status__c custom pick-list.

CDK lot management tracks vehicle inventory as a separate object from customer records. For unsold inventory, vehicle records migrate to Vehicle__c with status='Available' and no contact link. When a vehicle sells, the corresponding deal record in HubSpot links to the Vehicle__c record via a Vehicle_Reference__c lookup field. Dealerships choosing not to track lot inventory in HubSpot can omit unsold vehicle records.

CDK deal records (deal name, deal amount, deal stage, close date) map to HubSpot deals. CDK deal stage names do not automatically match HubSpot pipeline stages — value-by-value stage mapping is required. CDK deal notes field maps to the HubSpot deal notes field. Deal owner resolves by email match to a HubSpot user.

CDK F&I products (GAP coverage, tire protection, paint protection, service contracts, warranties) are stored as separate line items linked to the deal. HubSpot deals have no F&I line-item model — product name, provider, term length, and cost map to custom fields on the deal record: F_I_Product__c, F_I_Provider__c, F_I_Term_Months__c.

CDK repair orders map to HubSpot tickets. CDK RO number becomes a custom Ticket field (CDK_RO_Number__c). CDK service advisor resolves to a HubSpot user by email — they become the ticket owner. CDK RO status (open, in-progress, invoiced) maps to HubSpot ticket pipeline stages. Parts and labor line items from the RO become ticket conversation notes.

CDK owner IDs on records (salesperson, service advisor, F&I manager) resolve by email match against HubSpot users. FlitStack flags any CDK owner without a matching HubSpot user before migration — the team either creates HubSpot users first or assigns those records to a fallback owner. No record lands in HubSpot without a resolved owner.

CDK user records (name, email, role) map to HubSpot user records. CDK role types (salesperson, service advisor, F&I manager) do not map to HubSpot built-in roles — FlitStack preserves role as a custom User field (CDK_Role__c) for reference. User must exist in HubSpot before records referencing them are migrated.

CDK parts inventory records (part number, description, price, quantity on hand) can map to HubSpot products if the dealership uses HubSpot's product catalog for parts tracking. For parts-only dealerships not using HubSpot products, parts data migrates as a custom object linked to the contact or repair order.

Multi-location CDK dealerships (separate rooftops) can map to HubSpot companies if each location is treated as a separate business account. CDK location code and address map to HubSpot company name and address fields. Alternatively, dealership name and location can be stored as a custom field on contact records for single-rooftop migrations.

CDK records test drive logs, deal conversations, and F&I presentations as engagement activities. CDK activity records with type, date, and notes map to HubSpot engagements on the contact record — calls, emails, and meetings. Original activity timestamps are preserved on the HubSpot engagement record.