Migrate from Method:Field Services to Mailchimp

Method Contacts migrate to Mailchimp Contacts within the target Audience. Email is the required primary identifier. First name, last name, phone, and address fields map to Mailchimp's FNAME, LNAME, PHONE, and ADDRESS merge fields. Contacts without an email address are flagged for manual review — Mailchimp requires a valid email for audience membership.

Method's Company records do not have a native Mailchimp equivalent — a Company Name merge field (COMPANY or MMERGE1) captures the parent organization on each contact record. Company address, industry, and employee count also map to custom merge fields so campaigns can reference service-client context per subscriber.

Work Order status (Scheduled, In Progress, Completed, Cancelled) maps to a STATUS merge field. Service type and job category map to Mailchimp tags applied per contact — for example, 'HVAC Installation', 'Preventive Maintenance', or 'Emergency Repair' — enabling segmentation by service history for targeted email campaigns.

The Method technician assigned to a Work Order migrates as a TECHNICIAN tag on the customer contact. Multiple work orders for the same contact accumulate multiple technician tags. This lets Mailchimp segment audiences by 'last serviced by' for follow-up drip sequences or technician-specific outreach.

Work Order site address maps to Mailchimp's native ADDRESS merge field (supports street, city, state, zip, country). If Method stores multiple sites per customer, additional address fields migrate to custom merge fields (SITE_ADDRESS_1, SITE_ADDRESS_2) with site labels as values. These custom fields enable segmentation by location in campaigns, allowing targeted service reminders or promotions based on the customer's nearest site. Site labels also support internal routing of service requests.

Open estimates map to an ESTIMATE_STATUS merge field with values like 'Pending', 'Accepted', 'Declined'. Accepted estimates trigger a tag ('Quote Accepted') for lifecycle segmentation in Mailchimp. Rejected estimates can receive a 'Follow-Up Needed' tag to drive a re-engagement campaign sequence.

Invoice status and payment history map to tags on the contact — 'Invoice Paid', 'Overdue', 'Payment Plan'. Total invoice amount can populate a LIFETIME_VALUE merge field for RFM (recency, frequency, monetary) segmentation. This turns Method's QuickBooks-synced transaction history into Mailchimp segmentation criteria.

Method allows unlimited custom tables with custom fields per table. Mailchimp caps merge fields at 50 per Audience. We audit all Method custom fields before migration and consolidate related fields into structured merge fields — for example, combining 'Certification Type' and 'Certification Expiry' into a single structured text field. Excess fields are flagged for prioritization.

Method syncs invoices, payments, and customer records to QuickBooks — this accounting metadata has no Mailchimp equivalent. We preserve QuickBooks Customer ID and last sync timestamp as reference merge fields (QB_CUSTOMER_ID, QB_LAST_SYNC) for audit trail purposes, but Mailchimp cannot process or display this data natively.

Method's contact owner (the internal user who owns the customer relationship) maps to an ASSIGNED_REP tag on the Mailchimp contact. This supports internal routing of email campaigns or enables 'Your service rep' personalization tokens in Mailchimp templates. Unassigned contacts receive a 'Unassigned' tag for follow-up assignment post-migration.

Method assigns Dispatcher or Field Crew roles based on installed packs. These roles are internal operational metadata with no Mailchimp equivalent — a customer in Method does not inherently carry a 'Dispatcher' flag. We do not migrate role metadata to contacts, as it represents internal staffing rather than customer attributes.

Method stores email and transaction templates tied to its QuickBooks sync engine. Mailchimp templates are HTML-based campaign builders with different content models. Template content does not migrate — we export Method template names and usage context as a rebuild reference for your Mailchimp admin to recreate in Mailchimp's template editor.