Migrate from Formaloo to Mailchimp

Each Formaloo Form Response maps to a Mailchimp Contact in the target Audience. The submitter's email address is the required dedupe key; we use Mailchimp's upsert (PUT) endpoint to insert or update based on email hash. Any contact that already exists in the Mailchimp audience is updated with the latest response data. Response timestamps migrate as the contact's timestamp field. We skip responses with no email address and flag them in the reconciliation report since Mailchimp requires an email for every member.

Standard text, email, phone, and number fields from Formaloo map to Mailchimp merge fields. We create merge fields in the destination Audience using the Mailchimp API before import, with field type matched to the Formaloo field type. Email fields migrate as EMAIL merge fields; phone as PHONE; text as TEXT. Field labels from Formaloo become the merge field display name. Date fields migrate as DATE merge fields with ISO format preserved.

Single-select choice fields migrate as merge field values. Multi-select choice fields and rating fields migrate as Mailchimp tags on the contact record — each selected choice becomes a tag with the form name and field name as prefix (e.g., event-interest-concert). This preserves the full multi-select state that Mailchimp's single-value merge fields cannot store. We apply tags after contact insert using the Tags API with batch processing.

Formaloo file upload fields have no direct Mailchimp equivalent since Mailchimp does not store attachments on contact records. We preserve file upload metadata (field label, file name, upload timestamp) as a text note in a dedicated FILE_UPLOAD_METADATA merge field on the contact. The customer downloads the actual files separately from Formaloo or stores them in a linked cloud storage location.

Signature fields from Formaloo (available on Team and Business paid plans) record an e-signature event. Mailchimp has no signature capture capability. We preserve the signature field label, submitter name, and submission timestamp as a SIGNATURE_RECEIVED note in a dedicated merge field. The legal validity of the signature record remains in Formaloo and is not transferable.

The source Form name becomes a tag source label in Mailchimp, applied to all contacts migrated from that form. This preserves the provenance of each contact record and allows segmentation by original form submission. Tag format is FORMSOURCE_<FormName>. If a contact was submitted to multiple forms, multiple tags are applied.

Formaloo Databases link multiple forms together via reference fields. Mailchimp has no relational database model. We export the Database structure as a JSON schema document and create Mailchimp tag sets with descriptive labels (e.g., RELATION_DB_OrderForm_to_CustomerForm) that represent the cross-form relationships. The customer uses these as a reference map to rebuild related records manually in Mailchimp or connect via a third-party CRM integration.

Formaloo conditional logic rules, field visibility conditions, and calculation formulas are UI-defined automation that does not export as structured data. We provide a written inventory of each form's logic configuration including trigger conditions, field dependencies, and calculation formulas, formatted as a configuration guide. The customer's Mailchimp admin rebuilds equivalent logic using Mailchimp Automations and merge field conditional content.

Formaloo Workspace and Folder structure organizes forms and responses. Since Mailchimp has no workspace or folder hierarchy, we map Workspace names to Mailchimp tags prefixed WORKSPACE_<name> and Folder names to tags prefixed FOLDER_<name>. This preserves the organizational context of each form as metadata on migrated contacts.