Migrate from FieldAware by GPS Insight to Mailchimp

FieldAware Customers (the company-level entity) do not map directly to a Mailchimp object — Mailchimp has no company account concept. We create one Mailchimp Audience per FieldAware customer and store the FieldAware customer name as a merge field (COMPANY_NAME). The audience represents a customer account; contacts under it become Mailchimp members.

FieldAware Contacts map to Mailchimp Members using email address as the unique key. First name, last name, phone, and email move directly. A Mailchimp Member status (subscribed, unsubscribed, pending) is set based on FieldAware contact communication preferences if present, defaulting to subscribed.

FieldAware Locations (street, city, state, zip, country) contain address components. We merge these into a single Mailchimp ADDRESS merge field per Contact. If a contact has multiple FieldAware Locations, the primary or most-recently-modified location is used for the address field; additional locations are stored as a TEXT merge field.

FieldAware Jobs (work orders with status, type, technician, timestamps) have no Mailchimp equivalent. We tag contacts with their most recent job status (e.g., Job_Active, Job_Complete) for segmentation, and store a summarized job history as a long-text merge field or reference file. Job details do not appear as native Mailchimp objects.

FieldAware Invoices (amount, status, date) cannot be represented as Mailchimp objects. We surface the most recent invoice amount and date as number and date merge fields for segmentation by customer value, and export full invoice history as a linked CSV reference file.

FieldAware Assets (equipment, serial numbers, service history) do not exist in Mailchimp. We store asset type and count as merge fields and tag contacts by primary asset category to enable service-announcement segmentation. Full asset records are exported as a separate CSV.

FieldAware Tasks (to-do items attached to Jobs or Contacts) have no Mailchimp equivalent. We tag the parent contact with a Task_Pending flag if open tasks exist. Completed task history is exported as a CSV reference file rather than stored in Mailchimp.

FieldAware Items (parts, products, pricing catalog) do not transfer to Mailchimp. If a contact has an associated pricebook or service tier, we store the service level name as a TEXT merge field. Full item and pricebook data is exported separately.

FieldAware Users (dispatchers, technicians, office staff) do not map to Mailchimp. We do not create Mailchimp accounts for FieldAware users. If the goal is to email internal staff from Mailchimp, a separate contact list is built from user email addresses — treated as a distinct audience.

FieldAware custom fields declared on the Customer entity (types: Text, Number, CheckBox, Dropdown, Date, Time) are mapped to Mailchimp merge fields of the corresponding type. TEXT becomes a Mailchimp TEXT merge field; NUMBER becomes NUMBER; DATE becomes DATE; CheckBox values become TEXT ('Yes'/'No'). Dropdown values are preserved as TEXT with the selected option string.

FieldAware custom fields declared on the Contact entity map to Mailchimp merge fields on the Member record using the same type-to-merge-field translation as the Customer entity. Mailchimp's per-audience merge field limit (30 on Free, 80 on paid tiers) applies — large custom field counts may require splitting into multiple audiences or archiving low-priority fields.

FieldAware contact tags or classification labels map directly to Mailchimp Tags on the Member record. Tags enable segmentation for marketing campaigns (e.g., 'VIP_Customer', 'Preventive_Maintenance', 'Annual_Service'). Tags are preserved verbatim from the source. Consistent tag naming helps you build reliable automation rules and reporting segments. We recommend reviewing tag names post-migration to merge any duplicates or variations that may have arisen from legacy data entry practices.

We store the FieldAware record ID on every migrated contact as a TEXT merge field (FIELDAWARE_ID). This enables delta-sync re-runs, de-duplication on subsequent migrations, and cross-reference lookup if data is ever reconciled back against FieldAware exports. Having the source ID stored also supports audit trails, helping compliance teams verify that contact records have been correctly transferred and that no data has been omitted during the process.

FieldAware contact communication opt-in flags map to Mailchimp member status. Contacts opted in become 'subscribed'; opted out become 'unsubscribed'; pending confirmation become 'pending'. If FieldAware has no preference field, all contacts default to 'subscribed' and you should review GDPR/compliance requirements before import.