Migrate from Tekion to Pipedrive

Tekion Customer records map 1:1 to Pipedrive Persons. Standard fields (firstname, lastname, email, phone, address) translate directly, along with createdate and updatedate timestamps. Tekion's automotive-specific extended properties — VIN, license plate, service records — are handled as Pipedrive custom fields on the Person record. The migration preserves original owner assignments via email-based user resolution.

Tekion Dealership Organization maps to Pipedrive Organization. Organization name, address, industry, and employee count translate directly. Parent dealership hierarchies map via Pipedrive's parent organization field if Tekion stores multi-rooftop structures. Website, phone, and custom dealership properties also transfer to maintain complete organization profiles in Pipedrive.

Tekion Deal records map to Pipedrive Deals. Deal name, value, stage name, close date, owner, and create/update timestamps transfer. Tekion deal stage names map to Pipedrive pipeline stage values by name with value mapping for stage probabilities. Deal description and notes also migrate, preserving full deal context for sales reps reviewing history in Pipedrive.

Tekion activity records — calls, emails, meetings, and notes — map to Pipedrive Activity objects by type. Original timestamps, owners, and linked Person/Deal associations are preserved. Activity subject and body content transfer as-is. The owner_id resolves via email match to ensure activities assign to the correct Pipedrive user during migration.

Tekion vehicle records (VIN, license plate, make, model, year, mileage) have no native Pipedrive equivalent. We create Tekion_VIN__c (text), Tekion_License_Plate__c (text), Tekion_Vehicle_Make__c (text), Tekion_Vehicle_Model__c (text), Tekion_Vehicle_Year__c (number), and Tekion_Mileage__c (number) as custom fields on the linked Person record. These fields are created as part of the pre-migration custom field plan before migration runs.

Tekion F&I product records — extended service contracts, GAP coverage, paint protection, tire-and-wheel coverage — store as Tekion_FI_Products__c custom text area on the Person record. If F&I products are linked to specific deals, Tekion_FI_Deal_Link__c associates the F&I product summary with the relevant Pipedrive Deal for complete product-to-deal visibility.

Tekion service records (appointment date, service type, RO number, advisor, mileage at service) have no Pipedrive equivalent. Tekion_Service_Date__c, Tekion_Service_Type__c, Tekion_RO_Number__c, and Tekion_Service_Advisor__c store as custom fields. Multiple service records for one customer aggregate into a comma-separated or JSON custom field.

Tekion owner IDs resolve to Pipedrive users by email match. Unmatched owners are flagged before migration and reported for team resolution; their records route to a designated fallback Pipedrive user during the migration run. Active or inactive owner status in Tekion preserves as a custom Tekion_Owner_Status__c picklist field on the migrated record.

Tekion file attachments linked to Customer, Organization, or Deal records re-upload to Pipedrive as File attachments on the corresponding Person, Organization, or Deal. Original file names and types are preserved during re-upload. File size limits per Pipedrive plan apply, with a default 25MB per file cap depending on subscription tier.

Tekion's DMS layer — parts inventory, technician scheduling, repair orders, service bay data, and manufacturing work orders — has no Pipedrive equivalent and is excluded from the CRM migration. These operations fall outside Pipedrive's Person/Organization/Deal/Activity schema entirely. We provide a structured CSV export of all excluded DMS data for separate handling and downstream system integration.

Tekion custom CRM properties beyond automotive fields migrate as Pipedrive custom fields. Each custom property must be pre-created in Pipedrive with matching field type before migration runs. We deliver a custom field creation plan listing all Tekion custom properties and their recommended Pipedrive type.

If Tekion stores a separate Lead object distinct from Customer, those records migrate as Pipedrive Persons in a designated pipeline labeled 'Migrated Leads' to keep them separate from existing CRM data. Tekion lead status maps to a custom Tekion_Lead_Status__c picklist field, and conversion-ready leads can be processed through Pipedrive's lead conversion workflow post-migration.