Migrate from Sanoflow to Nutshell

Sanoflow Contacts map directly to Nutshell Contacts. We extract the full contact profile including name, phone (required in Sanoflow), email, and all Custom Field values. Custom Fields on Contacts (text, number, date, choice) migrate as Nutshell custom fields on the Contact record. Owner assignment from Sanoflow maps to the assigned user in Nutshell; we resolve by email match and flag any owner without a matching Nutshell user for the admin to provision before record import.

Sanoflow Enquiries are the core transactional record — they represent inbound messages, form submissions, or Flow-started conversations linked to a Contact. We classify each Enquiry by status: active or open Enquiries map to Nutshell Leads, and Enquiries that have progressed to a sales-ready stage map to Nutshell Deals with stage name derived from the Sanoflow Pipeline Stage. The Enquiry body, source channel (WhatsApp, Instagram, etc.), assigned agent, and Custom Field values migrate. Closed Enquiry history is preserved as Notes or as Deal history depending on the customer's preference.

Sanoflow Pipelines are Kanban-style workflow boards. Each Pipeline maps to a Nutshell Deal with the pipeline name stored as a Deal field and the Enquiry's stage within that pipeline stored as the Deal stage. If the customer uses multiple Sanoflow Pipelines (up to 5 on Starter, 20 on Growth, 50 on Premium), we create a Nutshell custom field pipeline_name__c to preserve pipeline attribution on each Deal record.

Sanoflow Pipeline Stages migrate to Nutshell Deal stages in order. Stage names map 1:1. Stage-specific automation rules (Sanoflow Flow triggers tied to stage transitions) are flagged as Flow gotchas and documented in the Workflow Specification Document rather than migrated as automation code. Completion criteria defined in Sanoflow are noted as custom fields in Nutshell.

Sanoflow Channels represent connected messaging platforms (WhatsApp, Instagram, Messenger, TikTok). Channel credentials cannot migrate across platforms — WhatsApp Business API tokens and Instagram connection tokens are destination-specific and tied to Meta Business accounts. We document all active Channels as metadata (name, type, connected date) in a Channel Inventory and note which Contacts and Enquiries were associated with each Channel. The customer reconnects channels in Nutshell or their preferred messaging tool post-migration.

Sanoflow Custom Fields on Contacts and Enquiries (available at Growth tier and above) map to Nutshell custom fields of equivalent type. Text fields map to text, number fields to number, date fields to date, and choice fields to picklist. Choice field option values are enumerated as Nutshell picklist values during migration. Custom Field definitions and current values migrate; the field-level audit history is not preserved.

Sanoflow team membership and role names migrate to Nutshell Users. We extract all agents, their team assignments, and role names from Sanoflow. Permission granularity differs between platforms — Sanoflow's custom role model does not have a direct Nutshell equivalent, so we document the permission matrix and recommend the closest Nutshell sharing model (private, team, or global) during scoping.

Sanoflow Enquiry Forms are inbound entry points that create Enquiry records. We migrate form field definitions and map them to a Nutshell custom field lead_source__c set to the form name. Form routing rules (which Flow a submission triggers) are documented in the Workflow Specification Document as these cannot be migrated as automation. The customer recreates form-to-Lead routing in Nutshell's native web-to-Lead or a third-party form tool.