Migrate from Planfix to Mailchimp

Planfix Contact records map directly to Mailchimp Subscribers. The contact's email address becomes the subscriber email and serves as the dedupe key during import. We validate each email for Mailchimp-compliant format (no UTF-8 in prefix, valid domain, no typos in common domains) and flag malformed addresses before import to prevent bounce spikes that damage sender reputation.

Planfix Contact name fields map to Mailchimp's standard FNAME and LNAME merge fields on the target Audience. We create these merge fields via the Mailchimp API before importing any subscribers.

Planfix Contact phone number maps to a custom PHONE merge field if present on the source record. This field is created on the destination Audience during schema setup. Note that SMS marketing features in Mailchimp require a separate integration with Mailchimp's SMS product.

Planfix Contact address fields (street, city, state, postal code, country) map to Mailchimp's structured ADDRESS merge field. We split the Planfix address into Mailchimp's required addr1, city, state, zip, and country components.

Planfix custom fields on Contact (text, number, date, dropdown, checkbox) map to Mailchimp Merge Fields of equivalent type. Text custom fields become text merge fields, dates become date merge fields, and dropdowns become dropdown merge fields. We snapshot the Planfix workspace field schema first because every workspace has a different custom field configuration. Mailchimp limits audiences to 40 merge fields, so we prioritize the fields the customer selects during scoping.

Planfix tags applied to Contacts transfer to Mailchimp Tags on the subscriber record. Tags drive segmentation in Mailchimp for targeted campaigns. We preserve the tag taxonomy from Planfix, noting that the customer may want to restructure tags into a Mailchimp-specific taxonomy post-migration.

Planfix Company records can map to a custom COMPANY merge field on the Mailchimp Subscriber, or to Mailchimp Groups if the customer uses Group-based segmentation. We determine the strategy during scoping based on whether the customer needs to segment by company or just preserve company as a data attribute.

Planfix contacts with email addresses that have bounced or unsubscribed (tracked in Planfix's CRM) map to the corresponding Mailchimp status (bounced, unsubscribed) to maintain consent records. We do not set subscribed status for bounced contacts. Plain contacts with no tracking data default to subscribed.