Migrate from Salesforce Field Service to Mailchimp

Salesforce Contact maps directly to a Mailchimp subscriber by email address. Each Contact email field becomes the Mailchimp subscriber key. FirstName, LastName, Email, Phone, and Title all have Mailchimp merge field equivalents (FNAME, LNAME, EMAIL, PHONE, COMPNAME) and map without transformation. Duplicate email addresses across contacts in Salesforce are flagged and de-duplicated before loading.

Salesforce Account data (Name, Industry, Website, NumberOfEmployees) migrates as merge fields on the Mailchimp subscriber record attached to the primary Contact. Account.Name populates the COMPANY merge field. Industry maps to a value-mapped custom merge field since Mailchimp pick-list values must be entered exactly as they appear. Parent Account relationships do not translate — Mailchimp has no hierarchical account model.

WorkOrder records do not have a Mailchimp equivalent object. FlitStack AI extracts WorkOrder status (New, In Progress, Closed) and Work Order Type to generate Mailchimp tags applied to the related Contact subscriber. Tags like 'Service-Customer', 'Install-Pending', or 'Maintenance-Active' enable segmentation in Mailchimp campaigns. Work order line items, parts, and pricing do not migrate.

ServiceAppointment records have no Mailchimp equivalent. However, ScheduledServiceDate and actual arrival status (FSL__ArrivalTime__c in Salesforce Field Service) are mapped to a Mailchimp tag or a date-typed merge field (SCHEDULED_DATE) on the related Contact subscriber. This lets marketers target subscribers with upcoming service appointments in a campaign.

ServiceResource records (technician profiles) do not become Mailchimp subscribers. Instead, the ServiceResource's related WorkOrders and ServiceAppointments determine which tags are applied to the customer Contact. The technician's skill set and region can generate tags like 'Premium-Tech-Region-West' on the customer record for segmentation.

Salesforce Field Service often uses a custom Product or Service Resource Inventory object. Mailchimp has no inventory or product catalog. We surface these as descriptive tags on the Contact (e.g., 'ProductBundle-Enterprise') for campaign targeting but do not recreate the product data model in Mailchimp.

Call logs, email tasks, and meeting events on a Contact in Salesforce Field Service have no Mailchimp analogue. Mailchimp tracks email engagement (opens, clicks) on campaigns sent from Mailchimp only — third-party activity logs from Salesforce do not migrate. We document the activity log export as a separate CSV for compliance or audit purposes.

The original Salesforce Contact ID is stored as a custom merge field (SF_ID) on the Mailchimp subscriber record. This enables cross-referencing back to Salesforce, supports delta sync if you later set up a two-way integration, and provides an audit trail for compliance teams who need to trace a subscriber back to its source record.

Salesforce CreatedDate migrates as a custom Mailchimp date-typed merge field (SF_CREATED). This preserves the original contact creation timestamp for reporting continuity — marketers can segment by 'long-term customer' vs 'recent addition' based on the original Salesforce create date, not the Mailchimp import date.

Salesforce Account billing address fields (Street, City, State, PostalCode, Country) map to Mailchimp merge fields ADDR1, CITY, STATE, ZIP, COUNTRY. Mailchimp supports address merge fields natively. Multi-line street addresses are concatenated into the ADDR1 field. Billing address maps regardless of whether the Contact has a separate mailing address.

WorkOrderLineItem records representing parts, labor, and service descriptions have no direct Mailchimp equivalent object. However, FlitStack AI can tokenize line item description keywords into descriptive tags applied to the related Contact subscriber record (e.g., 'HasPart-HVAC-Unit', 'HasService-Installation') to support upsell and cross-sell campaign targeting. The granular line item pricing, quantity, and cost data do not migrate, as Mailchimp lacks a pricing or inventory data model.

Salesforce Leads that are converted or pending conversion migrate to Mailchimp subscribers if they have a valid email address. Lead Status pick-list values (Open, Working, Closed-Converted) map to Mailchimp tags so marketers can exclude converted or unqualified leads from nurture campaigns. Unconverted Leads with no Contact record also migrate as standalone subscribers.