Migrate from CDK Global to Microsoft Dynamics 365 Sales

Business-type CDK customers map 1:1 to Dynamics 365 Account. CDK's DealerCode, CustomerStatus, and CreditLimit fields migrate as custom fields on Account. Primary address and phone map directly. Multiple locations per customer in CDK require a parent Account with child Accounts in D365.

Consumer-type CDK customers map to Contact records in D365. The Contact.AccountId lookup field resolves to the corresponding Account record for B2C contacts linked to business accounts. CDK's DriverLicenseNumber and BirthDate migrate as custom fields on Contact when required for compliance or verification workflows. Personal email addresses and mobile phone numbers map directly to Contact.EmailAddress1 and Contact.MobilePhone for immediate usability in D365 marketing and communication sequences.

CDK prospects without a closed deal map to D365 Lead. Lead Source, Lead Rating, and InterestLevel from CDK map to corresponding Lead fields. CDK's ProspectNotes become the D365 Lead Description field. When a CDK prospect converts to a deal, the Lead converts to Account/Contact/Opportunity in D365.

CDK vehicle records split into two: the vehicle product data (make, model, year, trim) maps to D365 Product, while automotive-specific fields (VIN, stock number, odometer, vehicle condition) require a custom Vehicle__c table with a lookup to Product. Dealerships on Sales Professional must combine vehicle data into the Product record with extended custom fields due to the 15-table limit.

CDK deals with a vehicle and customer map to D365 Opportunity linked to the Account (via AccountId) and the Vehicle Product (via OpportunityProduct). Deal amount, stage, expected close date, and owner map directly. CDK DealType and DealStatus become custom fields on Opportunity.

F&I products (GAP, wheel-and-tire, service contract, dent ding) have no D365 native equivalent. We create a custom F_I_Product__c table with fields for product type, rate, term, and provider — linked to the parent Opportunity via OpportunityId. For reporting, F&I products also appear as Opportunity Product line items with custom pricing.

CDK service records map to D365 Case for service request tracking. RO-specific fields (RO number, technician name, labor hours, labor rate, parts used) migrate as a custom RO_Record__c table linked to Case. Open vs. closed RO status maps to Case Status. Vehicle lookup links the Case to the CDK Vehicle record.

CDK parts catalog maps to D365 Product records with the parts category. Part number, description, list price, and cost map directly. Inventory quantities require a custom Inventory__c field on Product or a linked custom table. CDK bin locations map to D365 Warehouse or a custom Location__c field.

CDK employee records resolve by email to D365 SystemUser. Unmatched employees are flagged before migration — dealerships either invite them to D365 first or assign their records to a fallback user. CDK roles map to D365 security roles, though CDK-specific role names require manual role assignment post-migration.

CDK logged calls and tasks map to D365 Task records with the original subject, description, due date, and owner preserved. CDK appointments map to D365 Appointment with start/end times. Parent regarding links each activity to the corresponding Account, Contact, or Opportunity record.

CDK notes and supporting documentation migrate to D365 Annotation records and attach directly to the parent record in the respective entity (Account, Contact, Lead, Opportunity, or Case). File attachments are downloaded from CDK's storage system and re-uploaded to D365 SharePoint/OneDrive integration for documents or attached directly to D365 Notes with file attachment. The migration preserves original file names, create timestamps, and last-modified dates so the document history remains intact for compliance and audit trail purposes.

CDK parent-dealer and sub-dealer relationships map to D365 Territory for reporting visibility. For Sales Enterprise, a custom Dealer__c table with self-referencing Parent_Dealer__c lookup captures the full franchise hierarchy. For Sales Professional, hierarchy information is stored in a custom field on Account.

CDK custom fields and user-defined data points migrate as custom columns on the corresponding D365 table. If CDK has fully custom objects (rare), they map to new D365 custom tables with appropriate relationships. Sales Professional's 15-table limit applies — excess custom objects may require combining into existing tables.