Migrate from FRONTU to Mailchimp

Frontu Customer maps 1:1 to a Mailchimp audience member. Email address is the unique identifier — required field in Mailchimp. First name, last name, phone, and custom properties map to merge fields on the member record. A Frontu Customer without an email address cannot become a Mailchimp member and is flagged for manual review.

Frontu Location stores service-site address data (street, city, state, postal code, country). Mailchimp has a native ADDRESS merge field type that accepts structured address components. We map Location fields to the ADDRESS merge field and optionally tag members by location name for geographic segmentation in Mailchimp.

Frontu Work Orders have no Mailchimp equivalent. We carry the most recent work order status and job type as a tag on the associated customer member (e.g., 'HVAC Service', 'Completed') and optionally store the last work order date in a DATE merge field. Historical work orders are not individually migrated — the member gets a summary tag.

Frontu task assignments and scheduling data have no Mailchimp equivalent. These records are excluded from migration. If scheduling information needs to be retained, we can create a free-text merge field storing the last task summary, but Mailchimp's model does not support task or calendar management.

Mailchimp has no technician or employee record type. Frontu technician names associated with work orders can be applied as tags on the related customer member (e.g., 'Assigned: J. Smith') for service-history reference, but there is no native employee management in Mailchimp.

Frontu asset records (equipment types, serial numbers, service intervals) have no Mailchimp equivalent. Asset summary data can be stored as a TEXT merge field on the customer member, and asset categories can be applied as tags for segmentation, but Mailchimp cannot manage asset lifecycle or service scheduling.

Frontu notes attached to a customer map to Mailchimp member notes. We preserve the full note text and timestamp. If a customer has multiple notes, they are appended to the Mailchimp member note in chronological order. Note length is limited to Mailchimp's 1,000-character member note field.

Frontu active customers map directly to Mailchimp 'Subscribed' status, allowing them to immediately receive campaigns after migration. Inactive or archived Frontu customers map to 'Unsubscribed' to ensure Mailchimp respects their opt-out decisions and prevents any future email sends. Bounced email addresses from Frontu are imported as 'Cleaned' status, which permanently suppresses those addresses in Mailchimp and prevents any re-sending attempts to invalid email accounts.

Frontu custom properties on Customer objects (e.g., 'Preferred Service Day', 'Contract Type') map to Mailchimp merge fields scoped to the destination audience. We match Frontu field data types to Mailchimp merge field types: TEXT → TEXT, number → NUMBER, date → DATE, picklist → DROPDOWN or RADIO.

Frontu labels and tags applied to customers (e.g., 'VIP Customer', 'Annual Contract', 'Referral Source') map 1:1 to Mailchimp tags on the corresponding member. Tags are applied in bulk during migration. Mailchimp tags have a 100-character name limit — longer Frontu labels are truncated.

Frontu Company name maps to the COMPANY merge field (built-in Mailchimp field) on the member record. If Frontu stores an organizational hierarchy (parent/child companies), we store parent company as a separate TEXT merge field. This keeps the customer member tied to their organization without creating separate Mailchimp records.