Migrate from Jobber to Mailchimp

Mailchimp free plan caps at 500 contacts — audience split planning required for larger client lists

Mailchimp's free plan limits audiences to 500 contacts. Jobber clients with more than 500 total email addresses require an audience split strategy before migration — either by service type (commercial vs. residential), region, or date range. We audit your client count before migration and deliver a split plan. Failure to split results in a Mailchimp API rejection at import time. The paid plan you choose determines whether you can have multiple audiences or need to merge and segment internally.

Unsubscribed clients from Jobber integrations must be imported as Mailchimp suppressions

Mailchimp's API does not return a full list of previously unsubscribed contacts for re-import. If you previously synced Jobber clients to Mailchimp and some contacts unsubscribed, those unsubscribe states must be preserved separately and imported as a suppression list before the migration runs. Failing to do this means previously unsubscribed contacts receive your first post-migration campaign — triggering bounce complaints and damaging sender reputation. We require a pre-migration suppression list export and validate it against the Jobber client list.

Mailchimp deduplicates by email address — shared emails across Jobber clients collapse silently

Mailchimp enforces one subscriber per email address within an audience. If two Jobber clients share the same email (common in household or business accounts where one person manages multiple properties), Mailchimp merges them silently into a single contact on import. The secondary client's phone, address, and custom field data is lost unless we detect the collision pre-import. We run a shared-email audit on your Jobber export and surface each collision with a resolution choice — keep the primary record, create a secondary audience, or append a suffix to one email.

Jobber property addresses decompose to Mailchimp's fixed 5-field address block

Mailchimp's address merge fields use a fixed five-field structure (street, city, state/province, postal code, country). Jobber properties sometimes store multi-line addresses, unit numbers, or cross-streets that don't map cleanly to this structure. We split address_line_1 and address_line_2 into ADDR1 and ADDR2, but any freeform delivery instructions (e.g., 'Ring doorbell twice', 'Leave at back gate') stored as custom fields are not imported to Mailchimp's address block and must be added manually or as a text merge field.

Mailchimp has no job history, invoice, or quote objects — that data becomes opaque reference JSON

Jobber stores rich operational history (job visits, line items, payment amounts, quote versions) that has no structural equivalent in Mailchimp's contact model. We export this data as a JSON payload stored in a custom field on the contact record. Mailchimp's UI does not render this data — it is only visible via API or a custom integration. This is a fundamental model gap, not a mapping limitation. If operational history visibility is required inside Mailchimp, a custom development effort is needed beyond the scope of standard migration.