Migrate from Tekion to HighLevel

Tekion customer records map directly to HighLevel contacts. The customer's name, email, phone, address, and contact type fields transfer as HighLevel standard fields. Owner assignment resolves by email match against HighLevel users. Records without a primary email flag as duplicates for manual review before commit.

Tekion leads that have not completed a vehicle purchase become HighLevel contacts tagged as 'Tekion_Lead' with lifecycle stage captured in a custom field (Lifecycle_Stage__c). Tekion's 90-day CRM window means pre-window leads require re-entry or manual import from spreadsheets. We recommend exporting any such pre-window leads from Tekion's reporting module before the migration window to ensure a complete lead history.

Tekion's dealership-level organization (dealer name, franchise brand, address, dealer code) maps to HighLevel's Company object. For multi-rooftop migrations, each dealership location becomes a separate HighLevel Company record. Franchise OEM affiliation stores as a custom field on the Company record. We also map the dealer code to a custom field (Dealer_Code__c) for reconciliation and reporting purposes.

HighLevel has no native vehicle object. We create a Tekion_Vehicle__c custom object with fields for VIN (unique identifier), Year, Make, Model, Trim, StockNumber, and VehicleType. Each vehicle links to its owning Contact via a relationship field. Active inventory vs. sold history distinguished by a Status custom field.

Tekion's F&I deal record — deal type (retail, lease, buy-rate), APR, term, backend F&I products — becomes a HighLevel opportunity with custom fields: Deal_Type__c, APR__c, Term__c, F_and_I_Products__c. The opportunity's name uses a convention like '2024 Toyota Camry — [Customer Name]' for readability in the HighLevel pipeline view.

Vehicle service history — RO number, service type, mileage, advisor notes, parts used — maps to a Tekion_Service__c custom object linked to the Contact and Tekion_Vehicle__c record. Service appointments and completed work orders store as tasks with Type='Service' for pipeline reporting. Original service date preserved as a custom datetime field.

Tekion lead stages (New, Contacted, Test Drive, Financing, Sold, Lost) map to HighLevel opportunity pipeline stages. Stage-to-stage probability values apply per HighLevel's pipeline stage configuration. Each Tekion pipeline maps to a separate HighLevel pipeline if multi-pipeline setup exists. We also set default probabilities for each stage based on typical conversion rates, which you can adjust in HighLevel's pipeline settings.

Tekion's logged calls, emails, and notes attach to the contact or vehicle record and migrate as HighLevel activities. Original timestamps and owning user preserved. HighLevel's activity feed displays these inline with the contact record. Attachments re-upload as HighLevel files linked to the parent record.

Tekion user and owner records resolve to HighLevel users by email address. Unmatched Tekion owners flag before migration — your team either creates HighLevel users for them or reassigns their records to a fallback user. Role and permission sets require manual rebuild in HighLevel's user management.

Tekion's custom fields on any DMS object — service types, OEM-specific classifications, survey scores — map to HighLevel custom fields on the equivalent object. Field type mapping applies: Tekion pick-lists become HighLevel dropdown custom fields, text fields map to text, numeric fields map to number with precision preserved.

Tekion's workflow rules, AI agents (Service AI, Scheduler AI, Technician AI), and dealership automations have no direct equivalent in HighLevel. We export Tekion's workflow definitions as a structured JSON document that your HighLevel admin can use as a reference when rebuilding automations in HighLevel's Workflows builder.