Migrate from CDK Global to Twenty CRM

CDK Person records (customers, leads, service clients) map directly to Twenty Person records. CDK Person records sometimes carry multiple role types per individual — a person can be a sales prospect, a service customer, and an F&I client simultaneously. We map them to a single Person record in Twenty and attach role context via a custom role field if needed. Owner resolved by email match to Twenty workspace members.

CDK Company records (franchised dealerships, OEM entities) map to Twenty Company records. CDK Company hierarchies (parent franchise / child dealership) map to the Twenty Company ParentId field. Multi-dealership CDK setups with separate Company records per location collapse to individual Twenty Company records; we add a custom Dealership field for cross-location filtering if needed.

CDK Deal records — representing vehicle sale or lease transactions — map to Twenty Opportunity records. The deal name, amount, close date, and stage all transfer directly. CDK lifecycle stage values map to Twenty's Opportunity stage field via a value-mapping table, and the original CDK stage name is preserved in a custom field for reporting continuity.

Vehicle is a core data entity in CDK (stock number, VIN, make, model, year, mileage, acquisition cost, status) but has no standard equivalent in Twenty. We create a Vehicle custom object in Twenty with fields matching CDK's vehicle record schema. Vehicle records link to their owning Person records via a VehicleOwner junction field on the Person object, since Twenty's custom objects do not support native junction tables between two custom objects.

F&I products are line-item records in CDK linked to deals — product type (GAP, extended warranty, paint protection), provider name, cost, and menu position. Twenty has no standard F&I object. We create an F&I Product custom object with fields for product type, provider, cost, menu position, and a lookup to the related Opportunity. CDK's F&I menu configuration (menu structure, provider settings, markup rules) does not migrate — we export it as a reference document for manual rebuild in Twenty.

Service records in CDK are tied to VIN and repair order (RO) number — they include service advisor, RO status, service type, open/close dates, and labor/parts costs. Twenty's standard Notes and Tasks objects cannot represent this automotive-specific structure. We create a Service Record custom object with all service fields and a link to the Vehicle custom object via a custom vehicle ID field.

CDK tracks parts orders for the service department — order number, part number, description, quantity, cost, and status. This has no standard equivalent in Twenty. We create a Parts Order custom object and link it to the related Service Record via a custom field. Dealers who rely on parts order history for service analytics will have that data available in Twenty after migration.

CDK notes and attachments on Person, Company, Deal, or Vehicle records migrate to Twenty Note records. File attachments are re-uploaded to Twenty's file storage. Original timestamps and creating user IDs are preserved. Inline images in notes are extracted and rehosted in Twenty's media storage.

CDK tasks (follow-ups, reminders, service appointments) map to Twenty Task records. Original due dates, assignees, and completion status transfer directly. Open tasks active at cutover are included in the delta pickup window so nothing slips through during the transition period.

CDK users assigned as record owners are resolved by email matching against Twenty workspace members. Unmatched owners are flagged before migration begins — your team either invites them to Twenty first or assigns their records to a designated fallback owner. No record lands in Twenty without a resolved owner.

CDK custom objects created by a dealership (beyond the standard CDK modules) map 1:1 to Twenty custom objects. Custom field data types are matched to Twenty field types (text, number, date, select, multi-select, relation, etc.). N:N relationships in CDK custom objects that use junction records require explicit junction objects in Twenty — we surface this in the migration plan before data lands.