Migrate from FieldEdge to Mailchimp

FieldEdge customers map directly to Mailchimp subscribers. Company name becomes the subscriber name, address maps to Mailchimp's address merge fields, and primary phone and email map to standard Mailchimp subscriber fields. A Mailchimp audience is created for each FieldEdge company record.

FieldEdge contacts map to Mailchimp subscribers using the contact's email as the unique identifier. First name, last name, phone, and email map to Mailchimp's standard FNAME, LNAME, PHONE, and EMAIL fields. Multiple contacts with unique emails within one FieldEdge customer create multiple Mailchimp subscribers.

When one email address appears on multiple FieldEdge contact records (e.g., different roles at the same customer), we create one Mailchimp subscriber per email and apply tags for each contact role. This prevents duplicate subscriber creation while preserving the contact role context.

Mailchimp has no native work order object. Work order metadata (work order number, status, service type, technician, service date, description, total amount) maps to Mailchimp merge fields on the subscriber record. Merge field names follow Mailchimp's MERGEn convention. Long text fields (descriptions, notes) are truncated at 255 characters with a flag in the migration report.

Work order line items are aggregated into a single merge field capturing part numbers, descriptions, and quantities. Full line-item detail exceeds Mailchimp's merge field capacity and must remain as reference data in FieldEdge. The aggregated summary provides context for email personalization without losing the data entirely.

Invoice metadata (invoice number, status, date, amount, balance due) maps to merge fields on the Mailchimp subscriber. Full invoice history and line-item detail have no Mailchimp equivalent and must remain in FieldEdge. Storing the most recent invoice status provides a signal for re-engagement campaigns.

Service agreement type, status, start date, and end date map to Mailchimp merge fields. Agreement status drives Mailchimp subscriber tags: 'Active Service Agreement', 'Expired Service Agreement', or 'No Service Agreement'. Monthly recurring revenue (MRR) is stored as a merge field for segmentation into high-value and standard service tiers.

Equipment records (manufacturer, model, serial number, install date, warranty status) attached to a FieldEdge customer map to merge fields on the corresponding Mailchimp subscriber. Mailchimp has no native equipment object, so this metadata is preserved as custom merge fields for segmentation by equipment type or warranty status.

FieldEdge custom properties on Customer and Contact records map 1:1 to Mailchimp merge fields. Text, number, date, and pick-list property types map to equivalent Mailchimp merge field types. Each custom property in FieldEdge creates a corresponding merge field in the Mailchimp audience before import.

Tags and labels applied to FieldEdge contacts carry over directly as Mailchimp subscriber tags. The Mailchimp tag model is fully compatible with FieldEdge's labeling system, preserving the meaning and context of each tag. Tags serve as the primary driver for segmentation in Mailchimp campaigns, including roles like 'Decision Maker', 'Billing Contact', 'Site Manager', and equipment-specific tags such as 'Equipment Type: HVAC' or 'Equipment Type: Plumbing'. Subscriber tags enable targeted messaging to specific audience segments without requiring additional data manipulation after migration.

FieldEdge's dispatch automation, work order routing, and technician assignment rules are field service constructs with no Mailchimp equivalent. These must remain in FieldEdge as the system of record for field operations. Any email triggers tied to these workflows must be rebuilt in Mailchimp using Mailchimp Automations.

FieldEdge's Premier tier includes a native Mailchimp integration that syncs customer lists. This integration does not transfer to the destination Mailchimp account and must be rebuilt manually after migration. FlitStack documents the current sync rules before migration so your team can recreate them in Mailchimp.