Migrate from FieldFX to Mailchimp

FieldFX Contacts migrate as Mailchimp audience members. Email address is the primary key — matched against existing Mailchimp subscribers by email to prevent duplicate creation. Contacts without email addresses are flagged for manual review before import and stored in a holding queue until resolved.

FieldFX Account data populates Mailchimp merge fields on the Contact record rather than a separate object. Company Name maps to a COMPANY merge field; Industry maps to INDUSTRY. Mailchimp has no native company hierarchy — parent-account relationships are not represented.

Any tags applied to FieldFX Contacts (e.g., 'VIP Customer', 'Commercial', 'Residential') transfer as Mailchimp tags on the corresponding subscriber record. Tags are preserved verbatim; Mailchimp's tag model matches FieldFX's tagging approach closely. This ensures segmentation continuity and enables identical filter criteria in Mailchimp campaigns.

FieldFX custom fields on Contact records (e.g., Service_Tier__c, Preferred_Technician__c) require corresponding Mailchimp merge fields created before migration. Each custom field in FieldFX becomes a text, number, or date merge field in Mailchimp. FieldFX pick-list fields become Mailchimp dropdown merge fields with mapped values.

Account-level custom fields (e.g., Contract_Type__c, Service_Area__c) map to merge fields on the Contact record since Mailchimp has no account equivalent. Merge fields must be pre-created in each Mailchimp audience before migration runs. We provide a pre‑migration checklist to ensure all required merge fields are ready.

FieldFX Tickets and Work Orders have no Mailchimp equivalent — Mailchimp is an email platform, not a service management system. We export ticket metadata (status, type, recent service date) as custom merge fields on the Contact record for segmentation purposes, but the operational ticket records do not migrate.

FieldFX Assets track equipment linked to Accounts or Contacts. Mailchimp has no asset management model. Equipment data cannot migrate; however, we can write the most recent service date or asset tag as a contact merge field if the data exists on the Contact record.

FieldFX Users (technicians, dispatchers) who are also customers may appear as Contacts. Owner IDs from Salesforce do not map to Mailchimp — Mailchimp has no concept of record ownership. Owner information is not transferred. Any user‑related contact data must be handled separately in your CRM workflow.

Email addresses from FieldFX Contacts become the primary identifier in Mailchimp. We validate email format before import and flag malformed addresses. Mailchimp handles email compliance flags (bounce, unsubscribe) per its own list hygiene rules post-migration and applies suppression as needed to maintain sender reputation.

Phone numbers from FieldFX Contacts map to the built-in PHONE merge field in Mailchimp. Mobile phone in FieldFX maps to PHONENUMBER. Mailchimp does not use phone for marketing unless SMS is enabled separately. If SMS marketing is part of your plan, we can configure the relevant phone fields accordingly.

FieldFX Contact address fields (street, city, state, zip, country) map to Mailchimp's built-in ADDRESS merge field structure. State and country use Mailchimp's pick-list formats. Addresses without a zip code may cause Mailchimp validation warnings. We recommend verifying all addresses before import to avoid delivery issues.

FieldFX Status Workflows define ticket lifecycle stages (e.g., Scheduled → In Progress → Completed). Mailchimp has no workflow engine for field service. Workflow definitions must be rebuilt manually or via a separate automation tool like Zapier or Make if needed.

FieldFX Reports and FX Reports API dashboards reference ticket data, technician metrics, and service KPIs. Mailchimp Campaign Reports track email opens, clicks, and unsubscribes — a fundamentally different metric set. Report definitions do not transfer; underlying data referenced in custom fields migrates as static values.

FieldFX stores service-call logs, appointment history, and technician notes as Salesforce Tasks and Events. Mailchimp has no activity log per subscriber beyond campaign engagement. Historical activity records do not migrate; only the current contact profile data does. These details remain available in FieldFX for operational reporting.