Migrate from Salesflo Engage to Mailchimp

Mailchimp's 40-merge-field limit per audience caps survey field carry-over

Salesflo Engage dynamic surveys can contain dozens of form fields per survey, and a team may run multiple surveys over time. Mailchimp enforces a hard limit of 40 merge fields per audience. If your Engage setup has more than 40 unique survey fields across all forms, we must split contacts into multiple Mailchimp audiences or drop low-priority fields. We surface this during scoping so you can decide which survey data matters most before migration. The drop list is agreed upon in writing before migration commits.

GPS coordinates and raw location geometry do not translate to Mailchimp

Salesflo Engage stores GPS coordinates, geofence data, and precise location geometry for each visit. Mailchimp has no native geospatial field type — there is no latitude/longitude, radius segment, or map-view feature. The location name (e.g., store name or district) is preserved as a tag and text merge field, which lets you segment by territory name in Mailchimp. But precise coordinate data is lost unless you export it separately to a GIS tool. We flag this explicitly in the pre-migration data audit so you can decide whether to keep a separate geospatial backup.

Visit scheduling and task assignment are not contact data — they require manual Customer Journey rebuild

Salesflo Engage workflows encode conditional routing logic: if a field rep completes a visit, then schedule a follow-up; if a survey score is below threshold, assign a manager review. These are not contact properties — they are automation rules that live on the Visit and Task objects. Mailchimp Customer Journeys are trigger-based automations attached to contact events (signup, tag added, date arrived). The mapping is not 1:1. We export every Salesflo Engage workflow definition as a structured JSON file. Your Mailchimp admin uses that file to rebuild the equivalent Customer Journey. We do not automate this step because the logic does not translate directly.

Salesflo Engage archived contacts map to unsubscribed in Mailchimp by default

Salesflo Engage has an active/archived status on contact records. By default, we map archived Engage contacts to unsubscribed status in Mailchimp — this is the closest equivalent semantic match. If your team used the archive status differently (e.g., as a suppression flag rather than a true unsubscribe), this default mapping may suppress contacts you intended to keep as subscribed. We offer a configurable mapping rule for this: you can choose to map archived contacts to 'cleaned' or 'pending' instead, depending on your Mailchimp plan's available status values.

Mailchimp tags are not hierarchical — territory nesting requires flat tag conventions

Salesflo Engage location hierarchies (region > district > store) allow nested filtering and drill-down. Mailchimp tags are flat — there is no native hierarchy or parent-child tag relationship. If your segmentation logic depends on nested location levels, you must encode the hierarchy into the tag name itself (e.g., tag_Region_West_District_Coastal_Store_Downtown). We implement a configurable flat tag prefix convention during migration so your Mailchimp segments can approximate the Engage hierarchy. This is a known limitation of Mailchimp's tagging model and we make it transparent during planning.