Migrate from Zuper to Mailchimp

Zuper Customers map to Mailchimp Members. Email address serves as the unique identifier — Mailchimp requires a valid email for each member record. Customers without email addresses cannot be imported automatically and are flagged during pre-migration audits for manual review before the migration execution begins.

Zuper Company records do not have standalone equivalents in Mailchimp. Company name, address, and industry values are migrated as custom merge fields attached to Member records. Multiple Zuper customers linked to the same Company will have matching merge field values applied.

Zuper customer tags transfer on a one-to-one basis to Mailchimp Tags since both systems use flat, non-hierarchical tag structures. Tags created for job-type categorization or priority levels in Zuper appear as standard Mailchimp tags for segmentation and targeting.

Zuper custom fields on Customer objects (e.g., custom pick-lists, date fields, text fields) require Mailchimp merge fields. Mailchimp supports a limited field-type set — Zuper multi-select, currency, or boolean fields may need transformation to text or require manual setup in Mailchimp before migration.

Zuper Jobs and Work Orders are field-service records with no Mailchimp equivalent. Job history, status, assigned technician, parts used, and job notes do not migrate. This is disclosed explicitly — teams needing this context should retain Zuper access or export job history to a separate system.

Zuper Teams and Users (technicians, dispatchers) are internal records with no Mailchimp counterpart. User assignment on jobs does not transfer. Mailchimp's user model is account-level (admin, author, viewer) and unrelated to customer contact records.

Zuper scheduling and appointment data (start time, end time, location, site) has no Mailchimp equivalent. Mailchimp sends campaigns at a scheduled time but does not store appointment or visit data on contact records.

Zuper timesheet and time-off records are internal operational data with no Mailchimp counterpart. They do not map to any Mailchimp object or merge field and are excluded from migration scope entirely.

Zuper Quotes and Proposals are sales documents tied to jobs. Mailchimp has no quote or proposal object. Quote line items, pricing, and proposal status are not migrated — teams should export these from Zuper as PDFs if needed for records.

Zuper Site records (address, city, state, zip, location coordinates) transfer to Mailchimp's native address merge fields (ADDR1, CITY, STATE, ZIP, COUNTRY). If a Zuper customer has multiple sites, only the primary site address migrates — secondary sites require a custom text merge field.

Zuper Workflow Builder automations (triggers, conditions, action nodes) have no Mailchimp equivalent and cannot be migrated in any exportable format. FlitStack exports workflow definitions as a reference JSON so your Mailchimp admin can rebuild them in Customer Journeys using the original logic as a guide.

Zuper customer suppression records (opted-out emails, hard bounces from Zuper email sends) migrate to Mailchimp's Suppression List. This ensures Mailchimp does not re-email contacts who previously unsubscribed in Zuper, maintaining deliverability and CAN-SPAM compliance across your migrated audience.