Migrate from Housecall Pro to Mailchimp

Mailchimp has no job or service history object — equipment data must be flattened into merge fields

Housecall Pro's Property Profile stores equipment items as structured child records linked to a customer address, with fields for item type, make, model, serial number, and install date. Mailchimp contacts have flat custom merge fields only. FlitStack flattens each equipment item into named merge fields (EQUIP_TYPE, EQUIP_MAKE, EQUIP_MODEL, EQUIP_SERIAL, EQUIP_INSTALL) on the contact. If a customer has multiple equipment items, values are comma-separated or the most recent item is stored — FlitStack surfaces this ambiguity before migration so you can decide on a rule. Mailchimp's merge field limit per Audience is 40, so equipment-heavy accounts with many item types per customer may require selective field creation.

Job-triggered automations and service reminders do not transfer — Mailchimp automations must be rebuilt from scratch

Housecall Pro has job-triggered automations — automated customer notifications when a job is booked, when a technician is on the way, and post-job follow-up reminders. These are stored as Housecall Pro workflow configurations that are not exposed via API. Mailchimp's automation builder creates email drip sequences from contact tags, merge field conditions, and date-based triggers. There is no automated translation between Housecall Pro workflow logic and Mailchimp automation logic. FlitStack exports your Housecall Pro workflow configuration as a written reference document so your Mailchimp admin can rebuild equivalent sequences in Mailchimp's automation builder using the tags and merge fields that migrated.

Mailchimp contact pricing tier may be triggered by the migration volume — free plans cap at 500 contacts

Housecall Pro customer lists for active home service businesses often exceed 500 contacts, particularly for companies that have been operating for more than a year. Mailchimp's free plan caps at 500 contacts per Audience. The migration will fail or require splitting across multiple audiences if your Housecall Pro customer count exceeds the Mailchimp plan limit. FlitStack flags the contact count against your current Mailchimp plan before migration begins and recommends a plan upgrade or audience split. This is a billing decision on the Mailchimp side, not a data loss risk — but it must be resolved before the migration runs.

Housecall Pro leads and customers share a unified API record type — distinguishing them in Mailchimp requires a tagging strategy

Housecall Pro does not maintain separate API objects for leads and customers — both are returned from the /customers endpoint with a lead_source field distinguishing inbound leads from established customers. Mailchimp contacts do not have a native lead/customer flag. FlitStack maps HCP leads to Mailchimp contacts and applies a LEAD_SOURCE tag so they can be isolated in a dedicated Mailchimp segment. However, Mailchimp's tag-based segmentation cannot enforce access controls or separate billing audiences — if you need hard isolation between leads and customers, FlitStack recommends separate Mailchimp Audiences with a shared equipment merge field schema.

Housecall Pro customer addresses lack geocoding parity with Mailchimp's address validation

Mailchimp performs basic address validation on ADDRESS merge field submissions to ensure deliverability and deliverability metrics. Housecall Pro stores customer addresses as free-text strings that may include apartment numbers, unit designations, or directional street suffixes (e.g., 'N', 'SE'). Mailchimp's address validation can reject or flag addresses with unusual formatting. FlitStack normalizes HCP address strings before mapping to Mailchimp's structured ADDRESS field, but any addresses that fail Mailchimp's validation are flagged in the pre-migration report for manual review before the contact records are committed.