Migrate from Tekion to Mailchimp

Tekion customer records are mapped to Mailchimp subscribers using the email address as the linking key. When a Tekion customer contains a valid email, FlitStack AI creates a corresponding Mailchimp subscriber with all standard merge fields populated. Any Tekion customer lacking an email address is flagged in the pre‑migration audit and reported as an exclusion, because Mailchimp requires an email for every subscriber record.

Tekion stores first and last name as separate fields on each contact record. FlitStack AI extracts those values and loads them into Mailchimp's built‑in FNAME and LNAME merge tags, which are present by default in every Mailchimp audience. These fields enable dynamic personalization in subject lines, preview text, and body copy, allowing you to address recipients by name without additional configuration.

The email field is the primary key in Mailchimp. Each unique email address creates one subscriber. If the same email appears on multiple Tekion records (e.g., a customer who is also a co-buyer), Mailchimp deduplicates to a single subscriber and the additional Tekion associations are preserved as tags or custom fields.

Tekion records each customer's phone number as a free‑form string. Because Mailchimp does not include a native phone field, FlitStack AI creates a custom PHONE merge field in the target Mailchimp audience before the migration run. During data load, Tekion phone values populate the PHONE field so that SMS‑opt‑in campaigns and phone‑based segmentation can be enabled in Mailchimp without manual re‑entry.

Tekion vehicle records are many-to-one with customers (a customer can own multiple vehicles). In Mailchimp, each vehicle becomes a set of custom merge fields on the subscriber record plus a tag identifying the vehicle relationship. For customers with multiple vehicles, additional vehicles are added as additional tags — the primary vehicle populates the merge fields directly.

Tekion deal records carry deal name, amount, and stage. In Mailchimp, the deal stage becomes a tag on the subscriber (e.g., 'Deal Stage: F&I Product Presentation') and the deal amount and close date are stored as custom merge fields. Mailchimp's tag model lets you segment by deal stage for targeted re-engagement campaigns.

Tekion leads that have not yet converted to customers map to Mailchimp subscribers with a 'Lead' tag. The lead creation date is preserved as a custom datetime merge field. Lead status (New, Working, Unqualified) maps to Mailchimp tags for segmentation.

Tekion service clients who are not customers (service-only accounts) become Mailchimp subscribers tagged as 'Service Client'. The most recent service date is preserved as a custom merge field. Service appointment history can be stored as additional tags per service event.

Tekion assigns owner users to customers, leads, and deals. Mailchimp has no native owner concept. We preserve the owner email as a custom merge field (OwnerEmail) so users can reference which Tekion team member was assigned without rebuilding a CRM assignment system.

Tekion DMS workflows (service scheduling automations, lead routing rules, F&I product presentation sequences) have no Mailchimp equivalent. These operational automations are specific to dealer process management and must be rebuilt in Mailchimp's Customer Journeys or documented manually as reference for your team.

Tekion attaches F&I product details—such as extended warranty, GAP coverage, paint protection, or tire‑and‑wheel packages—to a deal record. FlitStack AI converts each product attachment into either a Mailchimp tag (e.g., F&I: Extended Warranty) or a custom merge field for quick reference. Because Mailchimp lacks a native F&I module, these tags and fields preserve product context purely for informational reporting and segmentation.

Tekion stores supporting documents—service invoices, F&I contracts, vehicle images, and signed forms—against customers, deals, and service records. Mailchimp's subscriber model is text‑only and does not accept binary file attachments, so FlitStack AI excludes all document references from the migration payload. Teams should export essential contracts and images directly from Tekion's UI before the offboarding date.