Migrate from Drivecentric to Microsoft Dynamics 365 Sales

DriveCentric contact maps directly to Dynamics 365 Contact. DriveCentric stores the primary company as a flat contact property; this translates to Contact.AccountId — the Account record must exist first. DriveCentric contacts without a company receive a placeholder 'Unassigned Account' record so the AccountId lookup is never null in Dynamics.

DriveCentric has no separate Lead entity; prospects live as contacts until a deal is created. For dealerships that qualify leads separately before creating a deal, we create Dynamics 365 Lead records from DriveCentric contacts flagged as prospects, preserving all contact properties plus the original DriveCentric created date as a custom field.

DriveCentric company objects map directly to Dynamics 365 Account records. Parent-child company hierarchies in DriveCentric translate to Account.ParentAccountId relationships, preserving organizational structure. Multi-location dealership groups with separate company records per rooftop map to individual Account records that share a common parent Account representing the dealership group hierarchy. All company properties including address, phone, and industry classification transfer to standard Account fields.

DriveCentric deal maps to Dynamics 365 Opportunity. Deal fields — name, amount, close date, stage — translate to Opportunity.Name, Amount, EstimatedCloseDate, and StageName. The StageName value map is per sales process; automotive-specific stage labels like 'Internet', 'F&I', 'Delivery' require custom stage values in the Dynamics Sales Process.

DriveCentric activity records (follow-up tasks, call logs, SMS logs) map to Dynamics 365 Task. Subject, Description, Priority, and Status transfer directly. Original timestamps transfer as custom fields since Dynamics sets ActualEnd on task completion. Task.RegardingObjectId links back to the parent Contact or Opportunity using the resolved Dynamics record ID.

DriveCentric notes map to Dynamics 365 Note (modern notes-enabled entity). Title, Body, and Owner transfer. Embedded file attachments are downloaded from DriveCentric storage and re-uploaded to Dynamics 365 SharePoint-connected file storage or Dataverse file attachments, preserving original file names and content.

DriveCentric stores automotive properties — make, model, year, VIN, stock number, trim — as custom fields on the contact and deal records. These become custom fields on Dynamics 365 Contact and Opportunity entities (VehicleMake__c, VehicleModel__c, VehicleYear__c, VIN__c, StockNumber__c). The custom field namespace is managed inside a Dataverse solution for clean export/import lifecycle.

DriveCentric tracks trade-in vehicle details and appraisal values as custom properties on deals. These map to custom fields on Dynamics 365 Opportunity (TradeInVIN__c, TradeInValue__c, TradeInMake__c, TradeInModel__c). Dollar amounts transfer as numeric fields; original currency codes are preserved for multi-currency Dynamics deployments.

DriveCentric stores DMS system links (Dealertrack ID, CDK link, Reynolds & Reynolds account reference) as custom fields. These map to DMSReference__c on Contact and Account in Dynamics 365 Sales. The field is informational in Dynamics; actual DMS connectivity must be re-established via Power Platform connectors or ISV integrations post-migration.

DriveCentric owner records (salesperson assigned to a deal or contact) resolve by email match against Dynamics 365 SystemUser table. Unmatched owners are flagged before migration so the admin can create the corresponding Dynamics user or assign to a fallback owner. Owner assignment on Opportunity maps to Opportunity.OwnerId; on Contact to Contact.OwnerId.

DriveCentric Enterprise custom objects (e.g., Service Appointment, Vehicle Inventory) map 1:1 to Dynamics 365 custom tables via Dataverse. Custom object associations that use DriveCentric's N:N junction model need an explicit junction table in Dynamics — we surface the required relationship schema in the migration plan for admin review before data lands.

DriveCentric file attachments on records (images, documents, deal sheets) are downloaded from DriveCentric storage and re-uploaded to Dynamics 365's connected SharePoint or OneDrive for Business document library. The original file name, MIME type, and uploaded-by user are preserved in the SharePoint metadata.