CRM migration
Field-level mapping, validation, and rollback between CDK Global and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
CDK Global
Source
Salesforce Sales Cloud
Destination
Compatibility
11 of 11
objects map 1:1 between CDK Global and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
48–72 hours
Overview
CDK Global structures its data around the dealership as a business unit: customers are tied to vehicles, vehicles carry service histories and F&I product attachments, and deals are finalized within CDK's finance-and-insurance module. Salesforce Sales Cloud models customers and vehicles as separate objects (Account/Contact and Asset), F&I products as Opportunity Products with a PricebookEntry, and service as Cases. The migration must therefore re-home CDK's customer-vehicle associations into Salesforce's Account-Contact-Asset relationship graph, decompose CDK F&I multi-product deals into Salesforce Opportunity Products, and surface automotive-specific fields (VIN, trade-in value, date-of-loss) as custom fields on the Account or Opportunity record. We access CDK through the Fortellis Data Extract API bundle, which provides structured exports of customer, vehicle, deal, and service datasets. The export runs on a scheduled SFTP delivery or on-demand API call, producing CSV or JSON payloads that feed our field-mapping engine. For large multi-rooftop CDK environments, we extract per-dealership and merge at the Salesforce end using the dealership ID as a custom field for territory segmentation. CDK workflows — service-reminder rules, lead-assignment triggers, and F&I product rules — are not exported by the CDK API and do not migrate. We document every CDK workflow definition as a rebuild reference for your Salesforce admin or a Flow consultant. The same applies to CDK's email templates, form templates, and DMS configuration. These must be recreated in Salesforce or documented separately as a configuration migration project.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a CDK Global object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
CDK Global
CDK Customer (Contact)
Salesforce Sales Cloud
Account + Contact
1:1CDK stores customer name, address, and contact info on one record. Salesforce separates Account (organization or individual entity) from Contact (person). We map CDK customer fields to both objects: Account holds the legal name and address; Contact holds first name, last name, email, and phone. For individual customers without a company, the Account name mirrors the Contact last name.
CDK Global
CDK Vehicle
Salesforce Sales Cloud
Asset
1:1CDK vehicles map directly to Salesforce Asset. The Asset object carries VIN (stored as Name or a custom VIN__c field), make, model, year, stock number, vehicle status (new/used/available/pending/sold), and a lookup to the Account representing the customer or dealership lot. Original service history attaches to the Asset as related Cases.
CDK Global
CDK F&I Deal Header
Salesforce Sales Cloud
Opportunity
1:1CDK deal header — deal amount, deal term, APR, deal status, deal date, and finance source — maps to Salesforce Opportunity fields (Amount, StageName, CloseDate). The CDK deal status (pending/approved/funded) maps to a custom Opportunity Stage value set. Unfunded deals land as early-stage Opportunities; funded deals close-won.
CDK Global
CDK F&I Product Line (GAP, etch, warranty, maintenance)
Salesforce Sales Cloud
OpportunityLineItem + PricebookEntry
1:1Each CDK F&I product line becomes a Salesforce OpportunityLineItem on the related Opportunity. A PricebookEntry must exist for every F&I product SKU — we create a 'CDK F&I Products' Pricebook with entries for every product type found in the CDK deal export. Product cost and MSRP map from CDK product pricing fields.
CDK Global
CDK Trade-In Vehicle
Salesforce Sales Cloud
Asset + custom field on Opportunity
1:1Trade-in vehicles from CDK map to a separate Asset record (owned by the dealership or customer Account) and also to Opportunity-level custom fields (Trade_In_Vehicle__c, Trade_In_Value__c) for reporting continuity in Salesforce. Trade-in VIN and mileage are captured on the Asset; the dollar value appears on the Opportunity.
CDK Global
CDK Service Repair Order (RO)
Salesforce Sales Cloud
Case
1:1CDK service tickets map to Salesforce Case. The RO number becomes CaseNumber or a custom RO_Number__c field. Technician name, labor hours, labor rate, and parts lines are custom fields on the Case object (Technician__c, Labor_Hours__c, Labor_Rate__c). Parts used are stored as Case Line Items or custom CaseProduct__c records depending on your Salesforce configuration.
CDK Global
CDK Parts Inventory
Salesforce Sales Cloud
Product2 + custom inventory fields
1:1CDK parts catalog items map to Salesforce Product2 records. CDK stock quantity, bin location, reorder point, and cost map as custom fields on Product2 (Qty_In_Stock__c, Bin_Location__c, Reorder_Point__c). Actual inventory counts in real-time are not native Salesforce; we surface them as custom read-only fields updated via a scheduled integration if needed.
CDK Global
CDK Lead / Prospect
Salesforce Sales Cloud
Lead
1:1CDK prospects and internet leads with status 'new', 'contacted', 'pending' map directly to Salesforce Lead records. Lead Source, Lead Status, and any CDK lead scoring fields migrate as custom fields. Converted leads route to Account/Contact/Opportunity using Salesforce's standard lead conversion.
CDK Global
CDK Activity (calls, emails, notes)
Salesforce Sales Cloud
Task + Event + Note
1:1CDK logged calls map to Salesforce Task with Type='Call'; emails map to Task with Type='Email'; appointments map to Event with original start/end times and owners preserved. CDK free-form notes map to Salesforce Note or ContentNote (rich text). All activity parents link to the corresponding Account or Contact record.
CDK Global
CDK Custom Fields (OEM codes, program flags, user-defined fields)
Salesforce Sales Cloud
Custom fields (__c) on respective objects
1:1CDK's user-defined fields and OEM program codes have no Salesforce equivalents. We create custom fields on the relevant object (Account, Asset, Opportunity, Case) for each CDK custom property, preserving data type (text, number, date, picklist). Custom field names follow Salesforce __c convention; picklist values are re-created in Salesforce Setup.
CDK Global
CDK Accounting Transactions
Salesforce Sales Cloud
Custom fields on Opportunity + reporting only
1:1CDK's DMS accounting module (profit-per-vehicle, F&I per-copy, service absorption) is a general-ledger system with no direct Salesforce equivalent. We migrate the financial summary figures as read-only custom fields on the Opportunity record (F_I_Profit__c, Service_Revenue__c) for reporting continuity. Full accounting data should be handled by a dedicated ERP migration.
| CDK Global | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| CDK Customer (Contact) | Account + Contact1:1 | Fully supported | |
| CDK Vehicle | Asset1:1 | Fully supported | |
| CDK F&I Deal Header | Opportunity1:1 | Fully supported | |
| CDK F&I Product Line (GAP, etch, warranty, maintenance) | OpportunityLineItem + PricebookEntry1:1 | Fully supported | |
| CDK Trade-In Vehicle | Asset + custom field on Opportunity1:1 | Fully supported | |
| CDK Service Repair Order (RO) | Case1:1 | Fully supported | |
| CDK Parts Inventory | Product2 + custom inventory fields1:1 | Fully supported | |
| CDK Lead / Prospect | Lead1:1 | Fully supported | |
| CDK Activity (calls, emails, notes) | Task + Event + Note1:1 | Fully supported | |
| CDK Custom Fields (OEM codes, program flags, user-defined fields) | Custom fields (__c) on respective objects1:1 | Fully supported | |
| CDK Accounting Transactions | Custom fields on Opportunity + reporting only1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
CDK Global gotchas
CDK's 2024 ransomware outage sets migration precedent
Accounting records are migration-excluded by design
Deal/F&I bundle requires custom field mapping
Data Export Tool output requires transformation for non-CDK targets
Fortellis API rate limits are unpublished
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Extract and profile CDK data via Fortellis Data Extract API
FlitStack connects to your CDK instance via the Fortellis Data Extract API bundle or the scheduled SFTP data export, pulling structured CSV or JSON payloads for customers, vehicles, deals (with F&I product lines), service ROs, and parts. We run a data-profiling pass that identifies null rates per field, duplicate customer records, unmatched vehicle-to-customer links, and any F&I product codes not yet catalogued. This profile is shared with you before field mapping begins — it surfaces data-quality issues that need a business rule (e.g., which duplicate customer record wins) before migration.
Build the Salesforce F&I Pricebook and custom field schema
Before any data is loaded into Salesforce, we create the Pricebook and Product2 records for your F&I product catalog (each CDK F&I product becomes a Product2 with a PricebookEntry in your custom pricebook) and all custom automotive fields (VIN__c, Trade_In_Value__c, RO_Number__c, Term_Months__c, Backend_Rate__c, Vehicle_Status_CDK__c, etc.) on the relevant objects. This step runs in a Salesforce sandbox first; once validated, the same metadata deploys to your production org via a change-set or CI/CD pipeline.
Map, transform, and load customer and vehicle records first
CDK customer records load into Salesforce as Account + Contact pairs, with the CDK customer number preserved as CDK_Customer_ID__c on Contact for delta-run de-duplication. Vehicle records from CDK load as Asset objects linked to the parent Account, with VIN stored both as the Asset Name and as VIN__c for reporting queries. Because Salesforce requires Account to exist before Contact (via AccountId) and Asset to have an Account lookup, we sequence the migration: accounts first, contacts next, then assets. This ordering ensures every Contact and Asset has a valid parent Account at load time.
Migrate F&I deals with line-item products, then service records
CDK F&I deal headers load as Opportunities linked to the Account/Contact pair from step three. Each F&I product line on the CDK deal becomes an OpportunityLineItem with the correct PricebookEntry from the F&I Pricebook built in step two. Trade-in vehicles appear as separate Asset records linked to the Opportunity via a lookup. CDK service ROs then load as Cases linked to the Asset (for vehicle-related service) or the Account (for customer-level service). All parent-key relationships are validated before committing — any Opportunity with a missing AccountId or any Case with a missing AssetId/AccountId is flagged and held for resolution.
Run a sample migration with field-level diff and delta-pickup cutover
A representative slice — typically 200–500 records spanning customers, vehicles, deals with multiple F&I products, and service ROs — migrates into a Salesforce sandbox first. We generate a field-level diff comparing CDK source values against the Salesforce destination values for every mapped field, so you can verify that the F&I product count matches, RO totals landed correctly, and vehicle status translated as expected. After sign-off, the full migration runs against your production Salesforce org, followed by a 24–48 hour delta-pickup window that captures any CDK records modified during the cutover window. Audit log and one-click rollback are available for 72 hours post-migration.
Platform deep dives
CDK Global
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across CDK Global and Salesforce Sales Cloud.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
CDK Global: Not publicly documented by CDK.
Data volume sensitivity
CDK Global exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during CDK Global to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your CDK Global to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave CDK Global
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.