Migrate from Formitize to Mailchimp

Formitize contacts map 1:1 to Mailchimp audience members. The contact's email address serves as the primary key for the migration — FlitStack resolves each Formitize email to a corresponding Mailchimp member record, creating new members where no match exists or updating existing ones by email match during the import process.

Formitize clients represent businesses associated with contacts. Since Mailchimp has no native client-account object, FlitStack maps each unique client name to a Mailchimp tag that gets applied to all contacts belonging to that client. This approach preserves the original grouping relationship from Formitize for segmentation and filtering purposes.

Every Formitize custom contact field becomes a Mailchimp merge field of the corresponding type. Text fields become text merge fields, date fields become date merge fields, and number fields become number merge fields — all created in the Mailchimp audience before any data import begins.

Formitize pick-list custom fields migrate to Mailchimp merge fields with identical option values maintained. Each Formitize pick-list value is created as a merge field option in Mailchimp so that email templates can reference the values for personalization and conditional content without requiring manual re-entry of the options.

Formitize active contacts are mapped to Mailchimp subscribed status to ensure they receive campaigns. Formitize inactive or deleted contacts are mapped to unsubscribed status in Mailchimp to prevent accidentally mailing outdated or unwanted records during the migration.

Formitize jobs, service records, and job-linked notes have no email-marketing analogue in Mailchimp's contact-centric model. These records are documented in the migration plan as reference-only exports, and your team decides whether to archive them separately or rebuild service-history summaries as Mailchimp tags for future reference.

Formitize form submissions represent operationally specific records that do not map cleanly to Mailchimp's contact model. Form submission data is exported as a separate reference file for archival purposes. Mailchimp signup forms are set up independently after the migration using Mailchimp's native form builder tools.

Formitize quotes and invoices are billing documents with no email marketing counterpart in Mailchimp's feature set. These records remain out of scope for the Mailchimp migration — they stay in Formitize or can be migrated separately via a billing-system export if your team requires that data in another platform.

Formitize Workflows automate job routing, compliance tasks, and multi-step business processes that cannot directly translate to Mailchimp's email-trigger automation model. FlitStack exports the workflow definitions as a JSON reference file so your team can manually evaluate and map the business logic to appropriate Mailchimp customer journeys.

Formitize assets represent physical equipment or inventory items tracked in connection with service jobs. Mailchimp's platform has no asset object or inventory tracking capability. Asset data is exported as a reference CSV file for archival purposes — it is not imported into the Mailchimp audience.