CRM migration
Field-level mapping, validation, and rollback between CDK Global and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
CDK Global
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between CDK Global and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
CDK Global is a dealer management system (DMS) that bundles CRM, inventory, F&I, service, and accounting into a single platform used by franchise and independent dealerships across North America. Its data model covers Customers (contacts), Vehicles (inventory), Deals (sales transactions), Service Records, Parts Inventory, and User/Owner records. CDK does not publish a public API for third-party data extraction, but its Data Export Tools expose SFTP-based exports of predefined datasets including customer, sales, service, and parts data. Nutshell is an SMB-focused CRM with a flat object model: People (contacts), Companies (accounts), Leads, Deals (pipeline opportunities), and Activities (tasks, calls, emails). Nutshell's API uses JSON-RPC over HTTPS with Basic authentication, supporting CRUD operations on all standard objects plus custom fields. We map CDK Customers to Nutshell People and Companies, CDK Deals to Nutshell Deals, and CDK Vehicle records to Nutshell custom fields on the Deal object. Service records and parts data become custom fields or notes in Nutshell since it has no native service-management object. CDK's user/owner list is resolved by email match against Nutshell users. We extract via CDK's SFTP export bundles, validate field coverage, then import into Nutshell via its JSON-RPC API. A 24–48 hour delta-pickup window captures any CDK records modified during cutover before the go-live sync commits.
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 Nutshell, 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)
Nutshell
Nutshell Person
1:1CDK stores customer name, phone, email, address, and owner as a Customer record. Nutshell's Person object holds the same fields. We map CDK Customer fields directly to Nutshell Person fields, with the CDK customer ID preserved as a custom field for reference and delta-run de-duplication.
CDK Global
CDK Customer Company / Dealer
Nutshell
Nutshell Company
1:1CDK links customers to a dealership or parent company. In Nutshell this maps to the Company object. For franchise dealers with a parent organization, we map CDK's parent company link to the Nutshell Company parent field. Multi-location CDK setups may produce multiple Nutshell Companies per franchise entity.
CDK Global
CDK Deal / Deal Jacket
Nutshell
Nutshell Deal
1:1CDK Deal records contain the vehicle being sold, sale price, F&I products selected, backend reserve, and deal status (pending, booked, finalized). Nutshell Deals hold the deal name, value, pipeline stage, and close date. We map CDK deal status to Nutshell Deal stage and preserve the total deal value and backend gross as custom fields on the Nutshell Deal.
CDK Global
CDK Vehicle (Inventory Unit)
Nutshell
Nutshell Deal — custom fields
1:1CDK's Vehicle object stores VIN, stock number, year, make, model, trim, color, mileage, and retail price. Nutshell has no native vehicle object, so we create custom fields on the Nutshell Deal record to store VIN, stock number, year/make/model, and mileage. The Nutshell Deal becomes the vehicle-sale record.
CDK Global
CDK F&I Products (GAP, Tire, Service Contract)
Nutshell
Nutshell Deal — custom fields
1:1CDK F&I module tracks backend products sold with each deal, including product name, provider, price, and reserve amount. Since Nutshell has no F&I module, we create custom text or currency fields on the Nutshell Deal to record each F&I product and its backend value. Product names are value-mapped if multiple CDK F&I product types need distinct Nutshell fields.
CDK Global
CDK Service Record (Repair Order)
Nutshell
Nutshell Person / Company — notes or custom fields
1:1CDK Fixed Operations stores service appointments, RO numbers, vehicle mileage at service, and parts used. Nutshell has no service module. We attach service history as formatted notes on the Nutshell Person or Company record linked to the vehicle. For high-volume service dealers, service records can be stored as custom long-text fields on the Company record.
CDK Global
CDK Parts Inventory
Nutshell
Nutshell — not migrated
1:1CDK parts inventory tracks bin locations, part numbers, pricing, and stock levels. Nutshell has no inventory management or parts module, so this data has no equivalent destination. We export the CDK parts data as a CSV file for the dealer's reference but do not import it into Nutshell. Dealers managing parts inventory separately retain that data outside Nutshell.
CDK Global
CDK User / Owner
Nutshell
Nutshell User
1:1CDK stores staff users with names, emails, roles, and location assignments. Nutshell's user model is email-based. We resolve CDK users to Nutshell users by email match. Unmatched CDK users are flagged before migration; the dealer either creates Nutshell accounts for them or reassigns their records to an existing user before the import runs.
CDK Global
CDK Activity (calls, emails, notes)
Nutshell
Nutshell Activity
1:1CDK logs phone calls, emails, and notes against customer and deal records. These map directly to Nutshell's Activity records (calls, emails, notes) with the original timestamp and owning user preserved. Activities are linked to the migrated Person or Deal record by cross-referencing the CDK record IDs stored as custom fields.
CDK Global
CDK Lead (unsold prospect)
Nutshell
Nutshell Lead
1:1CDK tracks unsold prospects and internet leads separately from closed deals. Nutshell has a native Lead object for people not yet converted to Contacts. We map CDK lead records to Nutshell Leads, preserving the lead source, interest level, and last-contact date as standard Nutshell Lead fields.
CDK Global
CDK Accounting / Finance Ledger
Nutshell
Nutshell — not migrated
1:1CDK's accounting module holds the general ledger, accounts payable, and financial reporting for the dealership. Nutshell is a CRM with no accounting module. Financial data remains in CDK or migrates separately to an accounting tool. We do not move CDK accounting data into Nutshell.
CDK Global
CDK Attachment / Document
Nutshell
Nutshell File Attachment
1:1CDK stores deal jackets, contracts, and F&I forms as attachments on deals. Nutshell supports file attachments on Deals, People, and Companies. We re-upload CDK deal attachments to the corresponding Nutshell Deal record. File size limits apply — attachments over Nutshell's upload limit are flagged for manual retrieval from CDK.
| CDK Global | Nutshell | Compatibility | |
|---|---|---|---|
| CDK Customer (Contact) | Nutshell Person1:1 | Fully supported | |
| CDK Customer Company / Dealer | Nutshell Company1:1 | Fully supported | |
| CDK Deal / Deal Jacket | Nutshell Deal1:1 | Fully supported | |
| CDK Vehicle (Inventory Unit) | Nutshell Deal — custom fields1:1 | Fully supported | |
| CDK F&I Products (GAP, Tire, Service Contract) | Nutshell Deal — custom fields1:1 | Fully supported | |
| CDK Service Record (Repair Order) | Nutshell Person / Company — notes or custom fields1:1 | Fully supported | |
| CDK Parts Inventory | Nutshell — not migrated1:1 | Fully supported | |
| CDK User / Owner | Nutshell User1:1 | Fully supported | |
| CDK Activity (calls, emails, notes) | Nutshell Activity1:1 | Fully supported | |
| CDK Lead (unsold prospect) | Nutshell Lead1:1 | Fully supported | |
| CDK Accounting / Finance Ledger | Nutshell — not migrated1:1 | Fully supported | |
| CDK Attachment / Document | Nutshell File Attachment1: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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Inventory CDK data exports and align export schedule with migration window
Before any mapping work begins, we identify which CDK Data Export Tool bundles are available on your CDK plan (Customer, Vehicle, Deal, Service, Parts, Accounting). We request an on-demand export trigger to capture the current state of all data rather than waiting for the next scheduled SFTP delivery. We validate that the export files contain the fields needed for the Nutshell field mapping plan. If any required fields are missing from the standard CDK bundles, we flag those gaps and recommend a supplemental manual export. This step also confirms the CDK user list that will be mapped to Nutshell users by email.
Create Nutshell custom fields for vehicle and F&I data
Based on the CDK field inventory, we deliver a step-by-step checklist of custom fields to create in your Nutshell account before data import begins. This includes text fields for VIN, stock number, vehicle year/make/model/trim/color, mileage, and F&I product slots; currency fields for F&I product prices and backend reserves; and a text field for the CDK deal ID reference. We recommend creating these fields during the planning phase so the Nutshell schema is ready when the migration validation run executes. If your CDK setup includes more F&I products than the standard five slots, we discuss the overflow strategy (additional fields vs. notes format) before the migration runs.
Resolve CDK users to Nutshell users by email match
CDK stores staff users (salespeople, finance managers, service advisors, admins) with names and email addresses. Nutshell's user model is email-based. We extract the CDK user list, match each CDK owner email to a corresponding Nutshell user account by email address, and generate a mapping table. CDK users without a matching Nutshell account are flagged in a pre-migration report. The dealer's Nutshell admin creates accounts for those users or assigns their records to a fallback owner before the import run. This step prevents records from landing in Nutshell with an unassigned owner.
Run a sample migration of 100–500 CDK records with field-level diff
We run a representative slice of CDK data (customers, companies, deals, vehicles, activities) into the Nutshell account and generate a field-level diff showing what was mapped, what was transformed, and what was written to custom fields. The diff is reviewed by the dealer's admin to verify vehicle field mapping, F&I product mapping, and deal stage alignment before the full migration commits. Any field mapping errors identified in the sample are corrected before the full run. This step also confirms the multi-location strategy (separate Nutshell accounts vs. single account with location tags) is configured correctly.
Execute full migration with delta-pickup and audit log
The full CDK dataset migrates into Nutshell: People from CDK Customers, Companies from CDK Dealer records, Deals from CDK Deal jackets (with vehicle custom fields and F&I product fields populated), Leads from CDK Prospects, and Activities linked to their parent records. After the initial load, a 24–48 hour delta-pickup window captures any CDK records created or modified after the export snapshot. All operations are logged in an audit trail. A one-click rollback to the pre-migration Nutshell state is available if reconciliation reveals data integrity issues. After go-live, the dealer runs a parallel-read period in CDK for 48 hours to confirm no in-flight deals were missed before decommissioning the CDK connection.
Platform deep dives
CDK Global
Source
Strengths
Weaknesses
Nutshell
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 Nutshell.
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 Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your CDK Global to Nutshell 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 Nutshell
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.