Migrate from Tekion to Salesforce Sales Cloud

Tekion's Customer.Person entity maps directly to Salesforce Contact as a one-to-one field mapping. Standard fields including first name, last name, email address, phone number, and complete mailing address transfer as direct field-to-field matches without transformation logic. The original customer creation timestamp from Tekion is preserved as a custom Original_Create_Date__c datetime field on Contact, since Salesforce's native CreatedDate will reflect the migration batch execution time rather than the original record creation date in Tekion. The Tekion customer unique identifier is stored as Source_System_ID__c for de-duplication and traceability during delta migration runs.

Tekion's Customer.Company entity converts to Salesforce Account using direct field mappings where possible. The company name populates Account.Name, the website URL maps to Website, and the industry classification transfers to the Industry pick-list. Any value mismatches between Tekion's industry taxonomy and Salesforce's pick-list options are resolved during the pre-migration value-mapping phase. The DMS dealer identification number issued by Tekion is stored as a custom Dealer_ID__c text field on Account, providing a reliable cross-reference key for reconciling records against Tekion reports and for linking back to the original DMS system if needed.

Tekion stores customer type (individual, business, fleet) as a property on the Customer record. We split individuals to Contact only, businesses to Account with a Contact for the primary contact person, and fleet buyers to Account with the Fleet_Buyer__c flag set to true.

Tekion's CRM lead export maps to Salesforce Lead with standard fields (FirstName, LastName, Email, Phone, Company). Tekion lead score and source campaign map to custom Number and Text fields on Lead. Historical leads beyond the 90-day window may require a separate DMS data pull.

Tekion Deal maps to Salesforce Opportunity with deal amount as Amount, close date as CloseDate, and deal stage as StageName. Tekion's deal type (new vehicle, used vehicle, service) maps to a custom Deal_Type__c pick-list field. RecordTypeId is assigned based on deal type for Salesforce page layout routing.

Tekion F&I products — financing, GAP waiver, service contract, etch — are line items within the Deal jacket. We map these to Salesforce OpportunityLineItem using PricebookEntry linked to a Tekion F&I product catalog custom pricebook. Each product type maps to a custom Product_Category__c field on the line item.

Tekion Vehicle has no Salesforce standard equivalent. We create a Vehicle__c custom object with VIN__c as the Name field, Stock_Number__c, Year__c, Make__c, Model__c, Trim__c, Mileage__c, Condition__c (New/Used/Certified Pre-Owned), and a lookup to the selling Account. Asset records are created in parallel for warranty tracking.

Tekion service records map to Salesforce Case with Subject set from the RO number, Description from the service advisor notes, and Status from the repair order completion flag. Vehicle__c lookup links the Case to the Vehicle record. Technicians and service advisors map to Case team members by email match.

Tekion documents attached to deals, customers, and vehicles are downloaded and re-uploaded to Salesforce Files linked to the corresponding record. File size limits (25MB per file in Salesforce) are enforced during re-upload. Inline images in Tekion note fields are extracted and hosted as Salesforce Files.

Tekion users and owners are matched to Salesforce Users by email address. Unmatched owners are flagged in the pre-migration report — your team either creates Salesforce User records for them before migration or assigns them to a fallback owner to prevent orphaned records.

DMS-specific data — parts inventory, accounting ledgers, technician schedules — lives in Tekion's DMS module and is not part of the CRM API export scope. These records do not migrate to Salesforce Sales Cloud and should be handled separately as part of a broader ERP migration if needed.

Tekion's workflow automations (lead routing, deal stage triggers, service appointment reminders) are platform-native and tied to Tekion's event model. They cannot be extracted via API. We provide a Tekion Workflow Definition Export as a reference document for your Salesforce admin to rebuild equivalent logic in Flow.