Migrate from Sales Flow Technologies to Mailchimp

Sales Flow Contacts map to Mailchimp Subscribers in the target Audience. We use the contact's email address as the Subscriber Hash for the Mailchimp API import. Name, company, role, and any custom fields map to Mailchimp merge fields (FNAME, LNAME, COMPANY, ROLE, and any custom MMERGE field). Email opt-in status is preserved from the Sales Flow contact's subscribed flag. Duplicate email addresses are handled via Mailchimp's upsert semantics (update existing or create new).

Sales Flow Prospect Lists are named groupings of Contacts used to organize outreach targets. We map each Prospect List to a Mailchimp Tag of the same name applied to every Subscriber in that list. If the customer prefers segment-based grouping, we can create a Mailchimp Segment using the Tags condition and save it with the Prospect List name for reference. Multi-list membership (a Contact in two Sales Flow Prospect Lists) results in two Tags applied to the same Subscriber.

Sales Flow Campaigns bundle multiple Sequences under a single objective. We preserve Campaign names, associated Sequence names, and reporting date ranges as a structured reference document attached to the migration record. Mailchimp Campaign metrics (open rate, click rate, unsubscribe rate) are imported as historical reference notes against the equivalent Mailchimp Campaign record if the customer has existing Mailchimp data. Channel routing logic and A/B testing configurations do not transfer and are documented for rebuild.

Sales Flow Sequences define cadence and channel steps (LinkedIn connection request, follow-up Email, InMail) for a group of Contacts. Sequence step ordering and timing data are exported as a structured CSV. Mailchimp has no multi-channel Sequence equivalent; we document every Sequence step, timing interval, conditional branch, and channel assignment in the Workflow Summary for the customer's admin to rebuild as Mailchimp Customer Journeys or Automations post-migration.

Sales Flow User accounts define who on the team is running outreach (Admin or Standard roles). Mailchimp team members are managed under Account Settings with role-based permissions (Admin, Manager, Author, Viewer). We document the Sales Flow user roster and role assignments as a reference for the customer's Mailchimp admin to provision equivalent access. Sales Flow seat count does not map directly to Mailchimp seat count.

Sales Flow provides per-sequence and per-step open rates, reply rates, and connection acceptance rates. We export these metrics as a structured CSV report and attach them as reference notes to the corresponding Mailchimp Campaign record. Mailchimp's reporting model (open rate, click rate, bounce rate, unsubscribe rate) is not directly equivalent to Sales Flow's outreach-specific metrics, so the data serves as historical reference rather than live reporting continuity.

Inbox messages represent the conversation thread between the rep and the prospect across LinkedIn and email. These are stored in LinkedIn's infrastructure and are not accessible via Sales Flow export. Mailchimp has no Inbox equivalent. This data is not migrated.

Sales Flow Workflows define conditional branching logic for prospect responses and follow-up actions (e.g., 'if no reply after 3 days, send template B'). The workflow builder configuration is not exported via CSV or API. We document the workflow logic in the Workflow Summary: every conditional rule, step order, timing, and action. The customer's admin rebuilds these as Mailchimp Customer Journeys. This is the most common source of post-migration surprise and we flag it explicitly during scoping.