Migrate from Field Harmony to Mailchimp

Field Harmony Customer records map directly to Mailchimp Subscriber members within a target audience. The email address field serves as the unique identifier for deduplication and Mailchimp's subscriber key. Each customer becomes one member regardless of how many work orders are attached.

The customer email address is the primary key for Mailchimp subscriber creation. FlitStack validates email format before insertion and flags invalid addresses in a separate error report. Bounced or invalid emails from Field Harmony do not transfer to avoid Mailchimp list hygiene penalties.

First name from Field Harmony populates the FNAME merge tag in Mailchimp. If no first name exists in Field Harmony, the merge field is left blank. FlitStack does not infer names from email addresses — that requires a separate enrichment step.

Last name from Field Harmony populates the LNAME merge tag in Mailchimp. Same handling as first name — blank if absent, no inference from email or other fields. FlitStack preserves the exact spelling from Field Harmony without modification. Name formatting (e.g., hyphens, special characters) transfers as-is to maintain data fidelity.

Phone number transfers to Mailchimp's PHONE merge field if the field exists in Field Harmony. Phone numbers are stored as plain text; no formatting normalization is applied unless specified in the migration plan. If Field Harmony stores phone numbers with country codes, those characters transfer intact.

Mailchimp's ADDRESS merge field is a structured group containing addr1, addr2, city, state, zip, and country. Field Harmony address components are mapped into the corresponding sub-fields. Multi-address customers require a rule — we use the primary service address by default and flag the record for secondary address handling.

Any custom fields on Field Harmony customers (such as service_tier, contract_type, or technician_assigned) require corresponding merge fields in Mailchimp. FlitStack creates text or dropdown merge fields in Mailchimp before migration. Dropdown fields require value enumeration matching the Field Harmony picklist.

Work order records (jobs, tasks, scheduling data) have no direct equivalent in Mailchimp. These do not migrate. If work order history is needed for marketing context, a summary field (e.g., last_service_date) can be added as a custom merge field on the customer contact — FlitStack surfaces this option in the migration plan.

Technician assignments from work orders can be summarized as tags on the customer subscriber record in Mailchimp. For example, customers with assigned technician 'J. Smith' receive the tag 'Technician: J. Smith'. This requires aggregating work order data to derive the tag values before Mailchimp insertion.

Field Harmony customer active/inactive status maps to Mailchimp subscriber status. Active customers insert as 'subscribed'. Inactive customers insert as 'unsubscribed' to respect the customer's implied preference. You confirm the mapping rule before migration runs. This ensures the Mailchimp audience reflects the original communication preferences set in Field Harmony.

Mailchimp does not store original subscriber creation timestamps natively. We create a custom merge field (OPTIN_DATE__c) on the Mailchimp audience to preserve the Field Harmony customer create date for segmentation and historical reporting. This allows you to segment subscribers based on when they originally became customers in Field Harmony.

If Field Harmony supports label or tag assignment on customers, those transfer as Mailchimp tags on the subscriber record. Tags enable segmentation in Mailchimp (e.g., 'Preferred Customer', 'Commercial Account'). We extract unique tag values and apply them during batch insertion.