Migrate from WorkBuddy to Mailchimp

Job and work order records have no Mailchimp equivalent and are excluded from migration

WorkBuddy organizes field-service operations around Jobs and Work Orders — these records carry job status, scheduling, parts, and technician assignments. Mailchimp has no concept of work orders; the platform manages subscriber records and email campaigns only. Job history cannot be imported into Mailchimp. FlitStack can export job history as a separate reference CSV before migration, but this data lives outside Mailchimp's subscriber model and must be used for manual context or rebuilt via a separate integration. Marketing teams using job history for customer segmentation should export job count or last-job-date as custom merge fields rather than trying to replicate the job record structure.

Mailchimp counts every contact toward billing including unsubscribed and cleaned records

Mailchimp pricing is based on total contact count within each Audience, and it counts unsubscribed and cleaned contacts toward the billing limit. WorkBuddy may have contacts that are inactive, bounced, or manually suppressed that will inflate Mailchimp's contact count if migrated as-is. FlitStack flags unsubscribed and bounced WorkBuddy contacts during import and marks them as Non-Subscribed or Cleaned in Mailchimp, but they still count toward your Mailchimp plan tier. Teams should clean their WorkBuddy contact list before migration or set a deduplication rule to avoid paying for contacts that should have been suppressed.

WorkBuddy custom fields require manual merge field declaration in Mailchimp before import

WorkBuddy supports custom fields on contacts and companies, but Mailchimp requires merge fields to be declared in the Audience settings before data can populate them. Each merge field must be created individually in Mailchimp's Audience settings interface or via API with a defined field type (text, number, date, phone, address, URL). WorkBuddy accounts with many custom fields require upfront planning — Mailchimp caps merge fields at 40 per Audience. FlitStack declares merge fields via the Mailchimp API as part of the migration setup step, but the mapping of WorkBuddy field types to Mailchimp field types must be confirmed to avoid data truncation (e.g., long-text WorkBuddy fields cannot map to Mailchimp's text fields if they exceed character limits).

Contact-to-company associations in WorkBuddy become tags or merge fields in Mailchimp with no relational integrity

WorkBuddy links Contacts to Companies using a many-to-many association model — a single contact can belong to multiple companies. Mailchimp subscribers belong to exactly one Audience with no native concept of cross-contact relationships. Company affiliation is typically stored as a merge field or tag, losing the N:N structure. If a WorkBuddy contact is associated with multiple companies, Mailchimp can only reflect one company name in a merge field; the rest are lost or must be handled as tags. FlitStack defaults to using the primary (most recently modified) company association for the merge field and applies secondary companies as tags, but your team should review this mapping before the full run.

Automation workflows, job-stage triggers, and scheduling rules do not migrate and must be rebuilt

WorkBuddy workflow rules handle field-service process logic such as job-stage notifications, technician assignment triggers, and scheduling escalations. Mailchimp Customer Journeys handle email automation based on subscriber actions, date conditions, and segment membership — a fundamentally different paradigm. Workflows built in WorkBuddy cannot be exported in a format compatible with Mailchimp. FlitStack migrates data only. Your team should export WorkBuddy workflow definitions as a reference document before migration and plan to rebuild customer-facing email automations in Mailchimp's Customer Journeys builder after go-live.