Migrate from Tekion to Microsoft Dynamics 365 Sales

Direct map. Tekion customer name, address, and contact information map to Dynamics 365 Account. Phone, email, and website fields transfer directly. Parent-child company hierarchies in Tekion map to the ParentAccountId lookup in Dynamics 365. This hierarchy preservation maintains territorial sales assignments and regional reporting structures within the migrated CRM data.

Direct map. Tekion contact records (salesperson, service advisor, F&I manager) map to Dynamics 365 Contact. The primary contact on an Account gets the primarycontactid lookup set. Secondary contacts attach to the same Account. This mapping preserves the communication pathways and escalation hierarchies that dealer organizations rely on for coordinated customer engagement.

Dynamics 365 has no native vehicle entity. We create a custom Dataverse table (Vehicle) with columns for VIN, StockNumber, Make, Model, Year, and Mileage. The Vehicle record links to the Account (customer) via a lookup field. One customer can own multiple vehicles.

Tekion F&I deals map to Dynamics 365 Opportunity. F&I product type (Extended Service Contract, GAP, Maintenance) becomes a custom pick-list field (F&I_ProductType__c). Deal amount, term, and monthly payment map to custom currency and number fields. Tekion deal stage maps to Opportunity StageName via value mapping.

Direct map for internet leads captured in Tekion. Lead source, status, and estimated value fields map to the Dynamics 365 Lead entity. Lead scores from Tekion migrate as a custom integer field (Tekion_LeadScore__c). When a Lead converts, entity mappings pre-populate the resulting Account and Contact.

Tekion service history (RO number, service type, labor, parts, advisor) migrates to a custom Dataverse table linked to the Vehicle record. Original service date and mileage at service are preserved as custom datetime and number fields for warranty and retention reporting.

Owner resolution by email match. Tekion staff records are matched against Dynamics 365 user accounts by email address. Unmatched owners are flagged before migration — dealers either invite them to Dynamics 365 first or assign records to a fallback owner for the migration run.

All Tekion custom fields on Customer, Vehicle, and Deal objects require pre-creation in Dataverse before migration. We deliver a custom-column manifest listing each field name, data type, and pick-list values so your Dynamics admin can create them before the data load runs.

Tekion documents attached to deals, vehicles, or customers are downloaded and re-uploaded to the associated Dynamics 365 record's SharePoint document library or Dataverse file column. File size limits from Dynamics apply (default 128 MB per file). Inline images in notes are extracted and re-hosted separately.

Tekion automations (service reminders, lead-assignment rules, F&I triggers) do not migrate. We export Tekion workflow definitions as a reference document for your Dynamics admin to rebuild in Power Automate. The functional logic — triggers, conditions, actions — is preserved in the export, just not executable in Dynamics 365.

Tekion's internal record ID is stored on every migrated record as Source_System_ID__c. This enables delta-run de-duplication (preventing re-creation of records already migrated) and traceability back to the Tekion source for audit and reconciliation. The Source_System_ID__c field also supports cross-referencing between Tekion reports and Dynamics 365 dashboards during the parallel-running period.

Dynamics 365's CreatedDate and ModifiedDate are set at migration time. Tekion's original create and update timestamps are preserved in custom datetime fields (Original_Create_Date__c, Original_Modified_Date__c) for reporting continuity and historical analysis. These preserved timestamps enable accurate service interval calculations and provide historical context for customer relationship analytics in Dynamics 365.