CRM migration

Migrate from CDK Global to Salesforce Sales Cloud

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 logo

CDK Global

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

100%

11 of 11

objects map 1:1 between CDK Global and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

CDK Global logo

CDK Global

What's pushing teams away

  • The 2024 ransomware breach caused a multi-week outage across CDK's entire dealer base, with significant revenue loss and manual-recovery labor that has dealerships actively evaluating alternatives.
  • CDK charges premium implementation fees (~$10,000) and opaque monthly licensing that many mid-market dealers describe as expensive for the value delivered.
  • Users consistently report CDK runs slowly and suffers random save errors that interrupt customer contracting and deal-closing workflows.
  • Switching DMS providers is architecturally disruptive because CDK stores deeply integrated relationships between vehicles, customers, repair orders, and F&I products that don't export cleanly.
  • Limited pricing transparency and a complex partner-billing model make it difficult for dealers to predict total cost of ownership before committing.

Choosing

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How CDK Global objects map to Salesforce Sales Cloud

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)

maps to

Salesforce Sales Cloud

Account + Contact

1:1
Fully supported

CDK 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

maps to

Salesforce Sales Cloud

Asset

1:1
Fully supported

CDK 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

maps to

Salesforce Sales Cloud

Opportunity

1:1
Fully supported

CDK 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)

maps to

Salesforce Sales Cloud

OpportunityLineItem + PricebookEntry

1:1
Fully supported

Each 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

maps to

Salesforce Sales Cloud

Asset + custom field on Opportunity

1:1
Fully supported

Trade-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)

maps to

Salesforce Sales Cloud

Case

1:1
Fully supported

CDK 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

maps to

Salesforce Sales Cloud

Product2 + custom inventory fields

1:1
Fully supported

CDK 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

maps to

Salesforce Sales Cloud

Lead

1:1
Fully supported

CDK 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)

maps to

Salesforce Sales Cloud

Task + Event + Note

1:1
Fully supported

CDK 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)

maps to

Salesforce Sales Cloud

Custom fields (__c) on respective objects

1:1
Fully supported

CDK'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

maps to

Salesforce Sales Cloud

Custom fields on Opportunity + reporting only

1:1
Fully supported

CDK'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.

Gotchas + challenges

What specifically takes care here

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 logo

CDK Global gotchas

High

CDK's 2024 ransomware outage sets migration precedent

High

Accounting records are migration-excluded by design

Medium

Deal/F&I bundle requires custom field mapping

Medium

Data Export Tool output requires transformation for non-CDK targets

Low

Fortellis API rate limits are unpublished

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • CDK F&I multi-product deals require a Salesforce Pricebook built from scratch

    CDK stores multiple F&I product lines (GAP, tire-and-wheel, maintenance contract, paint protection) on a single deal record. Salesforce OpportunityLineItems require a PricebookEntry for every product, which means you must define a 'CDK F&I Products' Pricebook and create a Product2 record + PricebookEntry for each product type found in your CDK deal export. If your CDK instance has 40 F&I product SKUs across three lenders, that translates to 40 PricebookEntries. Skipping this step means F&I backend products cannot be recorded in Salesforce at the line-item level and will collapse into the Opportunity Amount with no product-level detail.

  • CDK vehicle inventory status flags have no Salesforce native equivalent

    CDK tracks vehicle status with codes that include hold, recon, dealer-traded, loaner, and consignment — each driving different DMS workflows and reporting views. Salesforce Asset has a standard Status field with four values: Purchased, Shipped, Installed, Retired. None of CDK's automotive-specific vehicle states map cleanly to those four values. We create a custom pick-list field (Vehicle_Status_CDK__c) that preserves every CDK status flag as-is. If your reporting depends on filtering by CDK status (e.g., recon vehicles excluded from new-vehicle floorplan reporting), that logic must be rebuilt in Salesforce as a filter on the custom field — it will not happen automatically.

  • CDK service records carry RO-level financials that Salesforce Case does not aggregate

    CDK repair orders include posted labor, posted parts, sublet charges, and applicable taxes as fields on the RO record. Salesforce Case is a ticket object — it does not aggregate financial line items natively. A Case can have Description, Subject, and a small set of custom fields, but it has no Opportunity-style Amount field. We map CDK RO total to a custom currency field (RO_Total__c) on Case, but the RO line-item breakdown (which parts were used, which technicians billed) requires either Case Products (an add-on module) or a custom junction object. If your service absorption reporting depends on per-line-part revenue, that structure needs Salesforce admin configuration before the migration lands.

  • CDK workflows and F&I product rules do not export via the CDK API

    CDK encodes business rules — service-reminder emails, lead-assignment triggers, F&I product recommendation rules — within its DMS configuration layer. The CDK Fortellis Data Extract API and Data Export/Import Tool expose data records only; they do not export workflow definitions, conditional logic, or F&I product rules. We can export CDK's workflow descriptions as documentation for your Salesforce admin to rebuild in Flow or Process Builder, but the migration itself carries zero workflow logic. Any CDK rule that automatically adds a service reminder, flags a lead, or pre-selects a GAP product in a deal must be rebuilt from scratch in Salesforce.

  • Multi-rooftop CDK environments require dealership-level segmentation in Salesforce

    Groups running CDK across multiple franchises or rooftops typically store all locations in one CDK instance with a location identifier on each record. Salesforce's multi-entity model offers three paths: separate Business Units (requires Enterprise or Unlimited edition with Enhanced Domain), a custom Dealership__c field on every record used for filtering, or completely separate Salesforce orgs per rooftop. We add a Dealership_ID__c field to every migrated object as the universal segment key, but which Salesforce segmentation model your group adopts is a business decision that must be made before the full migration runs, as it affects how record sharing and page layouts are configured.

Migration approach

Six steps for a successful CDK Global to Salesforce Sales Cloud data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

CDK Global logo

CDK Global

Source

Strengths

  • $540B in annual dealer commerce managed through CDK systems, making it the most data-rich DMS in North America.
  • End-to-end stack covering front-office CRM, F&I, fixed operations, parts, and accounting in a single proprietary platform.
  • Fortellis API ecosystem with OAuth authentication and documented Get/Post/History/Async endpoints for vehicle, sales, service, parts, and customer data.
  • Tier IV data centers with PGP encryption and MFA on data exports, meeting FTC Safeguards Rule requirements.
  • CDK Data Export/Import Tool schedules predefined data sets to SFTP with PGP encryption at no additional license cost.

Weaknesses

  • Opaque pricing with no published tiers and implementation fees of $10,000+ create high switching costs that lock in mid-market dealers.
  • 2024 ransomware breach exposed CDK's systemic risk; a weeks-long outage forced dealerships into manual processes and revenue loss.
  • Performance complaints across G2 and SoftwareAdvice consistently cite slow response times and random save errors in production use.
  • Accounting module is deeply integrated and cannot be cleanly decoupled for export, complicating migrations to standalone CRMs.
  • High switching costs and complexity mean CDK migrations typically require weeks of discovery, custom mapping, and parallel-run validation.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across CDK Global and Salesforce Sales Cloud.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    CDK Global: Not publicly documented by CDK.

  • Data volume sensitivity

    A

    CDK Global exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your CDK Global to Salesforce Sales Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about CDK Global to Salesforce Sales Cloud data migrations

Answers to the questions buyers ask most during CDK Global to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most CDK-to-Salesforce migrations run 48–72 hours of clock time for environments under 50,000 total records across customers, vehicles, deals, and service ROs. Multi-rooftop environments with 500,000+ records or heavy F&I product complexity (30+ products across 5+ lenders) extend to 7–14 days. The longest planning step is building the F&I Pricebook schema in Salesforce before data loads — every F&I product SKU needs a Product2 and PricebookEntry, and that catalog must be complete before OpportunityLineItems can be inserted.

Adjacent paths

Related migrations to explore

Ready when you are

Move from CDK Global.
Land in Salesforce Sales Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day