Migrate from Fieldy to Mailchimp

Fieldy Customer records — which store contact name, email address, phone, and company association — map directly to Mailchimp subscribers. Each Fieldy customer with an email address becomes one subscriber record in your target Mailchimp audience. Customers without email addresses are flagged for manual review before migration.

Fieldy standalone Contact records map 1:1 to Mailchimp subscribers. The contact's first name, last name, and email address populate the corresponding Mailchimp merge fields. Phone number maps to the phone merge field if configured in the Mailchimp audience schema. Any additional contact details such as job title or secondary email are preserved in custom merge fields or exported as supplementary data.

Fieldy Company records store business name, industry, website, and employee count. These values migrate as Mailchimp merge fields on the Subscriber record — typically COMPANY_NAME, INDUSTRY, and WEBSITE — rather than as a separate object, since Mailchimp has no native company/account object at the subscriber level.

Fieldy Job records contain job type, status, scheduled date, technician assigned, service address, and completion notes. Mailchimp has no job or work-order object. These records cannot auto-migrate. FlitStack documents all Fieldy job field names and values in a CSV rebuild reference so your team can manually recreate job-status email triggers in Mailchimp automations if desired.

Fieldy Invoice records include invoice number, amount, status (paid/unpaid/overdue), line items, and payment date. Mailchimp has no invoice object. Invoice data cannot migrate to Mailchimp's subscriber schema. We export the invoice dataset separately as a CSV and flag it for import into a dedicated billing or accounting tool.

Fieldy Quote records store quoted service name, line items, pricing, validity date, and acceptance status. Mailchimp has no quote object. Quotes are exported as a separate CSV with field names preserved. Your team can map quote acceptance status as a trigger for a Mailchimp automation that sends a follow-up campaign, but the quote record itself must be recreated in your quoting tool.

Fieldy custom fields on Customer records — such as service_agreement_type, preferred_technician, or renewal_date — are type-mapped to Mailchimp equivalents. Text custom fields become Mailchimp text merge tags. Date fields become Mailchimp date merge tags. Pick-list or dropdown fields in Fieldy map to Mailchimp Groups with the pick-list values as group names. Custom fields on Job or Invoice objects cannot migrate.

Fieldy Users and Technicians are operational staff with dispatch assignments and service territories. Mailchimp Admin and User roles manage audience access and campaign permissions — they are not a counterpart to technician records. Technician contact information that serves as a customer-facing point of contact can be stored as a custom merge field on the subscriber if needed.

Fieldy supports multiple business locations or branches, each with its own customer and job records. When your migration involves multiple Fieldy locations, we split the contacts by location_id and upsert them into separate Mailchimp audiences — one audience per location. This preserves segmentation by branch and allows location-specific campaign targeting in Mailchimp.

Fieldy job records may include photos, signed forms, or PDF attachments (e.g., service completion photos, before/after images). Mailchimp subscriber records do not support attachments or file uploads. Attachments are exported separately and can be linked in Mailchimp campaigns via URL if hosted externally, but the attachment files themselves do not migrate into Mailchimp.