Migrate from Swivl Tech to Mailchimp

Mailchimp has no native job, invoice, or work order object

Swivl Tech stores field service data (jobs, estimates, invoices, scheduling) as structured records linked to contacts. Mailchimp is an email marketing platform with a flat contact model — Members have merge fields and tags but no child objects for work orders or invoices. We encode the most recent job and estimate data as custom merge fields on each contact, and append job history as a structured note. Full invoice line-item history, scheduling data, and technician dispatch assignments have no Mailchimp destination and are not migrated. The marketing team should rebuild service follow-up sequences as Mailchimp automations triggered by the custom merge field values set during import.

Contacts without a valid email address cannot be imported

Mailchimp's audience model requires a valid email address for every Member record. Swivl contacts that lack an email field are flagged during the pre-import validation step and held in a separate report for manual review. These records cannot be bulk-imported through Mailchimp's standard import path. The migration audit log captures all flagged records so the team can collect missing email addresses and import them in a follow-on batch. Attempting to import contacts with invalid or blank email addresses will cause the import job to fail or produce hard bounces that damage the audience's sender reputation.

Swivl custom properties require Mailchimp merge field pre-creation

Swivl supports custom properties on contacts and jobs that do not map to Mailchimp's standard merge field set (FNAME, LNAME, EMAIL, PHONE, ADDRESS, COMPANY). Before the bulk import runs, our team creates all required custom merge fields in the Mailchimp audience (Settings > Audience fields). Mailchimp imposes a limit on the total number of custom merge fields per audience (200 at the Standard tier). Swivl setups with more than 50 custom contact properties may require the team to prioritize the highest-value fields for migration and archive the remainder as a contact note.

Swivl automations (scheduling, dispatch, routing) have no Mailchimp equivalent

Swivl Tech's workflow engine handles job scheduling, technician dispatch, and field routing automations that are tightly coupled to Swivl's operational data model. These automations cannot be imported into Mailchimp because Mailchimp's automation builder is designed for email sequences (welcome emails, abandoned cart triggers, birthday sends), not field service scheduling. We export the Swivl automation definitions as a written reference document so the Mailchimp admin can rebuild relevant marketing automations (e.g., a post-job thank-you sequence, a service reminder, a re-engagement campaign for dormant customers) using Mailchimp's automation templates.

Mailchimp's subscriber-based pricing means migrated contacts affect billing immediately

Swivl Tech's flat-rate pricing model is independent of contact count. Mailchimp bills based on total subscriber count across all audiences. When contacts are migrated from Swivl into a Mailchimp audience, they immediately count toward the Mailchimp plan tier. Teams migrating large Swivl contact lists (e.g., 10,000+ contacts with a high proportion of residential customers) should audit the Mailchimp plan tier before migration to avoid a billing surprise in the first month after go-live. Inactive Swivl contacts (no job history, no estimate in the past 12 months) can be excluded from the migration and imported later as a separate audience.