Migrate from Field Nexus to Mailchimp

Field Nexus contacts map directly to Mailchimp audience members. Email address is the unique identifier — required for import. Contacts without an email address are flagged and held for manual review before the migration commits. If a contact lacks an email address, we retain its other details in a supplemental CSV so you can follow up manually after migration.

Field Nexus company names map to a Mailchimp COMPANY merge tag. For contacts with multiple associated companies, we migrate the primary company (most recently modified) to the single Mailchimp company field and surface the full list as a custom merge tag for admin reference.

Work order records have no native Mailchimp equivalent. We migrate job status, priority, service type, technician name, and service address as summary merge tags. Full work order history is exported as a JSON or CSV attachment and stored as a Mailchimp note for contact-level reference.

Estimate amounts and statuses (pending, approved, declined) map to merge tags in Mailchimp. Estimate line items and notes are not supported as structured Mailchimp fields — they are summarized in a merge tag or exported as a note attachment. If you need detailed line‑item data for reporting, we can also attach a separate CSV file to the contact note.

Invoice status and total amount map to Mailchimp merge tags as text fields. Payment collected and outstanding balance are mapped to INVOICE_PAID and INVOICE_BAL merge tags respectively. Mailchimp does not have live invoice objects — these are snapshot values at migration time.

Field Nexus custom property values that represent customer classification (e.g., 'contract customer', 'one-time', 'commercial') are merged and applied as Mailchimp tags. Multiple Field Nexus property values on a single contact result in multiple Mailchimp tags, enabling segment-based rebuild in Mailchimp.

Field Nexus service address (often a single formatted string) is split into Mailchimp merge tags for street address, city, state, and ZIP. This enables geographic segmentation in Mailchimp segments based on service territory. If the source address contains additional components such as floor or suite, we preserve them in a supplementary ADDRESS_EXT merge tag.

The Field Nexus technician or contact owner name maps to a TECHNICIAN merge tag in Mailchimp. This is a reference field only — it enables segmenting contacts by assigned technician but does not create a linked user in Mailchimp. If you require routing automation based on technician assignment, you can build Mailchimp automations that trigger external scheduling actions using the TECHNICIAN value as a filter.

Field Nexus does not track email bounce or unsubscribe status natively. If your email history exists elsewhere, we export those addresses and import them as a Mailchimp suppression list so they are not re-emailed after migration. We also provide a verification report listing any addresses that could not be imported due to formatting issues.

Original Field Nexus create and last-modified timestamps are preserved as custom merge tags. Mailchimp's native MEMBER_COUNT and signup date do not reflect the original Field Nexus record creation date — the SRC_CREATED tag maintains that history for segmentation and reporting continuity.