Migrate from Fieldproxy to Mailchimp

Fieldproxy clients map 1:1 to Mailchimp contacts. Each client record becomes one subscriber in the target Mailchimp audience. Primary contact fields (name, email, phone, address) map to Mailchimp's standard contact fields. Fieldproxy does not store subscriber status — all migrated contacts are set to subscribed by default. FlitStack flags any Fieldproxy clients without a valid email address; those records are held for manual review before the import runs.

Mailchimp has no native company name field on contacts. FlitStack creates a Company_Name merge tag in Mailchimp and maps Fieldproxy's client company name into it. The original value is also appended to the contact notes field alongside job and quote summaries so the full client context is preserved in the notes section.

Fieldproxy locations have up to three address lines (street, street2, street3). Mailchimp accepts two lines (ADDR1, ADDR2). FlitStack maps street to ADDR1 and concatenates street2 and street3 into ADDR2, with a semicolon separator. If ADDR2 exceeds Mailchimp's character limit, the overflow is stored in the contact notes field. City, state, postal code, and country map directly to their Mailchimp equivalents.

Each Fieldproxy custom property on the client object becomes a Mailchimp merge tag. FlitStack creates the merge tag in Mailchimp before import, matching the field type: text fields map to text merge tags, dates to date merge tags, numbers to number merge tags, and dropdowns to text merge tags with the pick-list values as reference. Fieldproxy's custom property API key is stored in the Mailchimp contact's notes for traceability.

Fieldproxy work orders (jobs) have no native Mailchimp equivalent — Mailchimp has no object model for service records, technician assignments, or line-item invoices. FlitStack serializes the most recent five jobs per client into a structured text block stored in the contact notes field. Each serialized job includes job type, status, scheduled date, technician name, and a truncated description. Older jobs are summarized rather than fully detailed to prevent notes from exceeding Mailchimp's character guidance.

Fieldproxy quotes have line items, pricing, status, and expiry dates — none of which map to a native Mailchimp field. FlitStack serializes the most recent three quotes per client into a structured text block in the contact notes field. Each serialized quote includes the quote total, status, and expiry date. Full line-item details are not transferred due to Mailchimp's note format limitations.

Fieldproxy tags on clients migrate 1:1 to Mailchimp subscriber tags. Tags are applied at import time so each contact lands in Mailchimp already tagged. Fieldproxy job tags (e.g., service type, customer tier) are prefixed with 'FP-job:' in Mailchimp to distinguish them from contact-level tags. Duplicate tags across Fieldproxy and Mailchimp are merged — FlitStack does not create redundant tags.

Fieldproxy client notes map directly to Mailchimp contact notes. Notes are appended as plaintext — formatting, links, and special characters are preserved where Mailchimp's note field allows. Existing Mailchimp notes (if any) are not overwritten; Fieldproxy notes are added as a new entry timestamped with the migration date.

Fieldproxy invoices (linked to clients by foreign key) have no Mailchimp equivalent. Invoice totals, payment status, and balance due are serialized as a single text reference in the contact notes field (e.g., 'Last Invoice: INV-4521 | Total: $1,250 | Status: Paid'). Full invoice line items are not transferred. FlitStack recommends exporting invoices as a separate CSV report from Fieldproxy for financial record-keeping.

Fieldproxy clients can have multiple service locations. Mailchimp contacts have a single address. FlitStack migrates the primary location as the contact address and serializes additional locations into the notes field with a clear header (e.g., 'Additional Location 2: 456 Oak St, Chicago, IL 60601'). This preserves the full location history without data loss.

Mailchimp does not track when a contact was originally created in Fieldproxy. FlitStack creates a CLIENT_CREATED_DATE merge tag on each contact and populates it with the Fieldproxy client creation timestamp. This preserves historical customer onboarding dates for segmentation and reporting in Mailchimp.