Migrate from Sanoflow to Mailchimp

Sanoflow Contacts map to Mailchimp Subscribers within an Audience. The email address (required on Mailchimp subscribers) is the primary key. Phone number from Sanoflow maps to the PHONE merge field in Mailchimp. Owner assignment maps to a Mailchimp tag named after the owner. If a Sanoflow Contact has no email address, we flag it as unimportable and surface it in the reconciliation report; these contacts require manual email capture before they can be added to Mailchimp.

Sanoflow Contact custom fields (text, number, date, choice types available at Growth tier and above) map to Mailchimp merge fields. Text fields in Sanoflow must not exceed 255 characters to map to Mailchimp's TEXT merge field without truncation. Long-text Sanoflow fields require a decision: map to a truncated TEXT merge field, split into multiple TEXT fields, or exclude. Choice fields map to Mailchimp RADIO or DROPDOWN merge fields based on single-select or multi-select configuration. We document all field types and lengths during scoping to surface any character-limit violations before production import.

Sanoflow Enquiries are inbound WhatsApp messages or form submissions tied to a Contact. Mailchimp has no Enquiry object. We map the most recent Enquiry status and source channel to Mailchimp subscriber tags (e.g., enquiry_source_whatsapp, enquiry_status_open) to preserve segmentation context. Full enquiry thread content does not migrate because Mailchimp's subscriber profile is email-centric and does not support threaded message history.

Sanoflow Teams and role assignments govern which agents manage which Enquiries. We map team membership to a Mailchimp subscriber tag (e.g., team_sales, team_support) so the customer can segment by internal team if needed. Role granularity in Mailchimp is limited to Admin, Manager, and Author at Standard tier and above; we map role names to tags and note any fine-grained permissions that cannot be preserved.

Sanoflow Enquiry Forms are inbound entry points that create Enquiry records. Mailchimp signup forms serve an equivalent capture function. We document each Enquiry Form's field definitions and routing logic and deliver a written form specification so the customer can manually recreate them as Mailchimp embedded forms, popup forms, or landing pages. The form itself does not migrate programmatically because Sanoflow form configurations are not exported via API.

Sanoflow Pipelines are Kanban-style workflow boards for managing Enquiries and Deals. Mailchimp has no pipeline concept. We map active Pipeline names to subscriber tags (e.g., pipeline_sales_lead, pipeline_support) or recommend splitting into separate Mailchimp Audiences if the customer's pipeline count is small and manageable per-Audience. This is a configuration decision made during scoping; we present both options and the tradeoffs.

Each Pipeline Stage within a Sanoflow Pipeline maps to a subscriber tag reflecting the stage name (e.g., tag_stage_new, tag_stage_qualified, tag_stage_won). If the customer uses multiple Pipelines, we prepend the pipeline name to avoid tag name collisions (e.g., sales_new, support_new). Stage order and completion criteria are not transferable to Mailchimp because there is no Kanban or stage-progression concept in the platform.

Sanoflow Channels represent connected messaging platforms (WhatsApp, Instagram, Messenger, TikTok) with their own API credentials and configurations tied to Sanoflow's own Meta Business account setup. These cannot migrate to Mailchimp because Mailchimp is an email platform with no WhatsApp or Instagram channel integration. We document all active Channels during scoping so the customer understands which messaging connections they are discontinuing and can plan Meta Business account management separately.

Sanoflow Flows are no-code automation workflows built with triggers, message steps, and actions in the Flow Builder. There is no documented Flow export endpoint or API. We extract Flow metadata (name, trigger type, step count, action types) during scoping and deliver a Workflow Specification Document describing each active Flow's structure, conditions, and recommended Mailchimp Customer Journey equivalent. The customer rebuilds these manually in Mailchimp's Customer Journey Builder after migration. Flows that rely on WhatsApp-specific actions (e.g., session messages, template sends) have no direct Mailchimp replacement.