Migrate from Tekion to Twenty CRM

Tekion's Contact record maps directly to Twenty's People object. First name, last name, email, phone, job title, and address fields map 1:1. Tekion contacts without a primary company association land as standalone People records in Twenty with no CompanyId link.

Tekion's phone field (string) maps to Twenty's Phone field (text). When a contact has multiple phone numbers stored under different types in Tekion—such as mobile, office, or home—the primary number populates Twenty's Phone field; any secondary numbers are appended as semicolon‑separated values in the custom Tekion_Phone_Alt__c field, preserving the full contact detail set.

Tekion does not expose a persistent internal ID in standard CRM exports; therefore, we capture the exported record identifier and store it as source_system_id__c (text, custom field) on each Twenty People record. This field is created in Twenty's data model before the import and serves as a stable reference for delta-run de-duplication, allowing a second migration pass to update only changed records rather than reloading the entire dataset.

Tekion's Company object maps to Twenty's Company object. Company name, website (domain), industry, employee count, and annual revenue map directly. Tekion company hierarchies (parent/child relationships) map to Twenty's Parent CompanyId field. Multi-contact companies collapse to one primary Company record with all related People linked via companyId.

Tekion stores the company website URL as the field named 'domain'. Twenty also uses a 'domain' field for the same purpose, enabling a direct 1:1 mapping. The domain value is critical for Twenty's company deduplication logic during import; therefore, the field must be present, correctly formatted (typically lowercase, without leading http:// or https://), and match the Tekion source exactly to avoid duplicate Company records.

Tekion's Deal object maps to Twenty's Opportunity object. Deal name, amount, stage, and expected close date map 1:1. Tekion supports multiple deal pipelines that map to Twenty's pipeline kanban stages. Each Tekion pipeline stage value maps to a corresponding Twenty Opportunity Stage via value mapping.

Tekion vehicle records (VIN, make, model, year, trim, stock number, Odometer) have no direct Twenty equivalent. We create custom text fields on the People object: Vehicle_VIN__c, Vehicle_Make__c, Vehicle_Model__c, Vehicle_Year__c, Vehicle_Stock__c. The vehicle is linked to the customer (buyer) via the People record that carries these custom fields.

Tekion F&I product names, coverage types, and pricing attach to the deal record. We map these as custom fields on the Opportunity: FI_Product_Name__c (text), FI_Coverage_Type__c (select), FI_Price__c (currency). The F&I product narrative or contract notes migrate as a Twenty Note attached to the Opportunity.

Tekion service appointments—including advisor name, repair‑order (RO) number, service type, and current status—are transformed into Twenty Task records. Custom fields Service_RO_Number__c, Service_Type__c, Service_Advisor__c, and Service_Status__c capture the appointment specifics, while the original appointment start time maps to the Task due date and the completion timestamp maps to the Task completion date in Twenty. These custom fields must be created in the Twenty workspace before the import to avoid validation errors.

Tekion parts orders are automotive‑specific records with no standard Twenty CRM mapping. We create a custom object named 'Parts Order' in Twenty, adding fields Order_Number__c, Part_Number__c, Quantity__c, Price__c, and Order_Status__c. A relation field on this object points to the parent Opportunity, linking each part sale to its deal record. The custom object and fields must be defined in the Twenty workspace under Settings → Data Model before migration runs.

Tekion owner IDs resolve by email match against Twenty workspace members. All Tekion users must be invited to Twenty and accept their invitations before migration runs—Twenty requires users to exist before owner relations can be mapped. Unmatched owners are flagged and assigned to a fallback Twenty user before migration commits.

Tekion DMS documents (deal jackets, F&I contracts, service records) stored as file attachments have no direct Twenty equivalent. We migrate the file URL and filename as a Note with a custom field Attachment_URL__c for reference; actual file re-hosting requires a separate document migration step. Tekion PDF document conversion runs separately and requires the document data to be provided upfront per Tekion's implementation terms.

Tekion's standard CRM conversion limits lead data to 90 days of active leads based on lead creation date. Leads older than this window are not included in a standard Tekion export and cannot be migrated without a custom data extraction arrangement. We flag any leads outside the 90-day window and surface them in the migration plan for manual review.

Any Tekion custom CRM objects beyond standard Contact, Company, and Deal are mapped 1:1 to Twenty custom objects. N:N associations in Tekion require junction objects in Twenty—these are surfaced in the migration plan before data lands. The Twenty workspace must have the custom objects and fields created via Settings → Data Model before the migration runs.