Migrate from Field Squared to Mailchimp

Field Squared contacts map 1:1 to Mailchimp audience members. Email address is the unique identifier — contacts without an email are flagged for manual review before migration. Original create date migrates as a merge field since Mailchimp sets CreatedAt at import time.

Field Squared company names migrate as a merge field (COMPANY_NAME) and can also apply as a Mailchimp tag per company for segment-based campaigns. Multi-company contacts (Field Squared N:N) get the primary company tagged; secondary companies preserved as a comma-separated merge field value.

Work order summary (WO number, status, asset name, completion date) migrates as a contact note or as structured custom fields on the Mailchimp member. Full work order history is preserved for reference but does not create separate Mailchimp objects — Mailchimp has no work-order equivalent.

Task name, scheduled date, and status migrate as contact notes on the associated Field Squared contact. Tasks without an associated contact are flagged — these may represent internal dispatch records that have no Mailchimp audience member target. If a task belongs to an internal project with no customer link, it will be noted for manual review before the final audience is finalized.

Mailchimp has no technician or employee object. Technician assignments from Field Squared are preserved as tags (e.g., TECH: John Smith) or as a merge field (PRIMARY_TECH) on the customer contact so segment filters can group customers by assigned technician. These tags enable you to send targeted service updates or maintenance reminders based on the technician who typically handles each account.

Field Squared asset name and serial number migrate as merge fields (ASSET_NAME, ASSET_SERIAL) on the associated contact. If the asset has a status (active, retired), that value maps to a tag for filtering in Mailchimp campaigns. Asset information helps you segment audiences for warranty follow-ups or service renewal offers based on the equipment each contact owns.

Field Squared custom fields created in App Builder map to Mailchimp merge fields by type — text to text, number to number, date to date, dropdown to dropdown. Multi-select pick-lists in Field Squared become comma-separated text values in Mailchimp. Unsupported field types (e.g., media attachments) migrate as a note reference.

Field Squared service agreement status (Active, Expired, Pending) maps to Mailchimp tags and a merge field (SVC_STATUS). Active agreements tag the contact as SERVICE_ACTIVE; expired agreements tag as SERVICE_EXPIRED for re-engagement campaign targeting. You can also create automation triggers that fire when a contact’s service status changes, such as sending a renewal reminder when a service agreement nears expiration.

File attachments in Field Squared cannot migrate to Mailchimp files — Mailchimp does not have a file attachment model per contact. Document links or references are preserved as a note on the contact pointing to the original Field Squared document storage URL.

Field Squared internal users and owners (dispatchers, technicians) who are not customer contacts do not have a Mailchimp target. If internal users are also contacts (e.g., they receive service communications), they migrate as audience members; otherwise they are excluded from the audience migration.