Migrate from Teamleader to Mailchimp

Teamleader Contact records map to Mailchimp Members. We map firstname and lastname to the FNAME and LNAME merge fields, email address to the EMAIL field (used as the Member identifier), and phone to a custom merge field. Contact status (active/inactive) does not have a direct Mailchimp equivalent; we set unsubscribed contacts as unsubscribed in Mailchimp and active contacts as subscribed, preserving engagement history as tags if the customer requests a full historical import.

Teamleader Company records do not map to a dedicated Mailchimp object. We have two strategies depending on the customer's segmentation needs: Strategy A maps the Company name to a COMPANY merge field on each Member (one-to-one through the Contact-Company relationship), suitable when each Contact belongs to one Company. Strategy B creates a Mailchimp Tag per unique Company name and applies it to all Members linked to that Company, suitable for segmentation by organization in Mailchimp campaigns. The customer selects the strategy during scoping.

Teamleader does not have a native tag object equivalent to Mailchimp's tag model, but many Teamleader implementations use the notes field or custom multi-select fields to store segmentation labels. During scoping, we identify which Teamleader fields or note patterns represent tag-equivalent data and migrate them as Mailchimp Tags. Tags with more than 30 characters are truncated to Mailchimp's tag name limit.

Teamleader custom fields defined in the 'contact' context map to Mailchimp merge fields. Mailchimp limits text merge fields to 255 characters; any Teamleader custom field exceeding this length is truncated with a note in the migration report. We use the customFieldDefinitions.list API to enumerate all custom fields per context before mapping. Merge field types are inferred from Teamleader field types: text to text, number to number, date to date, dropdown to dropdown.

Teamleader custom fields defined in the 'company' context map to Mailchimp merge fields on the Member, accessible via the COMPANY merge field relationship. Company-level custom field data is resolved through the Contact-Company link at migration time and applied to the corresponding Member merge fields. Fields exceeding 255 characters are truncated.

Teamleader Owners (sales reps) linked to Contacts do not have a Mailchimp equivalent object. We apply the owner name as a Mailchimp Tag on each Member they own, enabling the customer's team to segment by rep or send rep-specific campaigns. Alternatively, the owner name can be stored as a merge field if the customer prefers a field-based approach over tagging.

Teamleader Deals and Pipeline data have no Mailchimp equivalent. We do not import Deals. Instead, we deliver a written inventory of all open Deals with their stage, value, and associated Contact names in a CSV file, so the customer's team can recreate deal pipeline tracking in a CRM or project tool of their choosing post-migration.

These Teamleader objects have no Mailchimp equivalent. We deliver a written inventory of open Projects, outstanding Invoices, active Subscriptions, and open Tickets with associated Contact and Company names in CSV format. This inventory serves as the handoff document for the customer's admin to recreate these records in a destination CRM or accounting tool if needed. We do not import these records as Mailchimp has no schema to receive them.