Migrate from Checkbox to Mailchimp

Checkbox Contact Profiles map directly to Mailchimp Members. Email address is the unique key — matching by email resolves duplicate members. Status (subscribed/unsubscribed) maps from Checkbox's contact property or survey response opt-in field. If multiple Checkbox contacts share the same email, we keep the most recent record and merge custom field values, flagging duplicates for review.

Checkbox custom fields of type text, number, and date export with their field labels. They become Mailchimp merge fields with matching names. Mailchimp limits merge fields to 255 characters — longer values are truncated and flagged in the migration report.

Checkbox exports checkbox-group answers as separate 0/1 columns per option. FlitStack consolidates these into a single comma-separated value for a text merge field OR applies tags per selected option — your team chooses the strategy before migration runs. If you opt for tags, each selected option generates a distinct Mailchimp tag that can be used for segment filtering and targeted campaigns.

Survey response bodies (form answers, approval comments, intake details) do not map to Mailchimp. Response metadata (submission timestamp, respondent email) migrates as member activity notes or merge fields. Survey logic must be rebuilt as Mailchimp customer journeys. Your team should document each survey's purpose and decision points so that equivalent automation can be designed in Mailchimp's Customer Journey builder.

Checkbox's conditional routing, SLA timers, and approval assignments have no Mailchimp analogue. We export workflow definitions as a JSON reference document for your team to rebuild in Mailchimp Customer Journeys. This export includes step sequences, condition branches, and assignee rules, providing a blueprint for manual recreation of the workflow logic.

Original survey submission dates preserve as a datetime merge field on the Mailchimp Member. This maintains reporting continuity for historical context even though Mailchimp engagement tracking starts fresh. If you have multiple surveys, the earliest submission date is stored, while later dates can be added as additional merge fields for detailed analysis.

If Checkbox stores company names on contact profiles, these migrate as a text merge field or a company-specific tag in Mailchimp. Mailchimp has no native company object — hierarchy and account linkage require custom field handling. We recommend defining a consistent naming convention for company tags to simplify segmentation across multiple brands or product lines.

Checkbox contact tags transfer directly to Mailchimp Tags. Tags are preserved for segmentation but do not carry workflow context from Checkbox — the business meaning of tags should be documented for Mailchimp segmentation. We advise creating a tag glossary that defines each label's purpose and usage rules to ensure consistent segmentation across campaigns.

Contacts marked as unsubscribed or opted out in Checkbox map to Mailchimp's Unsubscribed status. We import suppression data first to ensure bounced and cleaned addresses do not reactivate during member migration. After the suppression list is loaded, any subsequent member imports respect these statuses, preventing accidental reactivation of contacts who previously opted out.

Files attached to Checkbox survey responses do not migrate. We document attachment filenames and download locations separately so your team can decide whether to re-upload to a linked storage system or recreate the data in Mailchimp's supported formats. We also provide a manifest CSV listing each file's original survey, response ID, and storage path for straightforward reference during re-upload.