CRM migration
Field-level mapping, validation, and rollback between CDK Global and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
CDK Global
Source
Freshsales
Destination
Compatibility
10 of 10
objects map 1:1 between CDK Global and Freshsales.
Complexity
BStandard
Timeline
3–5 days
Overview
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.
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 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
Freshsales
Contact
1:1CDK 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
Freshsales
Account
1:1CDK 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
Freshsales
Deal
1:1CDK 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
Freshsales
Custom Object: Vehicle
1:1VIN, 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
Freshsales
Custom Object: Service Record
1:1RO 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
Freshsales
Custom Object: Deal F&I Product
1:1F&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
Freshsales
Custom Object: Payment
1:1Down 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
Freshsales
Freshsales User
1:1CDK 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)
Freshsales
Task / Note
1:1CDK 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
Freshsales
Freshsales Files
1:1CDK 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.
| CDK Global | Freshsales | Compatibility | |
|---|---|---|---|
| CDK Customer | Contact1:1 | Fully supported | |
| CDK Customer Company Link | Account1:1 | Fully supported | |
| CDK Deal | Deal1:1 | Fully supported | |
| CDK Vehicle | Custom Object: Vehicle1:1 | Fully supported | |
| CDK Service Record | Custom Object: Service Record1:1 | Fully supported | |
| CDK Deal F&I Product | Custom Object: Deal F&I Product1:1 | Fully supported | |
| CDK Deal Payment | Custom Object: Payment1:1 | Fully supported | |
| CDK Owner / User | Freshsales User1:1 | Fully supported | |
| CDK Activity (Task / Note) | Task / Note1:1 | Fully supported | |
| CDK Attachment / Document | Freshsales Files1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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
CDK Global
Source
Strengths
Weaknesses
Freshsales
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 Freshsales.
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 Freshsales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave CDK Global
Other ways to arrive at Freshsales
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.