Migrate from Tekion to Freshsales

Tekion's customer records map directly to Freshsales Contacts through a field-by-field translation. Every Tekion contact field — including name, email, phone, address, job title, and owner assignment — translates to the equivalent Freshsales Contact field using direct mapping or value transformation where field types differ. Owner resolution happens by matching the Tekion owner email against Freshsales user accounts before migration; any unmatched owners are flagged for your team to create Freshsales users or assign a fallback owner.

Tekion's CRM lead records migrate as Freshsales Leads. Tekion lead status, source, score, and custom properties map to Freshsales Lead fields. Lead-to-contact conversion mapping is configurable: your admin defines which Tekion lead stages route to Freshsales Contact vs remain as Leads.

Tekion companies (dealerships or business accounts) map to Freshsales Accounts. Tekion's dealer-group hierarchy — parent rooftop and child locations — translates to Freshsales Account hierarchy via the Parent Account field. Multi-location dealer groups require parent-account creation before child accounts migrate.

Tekion deals (vehicle sales, F&I products, service contracts) migrate as Freshsales Opportunities. Deal name, amount, stage, close date, owner, and custom fields map to Opportunity fields. Tekion deal pipelines map to Freshsales sales pipelines, which map to Opportunity Stage values.

Tekion's CRM deal pipelines translate directly to Freshsales Sales Pipelines, preserving the same pipeline structure and workflow logic. Each pipeline configured in Tekion becomes a separate Kanban board view in Freshsales, maintaining your team's familiar deal tracking layout. Pipeline stage names and values map one-to-one to Freshsales Stage pick-list values within each corresponding pipeline, ensuring deal progression logic carries over without manual reconfiguration.

Tekion vehicle records (VIN, make, model, year, mileage) have no Freshsales standard equivalent. We create custom fields on the linked Account or Contact record — Vehicle_VIN__c, Vehicle_Make__c, Vehicle_Model__c — to preserve vehicle association. Multiple vehicles per customer create multiple custom field sets.

Service appointments map as Freshsales Activities (Tasks and Events) linked to the customer Contact and vehicle-bearing Account. Key service fields (RO number, service type, mileage at service) become custom fields on the Activity record. Original service date and technician assignment are preserved.

F&I product terms attached to a Tekion deal (extended warranty, GAP, paint protection) translate to Freshsales Opportunity Product Line Items or custom fields on the Opportunity — depending on whether Freshsales Products module is in use. Price and product name map directly; term length and coverage type become custom fields.

Tekion engagement records — including calls, emails, meetings, and notes — map directly to Freshsales Tasks, Events, and Notes respectively. All original metadata is preserved during migration, including timestamps, owners, subject lines, and associated contact or account links. Call recordings and email body content exported from Tekion are attached as files to the corresponding Freshsales activity records, maintaining a complete communication history in the destination system.

Tekion users and deal owners resolve by email match against Freshsales users. Unmatched owners are flagged before migration — your team either creates Freshsales users first or assigns records to a fallback owner. No record lands without a valid Freshsales owner assignment.

Tekion CRM custom properties on Contacts, Leads, Deals, and Accounts map to Freshsales custom fields. Freshsales Garden caps custom fields at 100 per module; Estate/Forest allow 300. If Tekion custom property count exceeds the plan limit, we consolidate related fields or flag fields for Freshsales admin to create post-migration.

Tekion DMS data — vehicle history, service records, parts inventory — has no standard Freshsales equivalent and cannot be fully modeled in a general CRM. We preserve vehicle service history as custom fields on Accounts and flag historical DMS data for reference-only archiving in Freshsales or a linked system.