CRM migration

Migrate from CDK Global to Nutshell

Field-level mapping, validation, and rollback between CDK Global and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

CDK Global logo

CDK Global

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between CDK Global and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How CDK Global objects map to Nutshell

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)

maps to

Nutshell

Nutshell Person

1:1
Fully supported

CDK 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

maps to

Nutshell

Nutshell Company

1:1
Fully supported

CDK 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

maps to

Nutshell

Nutshell Deal

1:1
Fully supported

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

maps to

Nutshell

Nutshell Deal — custom fields

1:1
Fully supported

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

maps to

Nutshell

Nutshell Deal — custom fields

1:1
Fully supported

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

maps to

Nutshell

Nutshell Person / Company — notes or custom fields

1:1
Fully supported

CDK 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

maps to

Nutshell

Nutshell — not migrated

1:1
Fully supported

CDK 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

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

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

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

maps to

Nutshell

Nutshell Lead

1:1
Fully supported

CDK 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

maps to

Nutshell

Nutshell — not migrated

1:1
Fully supported

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

maps to

Nutshell

Nutshell File Attachment

1:1
Fully supported

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

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • CDK Data Export Tools use SFTP batches, not a real-time API — export scheduling affects migration timing

    CDK Global does not expose a real-time REST or GraphQL API for live data extraction. Instead, CDK's Data Export Tools deliver predefined data bundles to an SFTP folder on a scheduled basis (daily by default). This means the export window must be aligned with the migration window — if the last CDK export ran before the migration cutover, recent deals or service records created after that export may not be captured. We address this by requesting an on-demand export trigger from CDK (if available for your plan) and running a supplemental delta export before committing the full migration load to Nutshell. Dealers on CDK's lower tiers without SFTP export access may need manual CSV exports, which extend the timeline.

  • Vehicle and F&I data require custom field creation in Nutshell before data can be imported

    CDK's DMS data model includes vehicle inventory units (VIN, stock number, make/model/year, mileage) and an F&I product module (GAP, tire protection, service contracts, backend reserves) that have no equivalent in Nutshell's CRM object model. Nutshell's standard Deal object has no vehicle-specific fields. Before CDK data can land in Nutshell, custom fields for VIN, stock number, vehicle year/make/model/mileage/color, and up to five F&I product slots (product name, price, backend reserve) must be created in Nutshell's field management UI. We deliver a custom field creation checklist before the migration runs so the Nutshell account is field-ready. If your CDK setup uses more than five F&I products per deal, additional fields or a notes-based approach is needed.

  • CDK multi-location dealer groups map to multiple Nutshell accounts or require location tagging

    CDK Global is commonly deployed across multi-location dealership groups where one DMS instance manages several franchise or independent locations. Nutshell's standard account model does not have a native multi-location or multi-entity hierarchy. Dealers migrating from CDK with multiple locations have two options: create a separate Nutshell account per location (each with its own user seats and pipeline), or consolidate into a single Nutshell account and use custom fields or tags to distinguish locations. We surface this decision early because it affects user-seat billing, pipeline configuration, and reporting. The choice is made by the dealer's admin before migration validation begins.

  • CDK parts inventory and accounting data have no Nutshell destination — those modules must be retired separately

    CDK's Fixed Operations module tracks parts inventory with bin locations, part numbers, and reorder points. CDK's accounting module holds the general ledger, accounts payable, and financial reporting for the dealership. Nutshell is a CRM with no inventory, parts, or accounting capabilities. These datasets are not migrated into Nutshell because they have no home object. We export CDK parts and accounting data as CSV files for the dealer's reference and recommend a separate migration path to a dedicated inventory or accounting tool. Failing to address this upfront means the dealer may lose access to historical parts cost data and financial reports after CDK is decommissioned.

  • CDK service records and repair orders migrate as notes, losing structured field relationships

    CDK Fixed Operations stores repair orders (RO) with structured fields: RO number, vehicle at service, service advisor, labor hours, parts used, and total RO value. Nutshell has no service module and no structured repair-order object. We attach service history to the Nutshell Person or Company record as formatted notes or custom long-text fields. The structured relationship between RO number, advisor, and parts used is flattened into a text block. For dealerships that rely on service history for customer retention and service bay utilization reporting, this loss of structure in Nutshell means service analytics must be rebuilt using a separate reporting tool or a dedicated fixed-ops platform.

Migration approach

Six steps for a successful CDK Global to Nutshell data migration

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

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

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

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

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

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.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

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

  • 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 Nutshell 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 Nutshell data migrations

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

Can't find your answer?

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 consultation

Most CDK Global to Nutshell migrations complete in 48–72 hours of clock time for datasets under 10,000 customer records with standard export bundles. Large dealership groups with 50,000+ records, multiple franchise locations, and extensive F&I product fields extend to 2–4 weeks. The longest planning step is aligning CDK's SFTP export schedule with the migration window and creating Nutshell custom fields for vehicle and F&I data before the import runs.

Adjacent paths

Related migrations to explore

Ready when you are

Move from CDK Global.
Land in Nutshell, 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