Migrate from Field2Base to Mailchimp

Each Field2Base Form Submission maps to one Mailchimp Contact. The submitter's email address becomes the Contact's email address, which serves as Mailchimp's primary identifier. Multiple submissions from the same email address update the existing Contact rather than creating duplicates. This mapping also supports future updates where new submissions automatically refresh the corresponding contact's data in Mailchimp.

Field2Base User accounts with email addresses map directly to Mailchimp Contacts. Users without email addresses cannot become Mailchimp contacts — those are flagged for manual review. User role (Admin, Form Designer, Mobile User) maps to Tags on the Mailchimp Contact.

If migrating multiple form types, each Form Template maps to a dedicated Tag in Mailchimp applied to all Contacts created from submissions of that template. Alternatively, all submissions consolidate into one Mailchimp Audience with a form-type merge field identifying the source template.

Each Field2Base Region (text, numeric, date, dropdown, checkbox) on a Form Template maps to a Mailchimp Merge Field. Field2Base field validation rules inform the merge field data type. Dropdown Regions require value-by-value mapping to Mailchimp pick-list options. We also generate a validation report highlighting any values that do not map directly.

Mailchimp Contacts have no native submission timestamp. We create a F2B_SUBMIT_DATE merge field capturing the original Field2Base submission datetime. This preserves historical submission ordering for marketing segmentation. This timestamp can later be used in Mailchimp date‑based automations to trigger follow‑up emails based on when the original form was filled out.

Field2Base workflow approval status (Pending, Approved, Rejected) migrates as a merge field and applies corresponding Tags in Mailchimp. Approval routing logic cannot transfer — it becomes a documented reference for manual process rebuild. These tags enable segmentation by approval outcome, allowing targeted email campaigns for approved or pending items.

Field2Base GPS coordinates captured at submission migrate as latitude/longitude text in a F2B_GPS merge field. Geolocation segmentation in Mailchimp requires additional tools like Mailchimp's built-in location filtering on the city or country level. Mailchimp's location filters can then be applied to these coordinates for basic geographic segmentation across campaigns.

Photos captured via Field2Base Camera Region cannot attach to Mailchimp contacts. We export all photos to a cloud storage location and create a F2B_PHOTOS_URL merge field storing the link reference. Photos must be hosted externally. All URLs are validated for accessibility before the final import to prevent broken links.

Signature images captured on Field2Base forms have no Mailchimp equivalent. Signatures are exported as image files with the corresponding contact email in the filename for manual association. A F2B_SIGNATURE_URL merge field links to the exported file. The filename includes the submission ID for quick lookup when needed.

Field2Base workflows with multi-step approval chains have no direct Mailchimp equivalent. We document the workflow structure, approval steps, and conditional logic as a reference guide for rebuilding in Mailchimp Customer Journeys or a separate workflow tool. This documentation can be shared with stakeholders to align on process redesign before implementation.

Barcodes and QR codes scanned via Field2Base migrate as text in a F2B_BARCODE merge field. The barcode image itself is not preserved — only the decoded data value. Barcode lookup or validation logic is not transferred. If a barcode is invalid, we log the raw value for manual review rather than skipping the contact.

Submissions captured offline before syncing carry a flag in Field2Base. We preserve this as a F2B_OFFLINE merge field with Yes/No values so marketing can filter for contacts captured in offline-first scenarios. This field can be used in Mailchimp segment filters to target users who submitted forms while offline, enabling follow‑up on connectivity issues.