Tekion to Salesforce migration
Moving from Tekion to Salesforce Sales Cloud lets franchise dealer groups consolidate CRM data into the world's most widely adopted sales platform — with full access to Salesforce's AppExchange ecosystem, Einstein AI, and cross-department reporting that Tekion's automotive-specific data model was never designed to support at scale. FlitStack AI maps Tekion customer records, deal transactions, vehicle inventory, and F&I product fields into Salesforce's Account-Contact-Opportunity object graph, preserving timestamps and owner assignments throughout the migration.
FlitStack AI migrates contacts, accounts, contact + accounts, leads and opportunities from Tekion to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours of clock time for under 50,000 records after Salesforce schema is confirmed ready..

What moves from Tekion to Salesforce?
Tekion operates as an automotive retail platform combining DMS and CRM functions under one roof, with a data model built around the deal jacket — a unified record that ties a customer, a vehicle, and a set of F&I products together in a single transaction context.
Read the full summary
Salesforce Sales Cloud separates these concerns across Account, Contact, Lead, Opportunity, and custom objects, requiring a deliberate schema split during migration. FlitStack AI extracts Tekion's standard CRM export (Customers, Leads, Deals, Service Records, Attachments) and maps each entity into Salesforce's relational model: Customer.Person and Customer.Company split into Contact plus Account; Tekion Deal becomes Opportunity with custom fields for F&I products; Tekion Vehicle maps to a custom Vehicle__c object with VIN as the Name field; and Service Records become Cases linked to the parent Contact or Account. The migration uses Tekion's API with scoped read access — no workflows, automation rules, or DMS-specific inventory records move, because Tekion's API license agreement restricts export of derivative data structures. We deliver a pre-migration schema plan, a sample migration with field-level diff, and a 24–48 hour delta-pickup window at cutover so Salesforce reflects Tekion's final state at go-live.
Customer.Person → Contact
Tekion's Customer.Person entity maps directly to Salesforce Contact as a one-to-one field mapping.
How it maps
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.
Customer.Company → Account
Tekion's Customer.Company entity converts to Salesforce Account using direct field mappings where possible.
How it maps
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.
Customer.CustomerType → Contact + Account
Tekion stores customer type (individual, business, fleet) as a property on the Customer record.
How it maps
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.
Lead (CRM conversion, up to 90 days) → Lead
Tekion's CRM lead export maps to Salesforce Lead with standard fields (FirstName, LastName, Email, Phone, Company).
How it maps
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.
Deal (transaction jacket) → Opportunity
Tekion Deal maps to Salesforce Opportunity with deal amount as Amount, close date as CloseDate, and deal stage as StageName.
How it maps
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.
F&I Product Line Item → OpportunityLineItem
Tekion F&I products — financing, GAP waiver, service contract, etch — are line items within the Deal jacket.
How it maps
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.
- Customer.PersonContact1:1
- Customer.CompanyAccount1:1
- Customer.CustomerTypeContacttransformed
- LeadLead1:1
- DealOpportunity1:1
- F&I Product Line ItemOpportunityLineItemtransformed
+ 6 more in the mapping below
How Tekion and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Tekion | Salesforce |
|---|---|---|
| Platform architecture | Unified Automotive Retail Cloud (ARC) combining DMS + CRM in one tenant; API license agreement restricts derivative data extraction and reverse-engineering of integrated structures. | Multi-object CRM with separate Sales Cloud, Service Cloud, and platform layers; unlimited customization via custom objects and fields without API usage restrictions. |
| Record model for customers | Customer.Person + Customer.Company stored as linked sub-objects within a single Customer record; each customer can have multiple vehicles and deals attached. | Contact + Account as separate objects with a required AccountId lookup on Contact; supports N:N relationships via Account Contact Relation; customer type distinguished by record type. |
| Deal / opportunity model | Deal is a transaction jacket tied to one vehicle and one customer; F&I products (financing, GAP, service contract) are line items within the deal record. | Opportunity is a standalone pipeline record linked to Account; Opportunity Contact Role links contacts; Opportunity Product (PricebookEntry + OpportunityLineItem) handles multi-product quoting natively. |
| Vehicle inventory | Vehicle Inventory is a first-class Tekion object with VIN, stock number, year, make, model, trim, mileage, condition, and status fields; lives within the DMS module. | No standard vehicle object in Salesforce Sales Cloud; must be modeled as a custom Vehicle__c object with VIN__c as Name, or as Asset linked to Account/Contact, depending on use case. |
| CRM lead retention window | Standard CRM conversion exports up to 90 days of active lead data based on lead creation date; historical leads beyond 90 days may require separate DMS extraction. | Salesforce stores all Lead records indefinitely with no automatic purge; Lead object supports custom fields, lead scoring, and assignment rules for unlimited historical records. |
| API access and data portability | Tekion API access governed by a license agreement that prohibits re-identification, derivative use, and reverse-engineering of integrated data structures; export scope is limited to what the license permits. | Salesforce Bulk API 2.0 supports up to 15,000 batches per day with 10,000 records per batch; REST API allows 100,000 daily requests plus 1,000 per user license on Enterprise tier; full data portability guaranteed. |
| Automation and workflows | Tekion provides dealership workflow automations for service scheduling, lead routing, and deal stages; automations are platform-native and tied to Tekion's event model. | Salesforce Flow replaces legacy Workflow Rules and Process Builder; flows are built in Lightning Flow Builder and operate on Salesforce records, events, and Schedule triggers independently of import method. |
Tekion to Salesforce field mapping
The 30 most-used fields of 53 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstNameCustomer.PersonFirstNameContact -
lastNameCustomer.PersonLastNameContact -
emailCustomer.PersonEmailContact -
phoneCustomer.PersonPhoneContact -
mobilePhoneCustomer.PersonMobilePhoneContact
| Tekion field | Salesforce field | Mapping | Note |
|---|---|---|---|
Customer.Person.firstName | Contact.FirstName | direct | |
Customer.Person.lastName | Contact.LastName | direct | |
Customer.Person.email | Contact.Email | direct | |
Customer.Person.phone | Contact.Phone | direct | |
Customer.Person.mobilePhone | Contact.MobilePhone | direct | |
Customer.Person.jobTitle | Contact.Title | direct | |
Customer.Person.streetAddress | Contact.MailingStreet | direct | |
Customer.Person.city | Contact.MailingCity | direct | |
Customer.Person.state | Contact.MailingState | direct | |
Customer.Person.postalCode | Contact.MailingPostalCode | direct | |
Customer.Person.country | Contact.MailingCountry | direct | |
Customer.Person.customerType | Contact.Contact_Type__c | custom_field_required | Tekion customer type (Individual/Business/Fleet) stored as a custom pick-list on Contact. |
Customer.Person.createdDate | Contact.Original_Create_Date__c | custom_field_required | Original Tekion create date preserved as a custom datetime field since Salesforce CreatedDate reflects migration time. |
Customer.Person.tekionId | Contact.Source_System_ID__c | custom_field_required | Tekion internal ID stored on Contact for traceability and delta-run de-duplication. |
Customer.Company.companyName | Account.Name | direct | |
Customer.Company.website | Account.Website | direct | |
Customer.Company.industry | Account.Industry | value_mapping | Industry pick-list values mapped value-by-value; Tekion automotive retail categories mapped to Salesforce's Industry pick-list equivalents. |
Customer.Company.phone | Account.Phone | direct | |
Customer.Company.numberOfEmployees | Account.NumberOfEmployees | direct | |
Customer.Company.annualRevenue | Account.AnnualRevenue | direct | |
Lead.firstName | Lead.FirstName | direct | |
Lead.lastName | Lead.LastName | direct | |
Lead.email | Lead.Email | direct | |
Lead.phone | Lead.Phone | direct | |
Lead.company | Lead.Company | direct | |
Lead.status | Lead.Status | value_mapping | Tekion lead status pick-list values mapped to Salesforce Lead Status; custom statuses require explicit value-mapping setup. |
Lead.leadScore | Lead.Lead_Score__c | custom_field_required | Tekion lead scoring migrates as a custom Number field on Lead when present. |
Lead.sourceCampaign | Lead.LeadSource | transformed | Tekion lead source campaign name maps to Salesforce LeadSource pick-list; if no match exists, stored as custom Campaign_Source__c text field. |
Deal.dealName | Opportunity.Name | direct | |
Deal.amount | Opportunity.Amount | direct |
What to watch for in a Tekion to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Tekion's API license agreement restricts derivative data use and bulk export scope
Tekion's API License and Data Sharing Agreement explicitly prohibits re-identifying aggregated data, creating derivative works from API data, and reverse-engineering integrated data structures.
How we handle it
The standard CRM conversion is limited to 90 days of active lead data based on lead creation date, and DMS-level data (parts inventory, accounting ledgers, technician schedules) is not accessible via the CRM API. We work within the license's permitted export scope and flag any data that cannot be extracted before migration begins. DMS-specific records must be handled as a separate data project outside the CRM migration.
Vehicle inventory has no Salesforce standard equivalent — custom object required with VIN as Name
Tekion Vehicle Inventory is a first-class object with VIN, stock number, year, make, model, trim, mileage, and condition fields that has no direct match in Salesforce's standard object model.
How we handle it
Salesforce's Asset object is designed for tracking owned products under warranty, not for new/used vehicle lot inventory. We model Tekion Vehicle as a Vehicle__c custom object with VIN__c as the Name field and External ID enabled for upsert performance. This requires your Salesforce admin to create the custom object metadata before data lands — FlitStack AI delivers the setup plan during the pre-migration schema phase.
Tekion Deal jacket bundles F&I products — Salesforce Opportunity bundles them as line items
Tekion stores financing terms, GAP waiver selection, service contract, and etch products as properties within a single Deal record.
How we handle it
Salesforce Opportunity separates financial products using OpportunityLineItem (tied to PricebookEntry). We create a Tekion F&I product catalog as a custom Salesforce Pricebook, then map each F&I product from the Deal into OpportunityLineItem records linked to the Opportunity. Your Salesforce admin configures the pricebook entries and product categories before migration. Deal-level F&I totals are also preserved as custom fields on Opportunity for reporting continuity.
Multi-rooftop dealer groups need Account hierarchy setup before contact migration
Franchise dealer groups operating multiple rooftops under one Tekion tenant often have customer records shared across locations.
How we handle it
Salesforce requires Accounts to be arranged in a parent-child hierarchy when representing multi-dealership groups. We use Tekion's dealer location identifier to establish Parent Account relationships in Salesforce, then migrate Contacts with AccountId lookups resolved to the correct rooftop Account. Contacts without a primary dealer assignment default to a placeholder 'Unassigned Accounts' record and are flagged for manual reassignment.
Tekion's 90-day CRM lead retention window may exclude historical sales pipeline data
Tekion's standard CRM conversion scope exports up to 90 days of active lead data based on lead creation date.
How we handle it
Leads older than 90 days — including stale but historically valuable prospects — may not appear in the standard CRM export. If your Tekion setup contains lead records beyond the 90-day window that you need to preserve, a supplemental data pull from the DMS module is required. We identify the gap during the pre-migration discovery phase and include a supplemental extraction recommendation in the migration plan.
How the migration runs
Pre-migration discovery and Tekion API scope assessment
FlitStack AI reviews your Tekion CRM configuration — customer record count, lead volume, deal history depth, F&I product catalog, vehicle inventory scope, and attachment count.
What this step covers
We verify export scope against Tekion's API license agreement and identify any data that falls outside the permitted export window (e.g., leads older than 90 days, DMS-level records). We deliver a Tekion Data Export Readiness Report that itemizes exactly what will migrate and what requires a separate project.
Salesforce schema setup with Vehicle__c custom object and F&I pricebook
Before data moves, your Salesforce admin creates the Vehicle__c custom object with the VIN__c external ID field, the F&I product pricebook, and any custom fields referenced in the field mapping (Deal_Type__c, GAP_Waiver__c, Financing_Amount__c, Condition__c, etc.).
What this step covers
We deliver a Salesforce Schema Setup Plan that lists every custom field, pick-list value set, record type, and page layout assignment required, organized by migration priority. This plan is reviewed and approved before we touch any data.
User and owner resolution by email match
Tekion users and deal owners are matched to Salesforce Users by email address.
What this step covers
We generate a User Resolution Report that shows matched users, unmatched owners, and the fallback assignment rule (typically a designated Salesforce admin User). Unmatched owners are either pre-created in Salesforce before migration or assigned to the fallback owner. No record migrates without a resolved OwnerId — this prevents orphaned opportunities and unowned contacts in Salesforce.
Sequenced migration: Accounts → Contacts/Leads → Vehicles → Opportunities → Cases → Files
Migration runs in dependency order: Accounts must exist before Contacts (AccountId required), Vehicles must exist before Opportunities (Vehicle__c lookup), and Opportunities must exist before Cases (for service records tied to a deal).
What this step covers
We run Accounts and Vehicles in the first batch, Contacts and Leads in the second, Opportunities with OpportunityLineItems in the third, Cases in the fourth, and Salesforce Files (re-uploaded from Tekion attachments) in the final batch. Each batch is validated before the next begins.
Sample migration with field-level diff and sign-off
A representative slice — typically 200–500 records spanning each object type — migrates first.
What this step covers
We generate a field-level diff report comparing source Tekion values against destination Salesforce values for every mapped field. You review the diff, verify F&I product mapping, confirm Vehicle__c record creation, and approve before the full run commits. Any field mapping errors are corrected in the migration configuration before proceeding.
Full migration run with 24–48 hour delta-pickup window and audit log
The full migration commits to Salesforce with an open delta-pickup window of 24–48 hours after the run completes.
What this step covers
Any Tekion records created or modified during the window are captured in a second pass. The full audit log — every insert, update, and upsert operation — is exported and delivered to you. One-click rollback reverts all migration operations if reconciliation against your Tekion export report reveals discrepancies exceeding your agreed tolerance threshold.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with the number of Tekion records exported, the count of custom fields needed to capture F&I products and vehicle attributes, and the number of Salesforce custom objects required for automotive-specific data. Standard CRM migrations (Contacts, Leads, Deals, Cases) fall in the lower half of the range. Migrations requiring a custom Vehicle__c object with VIN indexing, multi-rooftop Account hierarchy setup, or F&I product line-item mapping push toward the upper range. The delta-pickup window and post-migration audit log are included in all migrations. FlitStack AI does not charge separately for the sample migration run. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Tekion to Salesforce →Why teams move from Tekion to Salesforce
- Post-acquisition consolidation or multi-brand dealer group needing a single CRM that scales across franchises requires Salesforce's org architecture rather than Tekion's per-dealership tenant model. G2 reviews for Tekion specifically flag implementation complexity and timeline overruns as pain points that make switching to a platform with broader talent availability attractive for IT teams managing multiple locations.
- Salesforce's AppExchange ecosystem — over 5,000 apps — offers reporting, BI, and integration options that Tekion's automotive-only API scope cannot match. Franchise dealer groups evaluating Salesforce cite the ability to connect Sales Cloud with their ERP, manufacturer portals, and third-party F&I menu tools as a primary driver.
- Dealer groups operating across multiple OEM franchises find Tekion's unified DMS+CRM model restrictive when individual manufacturers mandate distinct data structures, reporting formats, and compliance fields. Tekion's per-tenant architecture forces franchise-specific customization that becomes difficult to maintain across brands. Salesforce's multi-record-type, multi-business-unit design allows each franchise to operate under its own page layouts, pick-list values, and validation rules without requiring separate tenant management or custom integrations between Tekion instances.
- The CDK Global ransomware outage of June 2024 — which knocked 15,000 dealerships offline for weeks — accelerated dealer interest in platforms with better data portability guarantees. Dealer principals evaluating Tekion alternatives now ask explicitly about data export rights and API access scope before committing.
Questions, answered
Tekion to Salesforce migration questions
How long does a Tekion to Salesforce Sales Cloud migration take?
Most Tekion-to-Salesforce migrations complete in 48–72 hours of clock time for up to 50,000 records, assuming Salesforce schema is pre-created. Large dealer groups with multi-rooftop Account hierarchies, custom Vehicle__c object with hundreds of vehicle records, or F&I product line-item mapping extending beyond 20 products typically need 5–10 business days. The longest planning step is the Salesforce Schema Setup Plan — getting record types, custom fields, and the F&I pricebook configured before data moves.
Will my Tekion workflow automations migrate to Salesforce Flow?
No. FlitStack AI migrates data and schema only — Tekion workflow automations, lead routing rules, deal stage triggers, and service appointment reminders are platform-native and cannot be extracted via API due to Tekion's API license agreement restrictions. They must be rebuilt in Salesforce Flow. We export your Tekion Workflow Definition Report as a reference document that your Salesforce admin can use to map Tekion automation logic to equivalent Flow triggers, criteria, and actions. Reports and dashboards underlying migrated data are preserved as data sources but the report configurations themselves do not transfer.
What happens to Tekion F&I products (financing, GAP, service contract) in Salesforce?
Tekion F&I products bundled within a Deal record are mapped to Salesforce OpportunityLineItem records using a custom Tekion F&I Pricebook. Financing amount, GAP waiver flag, service contract name, and etch selections migrate as line items linked to the parent Opportunity via PricebookEntry. The deal-level totals are also preserved as custom fields on Opportunity (Financing_Amount__c, GAP_Waiver__c, Service_Contract__c) for reporting continuity without requiring a pricebook query. Your Salesforce admin configures the pricebook entries and product categories before migration.
Can I migrate Tekion vehicle inventory to Salesforce?
Yes — but not as a standard Salesforce object. Tekion Vehicle Inventory maps to a custom Vehicle__c object that FlitStack AI creates as part of the migration plan, with VIN__c set as the Name field and External ID enabled for upsert performance. Fields including stock number, year, make, model, trim, mileage, condition, and color transfer as custom fields on Vehicle__c. A lookup field links each Vehicle__c record to the selling Account. Asset records can be created in parallel for warranty tracking use cases.
What data cannot migrate from Tekion to Salesforce Sales Cloud?
DMS-specific data — parts inventory, accounting ledgers, technician schedules, and DMS configuration settings — lives in Tekion's DMS module and is outside the CRM API export scope per Tekion's license agreement. Workflow automations and sequences cannot be extracted. Reports and dashboard configurations do not transfer; the underlying data does. Leads older than the 90-day CRM conversion window may require a supplemental DMS extraction. We itemize every excluded data type in the Tekion Data Export Readiness Report before migration begins.
Does the migration affect my Tekion account during cutover?
No. FlitStack AI uses scoped read access on Tekion's API — your team continues working in Tekion throughout the migration. A delta-pickup window of 24–48 hours after the full migration run captures any Tekion records created or modified during the cutover period, so Salesforce reflects Tekion's final state at go-live. No write operations are performed against Tekion during the migration. We deliver a complete audit log of every insert, update, and upsert operation committed to Salesforce.
How does Tekion's 90-day CRM lead retention window affect historical lead data?
Tekion's standard CRM conversion exports up to 90 days of active lead data based on lead creation date. Leads created more than 90 days before migration — including long-stale but historically valuable prospects — may not appear in the standard export. During pre-migration discovery, FlitStack AI identifies the gap between your Tekion lead creation dates and the 90-day window. If historical leads are needed in Salesforce, we recommend a supplemental data pull from the DMS module or a manual export of specific lead records for ad-hoc import.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → FreeCRM to SalesforceMapping · history · rollbackHubSpot to SalesforceMapping · history · rollbackMailchimp to SalesforceMapping · history · rollbackChartMogul to SalesforceMapping · history · rollbackKlipy CRM to SalesforceMapping · history · rollbackCliniko to SalesforceMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Tekion to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote