Migrate from InTouch to Mailchimp

InTouch contacts migrate directly to Mailchimp subscribers. Each InTouch contact becomes one subscriber record in the target Mailchimp audience with email address, name, and phone preserved as the subscriber's primary fields. All additional InTouch contact fields such as job title, address, and custom fields map to Mailchimp merge fields on the subscriber record. Contacts without an email address are flagged for review to prevent invalid Mailchimp records.

InTouch has a standalone Company object. Mailchimp has no company entity — company name, domain, industry, employee count, and revenue migrate as merge fields (COMPANY_NAME, COMPANY_INDUSTRY, EMPLOYEE_COUNT) on each related subscriber record. If a contact is associated with multiple companies, the primary company is selected by InTouch's primary flag, and its details populate the subscriber merge fields. Additional company associations are recorded as tags for reference.

InTouch Deals have name, amount, stage, close date, owner, and priority. Mailchimp has no deal object. All deal fields migrate as custom merge fields on the associated subscriber record — deal_name becomes DEAL_NAME, amount becomes DEAL_AMOUNT, and so on. The deal owner is stored as a tag to preserve attribution, and pipeline stage information is encoded in a separate merge field for clear segmentation.

InTouch pipelines and pipeline stages have no Mailchimp equivalent. We map each pipeline name to a Mailchimp tag prefix and stage values to sub-tags so deal pipeline context is searchable on the subscriber record. This approach preserves the hierarchical relationship between pipelines and stages while keeping the subscriber record clean and queryable in Mailchimp's segmentation UI.

InTouch email activities (subject, body, timestamp, owner) migrate as Mailchimp tags labelled 'Email: [subject]' with the timestamp preserved in the tag note field. The full email body is not stored on the subscriber — a summary tag signals email engagement history.

InTouch call logs migrate as Mailchimp tags labelled 'Call: [date]' with outcome and duration preserved in the tag note. Call history is surfaced as engagement context on the subscriber rather than a native log. If multiple calls exist for a contact, each call receives its own tag, allowing you to filter subscribers based on call recency or outcome without cluttering the record.

InTouch meeting records (subject, date, attendees, outcome) migrate as Mailchimp tags labelled 'Meeting: [date]' with meeting outcome preserved in the tag note for follow-up visibility. When a contact has multiple meetings, each meeting generates a distinct tag, so you can segment your audience by recent meeting activity or by specific meeting outcomes such as demo, discovery, or proposal.

InTouch notes attached to contacts or deals migrate as Mailchimp tags labelled 'Note' with a timestamp. The full note content is not stored — the tag signals that a note exists so your team can reference the source system. All note details are preserved in FlitStack's audit log, where they can be reviewed or exported alongside the migration report.

InTouch custom fields (text, number, date, dropdown) map to Mailchimp merge fields of the matching type. Mailchimp enforces field-type constraints — text fields become text merge fields, date fields become date merge fields, and pick-list values require dropdown merge field setup.

InTouch owners (sales reps) have no Mailchimp equivalent. Owner name migrates as a 'Owner: [name]' tag on each subscriber so team attribution is visible on the contact record post-migration. If a contact has multiple owners over time, the most recent owner is used as the tag value, and historical ownership is recorded in the audit log for traceability.

InTouch automation workflows, drip sequences, and email sequences have no Mailchimp equivalent. These must be rebuilt in Mailchimp Customer Journey Builder. FlitStack AI exports workflow definitions as a structured document your team can use as a rebuild reference. The exported document includes trigger types, condition branches, step order, and email content references, giving your Mailchimp setup team a clear blueprint to replicate the original logic.