Migrate your Sanoflow data

Contacts are the core CRM record in Sanoflow, storing name, phone, and custom fields. We extract full contact profiles including all Custom Field values and preserve owner assignment during migration. Custom field types (text, choice, date) are mapped to equivalent destination types.

Enquiries represent inbound customer messages or form submissions, linked to a Contact. We migrate the enquiry body, source channel, status, and assigned agent. Tag associations and custom Enquiry Fields require value mapping against the destination schema.

Pipelines are the Kanban-style workflow boards unique to Sanoflow. We preserve pipeline names, stage order, stage names, and the active pipeline assignment per Enquiry or Contact. Multiple pipelines are supported on Growth and above.

Each Pipeline contains ordered stages with names and optional completion criteria. We map stage order and naming 1:1 into the destination pipeline tool. Stage-specific automation rules are flagged as manual-recreate items since no export is documented.

Channels represent connected messaging platforms (WhatsApp, Instagram, Messenger, TikTok). Channel configurations cannot be migrated across platforms — WhatsApp Business API credentials are destination-specific. We migrate the channel assignment per Enquiry record as metadata only.

Flows are Sanoflow's no-code automation workflows built with Triggers, Messages, and Actions. There is no documented Flow export endpoint. We extract Flow metadata (name, trigger type, step count) and flag the workflow as a candidate for manual rebuild using destination equivalents (e.g. Zapier, Make, or native automation).

Sanoflow supports Custom Fields on both Contacts and Enquiries at Growth tier and above. Field types include text, number, date, and choice. We migrate field definitions and values. Choice-field option sets require remapping to match destination enum values.

Teams and role assignments govern which agents see and manage which Enquiries. We preserve team membership and role names. Permission granularity varies by destination CRM and may require simplification.

Webhook configurations are tier-gated (Premium and Enterprise only) and point to destination-specific URLs. Webhook endpoints cannot be transferred between platforms as they reference live systems. We document the webhook event types in use but do not migrate them.

Enquiry Forms are inbound entry points that create Enquiry records. We migrate form field definitions and map them to destination form or lead-capture structures. Form routing rules (which Flow a submission triggers) are flagged for manual reconfiguration.

Campaign records including audience segments, message templates, and send history are migrated as metadata. Actual WhatsApp message template approval status does not carry over — templates must be re-submitted to Meta for WhatsApp Business approval in the destination account.