Migrate from Connect Field Service to Mailchimp

Connect Field Service Contact records map directly to Mailchimp audience members. Each Contact becomes one Member record. Email address is the unique identifier used for deduplication. Unsubscribed contacts in Salesforce can be imported as unsubscribed in Mailchimp to preserve suppression-list compliance.

Account name and billing/service address map to Mailchimp merge fields on the Member record. Mailchimp does not have a native Account object — company context lives as a text or address merge field on the contact. Multi-address accounts take the primary service address by default.

Connect Field Service custom fields on Contact (beyond standard fields like phone and email) require Mailchimp merge field creation. Mailchimp limits merge fields to 255 characters — long-text area fields from Salesforce cannot map directly and must be truncated or stored as tags.

WorkOrder records have no native Mailchimp equivalent. We encode work‑order status (Completed, Cancelled, In Progress), service type, and priority as Mailchimp tags on the associated Contact record, allowing marketing teams to segment contacts by service history without importing the full WorkOrder object. When a contact has multiple work orders, each status generates a separate tag, so segment filters can count tags to approximate recency or volume of service activity.

Service appointment scheduling data cannot map to Mailchimp because the platform lacks a scheduling model. Appointment outcomes (Completed, No Access, Rescheduled) and service‑type labels are encoded as Mailchimp tags on the Contact record, enabling segmentation based on interaction history. When a contact has appointments, outcome and service type generate a tag, so segment filters can count tags to approximate variety or recency, while scheduling windows and assignments are not preserved.

Asset records (equipment under service contract) have no Mailchimp equivalent. The primary asset name or serial number migrates as a text merge field on the Contact for reference — asset relationship hierarchy and maintenance history are not portable to Mailchimp.

Connect Field Service account service addresses (street, city, state, postal code, country) map to Mailchimp's built‑in ADDRESS merge field block, preserving location data for each contact. Geolocation coordinates from FSL (latitude/longitude) are not portable, as Mailchimp does not store coordinate values; only text address components transfer. After migration, you can use the address fields to create city or region‑based segments, but any clustering based on coordinates requires a geocoding step.

Technician and dispatcher User records in Connect Field Service have no Mailchimp equivalent, so internal team member data does not migrate. Only customer‑facing Contact records are exported to the Mailchimp audience. If you need to include internal staff in Mailchimp communications, you must create a separate audience manually or import them from another source; the migration scope is limited to the Contact entity.

Scheduling policies, dispatch configuration, and territory management in Connect Field Service are stored as Salesforce FSL schema objects (FSL__Scheduling_Policy__c, ServiceTerritory, and related entities) with no Mailchimp equivalent. These objects define windows, technician assignment rules, and logic that cannot be expressed in Mailchimp's audience model, so they do not migrate. After moving to Mailchimp, you will need to manage scheduling and dispatch operations in a field‑service tool if capabilities are required.

The original Salesforce Contact ID is stored as a custom merge field (named SOURCE_SYSTEM_ID) on each Mailchimp member for traceability and delta‑run de‑duplication. This field lets the migration tool match updated source records to existing members on subsequent runs, enabling incremental syncs without creating duplicate contacts. You can also use the SOURCE_SYSTEM_ID merge field to link Mailchimp member data back to the original Salesforce record for reporting or reconciliation.