Migrate from Tekion to Nutshell

90-day CRM lead window limits migration scope

Tekion's standard CRM conversion is limited to 90 days of active lead data by creation date. Leads created more than 90 days before the migration window are not included in the default export. For sales cycles that exceed 90 days — common in B2B automotive service, fleet sales, and F&I product cycles — this means historical lead records and their associated activities are excluded unless the scope is explicitly extended with Tekion. Teams should audit their open lead age distribution before migration to determine how many records fall outside the window and decide whether an extended data extraction is feasible given Tekion's API license constraints.

Automotive-specific fields have no Nutshell equivalent

Tekion stores vehicle identifiers (VIN, year, make, model), trade-in data, F&I product selections, and DMS-linked service history as custom properties on contacts, companies, and deals. Nutshell has no native automotive object model — there is no Vehicle, TradeIn, or F&I Product object. These fields can be migrated as Nutshell custom fields, but Nutshell's custom field type support (text, number, date, pick-list, currency, URL, checkbox) may not accommodate all Tekion data types (for example, structured JSON or nested objects). FlitStack surfaces each automotive field during the sample migration phase so your team can decide whether to carry it over as a custom field, archive it, or rebuild it as a linked record.

Tekion API license governs extraction scope and method

Tekion's API License and Data Sharing Agreement restricts how data can be accessed, used, and distributed. Bulk data extraction via API is subject to these license terms — the agreement prohibits using the API to build competitive products or to re-identify de-identified data. Migration tooling that operates outside the scope of the authorized API use case risks violating these terms. FlitStack accesses Tekion data through authorized API endpoints only, within the license scope, and documents the data-handling chain-of-custody so you can audit the migration against your Tekion agreement.

Nutshell rate limits on find queries affect migration batch size

Nutshell's API rate limits apply specifically to find queries that return non-stub responses — for example, findLeads() or findPeople() calls that pull full record data. Large dataset migrations that push many concurrent find requests may encounter 429 rate-limit responses, causing batch delays. FlitStack manages Nutshell API request pacing with exponential backoff and batch sizing tuned to Nutshell's documented rate-limit thresholds. For migrations exceeding 50,000 records, the migration clock extends proportionally to account for rate-limit wait time.

Workflows and automations cannot migrate between platforms

Tekion's workflow engine ties automations to DMS events (service check-in, F&I menu close, OEM promotion triggers) and AI agent actions that have no Nutshell equivalent. Nutshell's automation layer (personal email sequences, basic pipeline rules) operates at the CRM level and cannot replicate automotive DMS event triggers. The workflow definitions, conditions, and action sequences must be rebuilt in Nutshell's automation tools. FlitStack exports Tekion workflow definitions as a structured JSON file that maps each workflow trigger, condition, and action to its Nutshell equivalent — providing your admin with a rebuild reference rather than a direct migration.