CRM migration

Migrate from CDK Global to Freshsales

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

CDK Global logo

CDK Global

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

10 of 10

objects map 1:1 between CDK Global and Freshsales.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

CDK Global organizes data around vehicles, deals, and fixed operations; Freshsales uses the standard CRM triad of Contacts, Accounts, and Deals. Reorganizing CDK's customer, vehicle, service, and F&I data into Freshsales' model requires custom objects for automotive-specific records and value-mapping for CDK status fields that don't map to Freshsales lifecycle stages or deal stages. FlitStack AI extracts CDK data via the Fortellis API and CDK Data Export Tools, then sequences the migration so foreign keys resolve in the right order: Accounts first, then Contacts, then Deals with F&I line items, then custom object records for vehicles and service history. Workflows, automations, and CDK-specific DMS modules (parts inventory, service dispatch) have no Freshsales equivalent and must be rebuilt in Freshsales Workflows. Owner resolution runs by email match against Freshsales users; unresolved owners are flagged for manual assignment before the migration window closes. A delta-pickup window (typically 24–48 hours) captures any CDK records created or modified during cutover, ensuring the final Freshsales state matches the live CDK database at go‑live. An audit log records every insert, update, and link operation, and a one‑click rollback can revert the Freshsales tenant to its pre‑migration snapshot if reconciliation fails. All field transformations, custom pick‑list values, and lookup relationships are logged in a migration manifest for downstream reference.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How CDK Global objects map to Freshsales

Each row shows how a CDK Global object lands in Freshsales, 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

maps to

Freshsales

Contact

1:1
Fully supported

CDK customer records map directly to Freshsales Contacts. Address, phone, email, and owner fields translate field-for-field. Customers without a company affiliation land as standalone contacts with no AccountId. If a customer record includes a company link, we resolve that link to an AccountId after the Account has been created. All original timestamps and source IDs are preserved in custom fields for traceability.

CDK Global

CDK Customer Company Link

maps to

Freshsales

Account

1:1
Fully supported

CDK stores business/dealership affiliations as separate Company records. These map to Freshsales Accounts — name, address, website, industry, and employee count translate directly. Parent-company hierarchies in CDK collapse to a primary AccountId in Freshsales. When a parent-child hierarchy exists in CDK, we map the top-level company to the primary Account and link child companies as child Accounts, preserving the relationship if the target Freshsales plan supports it.

CDK Global

CDK Deal

maps to

Freshsales

Deal

1:1
Fully supported

CDK deal records map to Freshsales Deals with stage, amount, close date, and owner. CDK Deal Status values (Pending, Submitted, Funded, etc.) require value-mapping to Freshsales Deal Stage pick-list per pipeline. Deal owner resolves by email match to Freshsales users.

CDK Global

CDK Vehicle

maps to

Freshsales

Custom Object: Vehicle

1:1
Fully supported

VIN, make, model, year, trim, mileage, and color have no Freshsales native equivalent. We create a Vehicle custom object in Freshsales and link it to the Contact or Account via a lookup relationship. The original CDK Vehicle record ID is stored as Source_Vehicle_ID__c for traceability.

CDK Global

CDK Service Record

maps to

Freshsales

Custom Object: Service Record

1:1
Fully supported

RO number, service type, date, advisor, and description require a custom object. Service records link to the Vehicle custom object or the Contact/Account. Timestamps and advisor assignments are preserved; CDK service status values map to a custom pick-list in Freshsales.

CDK Global

CDK Deal F&I Product

maps to

Freshsales

Custom Object: Deal F&I Product

1:1
Fully supported

F&I product type, product name, price, term, and provider do not exist in Freshsales native model. A Deal F&I Product custom object is created with a lookup to the Freshsales Deal. F&I product types (GAP, Tire & Wheel, Paint Protection, Extended Service Contract) are value-mapped to the custom pick-list.

CDK Global

CDK Deal Payment

maps to

Freshsales

Custom Object: Payment

1:1
Fully supported

Down payment, finance amount, APR, lender, and payment amount have no Freshsales native equivalent. A Payment custom object linked to the Deal captures finance details. Lender name maps to a text field; APR and payment amount map as number fields.

CDK Global

CDK Owner / User

maps to

Freshsales

Freshsales User

1:1
Fully supported

CDK user records resolve against Freshsales users by email address. Unmatched CDK owners are flagged before migration — the team either creates Freshsales users or assigns those records to a fallback owner. CDK user role and permission data has no Freshsales equivalent.

CDK Global

CDK Activity (Task / Note)

maps to

Freshsales

Task / Note

1:1
Fully supported

CDK service notes, deal notes, and general activity records map to Freshsales Tasks (for action items) or Notes (for informational records). Original timestamps and owning user are preserved. Subject and description fields map directly. Any attachments linked to a note are downloaded and re‑uploaded as Freshsales Files, preserving file names and sizes. If a note references a vehicle or deal, we link it via a lookup relationship to maintain context.

CDK Global

CDK Attachment / Document

maps to

Freshsales

Freshsales Files

1:1
Fully supported

CDK documents attached to customers, deals, or vehicles are downloaded and re-uploaded as Freshsales Files associated with the corresponding record. File size limits apply (Freshsales default 25MB per file). Inline images in notes are rehosted. During the download step we verify each file’s integrity with a checksum, and any file exceeding the 25MB limit is flagged for manual handling or compression before upload. We also log the original file path in Freshsales for auditability.

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Vehicle-centric data model has no contact-centric equivalent

    CDK Global organizes every record around the vehicle — VIN, make, model, service history, and F&I products all anchor to the vehicle object. Freshsales has no native vehicle object. Vehicles, service records, and F&I data must be mapped into Freshsales custom objects linked to Contacts or Accounts, or stored as custom fields on the Contact record. The chosen schema strategy (custom object per vehicle vs. embedded custom fields) must be decided before migration begins, as it affects every downstream query and report in Freshsales.

  • CDK F&I product types require custom pick-list value mapping

    CDK stores F&I product types (GAP, Tire & Wheel, Paint Protection, Extended Service Contract, Theft Deterrent, Credit Life) as pick-list values with no Freshsales native equivalent. These map to a custom pick-list on the Deal F&I Product custom object, but each value requires explicit mapping in the migration plan. If CDK uses provider-specific product names instead of standardized type labels, the mapping expands to include value normalization as well as type classification.

  • CDK export tooling covers predefined data sets only

    CDK's Data Export Tool provides SFTP exports for a fixed set of predefined data sets: customer, deal, vehicle, service, parts, and accounting. Any non-standard fields added to CDK via custom configurations or third-party integrations may fall outside the export scope and require separate Fortellis API calls. We audit the full CDK field inventory before migration to identify any fields that need supplemental API extraction. During the audit we generate a supplemental extraction plan that lists each non‑standard field, its source module, the Fortellis API endpoint, and expected volume. We then run a test pull for a subset of records to confirm API connectivity and field coverage before the full run.

  • Data integrity may be compromised from 2024 CDK outage

    The June 2024 CDK ransomware incident disrupted operations for an estimated 15,000 dealerships during the outage period. Records created or modified during the outage window may have been entered manually, entered with errors, or left incomplete. We recommend a pre-migration data quality audit to flag records with missing critical fields (VIN, customer email, deal amount) before migration begins. Our audit runs automated checks for missing VINs, invalid emails, and zero‑amount deals, producing a cleansing worksheet. Any records still incomplete after correction are migrated but flagged with a custom field for post‑migration review, and the delta‑pickup window can capture later fixes.

  • CDK workflows have no Freshsales equivalent and must be rebuilt

    CDK service reminders, F&I product triggers, deal approval chains, and DMS-specific automations are built on CDK's automotive business-rule engine. Freshsales Workflows use an independent rule builder with triggers based on Contact, Account, Deal, and custom object events. Automotive-specific logic — like triggering a service reminder when vehicle mileage crosses a threshold — requires redesign as a Freshsales Workflow. We export CDK workflow definitions as a rebuild reference document for the Freshsales admin.

Migration approach

Six steps for a successful CDK Global to Freshsales data migration

  1. Scope CDK modules and design Freshsales custom object schema

    We audit your CDK modules in use (CRM, F&I, Service, Inventory) and inventory every field across all modules. We then design the Freshsales custom object schema — Vehicle, Service Record, Deal F&I Product, and Payment custom objects — with the correct field types, pick-lists, and lookup relationships before any data is extracted from CDK. During the audit we also capture any custom pick‑list values, default settings, and field‑level validation rules that must be recreated in Freshsales to preserve data semantics.

  2. Extract CDK data via Fortellis API and Data Export Tools

    CDK data extracts via the CDK Data Export Tool (SFTP) and Fortellis API where non-standard fields require supplemental calls. We extract customers, companies, deals, F&I products, vehicles, service records, and attachments. Owner resolution runs in parallel — CDK user emails are matched against Freshsales users by email, and unmatched owners are flagged for team resolution before migration. We also capture any historical activity logs, notes, and linked documents, ensuring all relevant data is staged for transformation and loading into Freshsales.

  3. Run sample migration with field-level diff on representative dataset

    A representative slice of records (typically 100–500 spanning customers, deals, vehicles, and service history) migrates first. We generate a field-level diff report comparing source values against Freshsales field values so you can verify F&I product type mapping, vehicle record linkage, owner resolution, and lifecycle stage mapping before the full run commits. The diff highlights any discrepancies such as missing pick‑list values, mismatched owner emails, or incomplete vehicle data, allowing you to adjust the mapping plan before the final load.

  4. Execute full migration with delta-pickup and rollback on standby

    Full migration runs against Freshsales with the agreed schema. A delta-pickup window (typically 24–48 hours) captures any CDK records modified during the cutover so Freshsales reflects CDK's final state at go-live. Audit logs record every operation. One-click rollback is available if reconciliation fails or Freshsales data does not match the agreed mapping plan. During the run we monitor record counts, error rates, and API response times, and we provide a real‑time dashboard so you can track progress and any issues as they arise.

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

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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

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

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

Can't find your answer?

Walk through your CDK Global to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most CDK-to-Freshsales migrations complete in 3–5 days of clock time for under 10,000 records with standard CDK modules in use. Larger datasets or complex setups with vehicle custom objects, F&I product types, and multi-location CDK configurations extend to 2–4 weeks. The Freshsales custom object schema design phase is the longest planning step before any data moves. After schema design, a representative sample (100–500 records) is migrated first to generate a field‑level diff, and a delta‑pickup window captures any CDK changes during cutover, ensuring the final Freshsales state reflects the live source at go‑live.

Adjacent paths

Related migrations to explore

Ready when you are

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