Migrate from Sanoflow to Freshsales

Sanoflow Contacts migrate to Freshsales Contacts. We extract contact name, phone number, email, custom field values, owner assignment, and tags. The Freshsales Contact record is the primary mapping target. If Sanoflow Contacts have a qualification status (e.g., assigned to a sales agent), we evaluate mapping to Freshsales Lead instead based on the customer's lifecycle definition. We resolve Contact owner by email match against Freshsales User records and flag any unmatched owners for admin provisioning.

Sanoflow Enquiries represent inbound messages or form submissions and map most directly to Freshsales Leads. The Enquiry body, source channel (WhatsApp, Instagram, Messenger, TikTok), status, assigned agent, and timestamp migrate. Tags on Enquiries migrate to Freshsales Lead Tags or a custom multi-select field. If the customer treats Enquiries as resolved customer support cases, we evaluate mapping to Freshsales Tasks or Cases instead. This decision is made during scoping.

Sanoflow Pipelines map to Freshsales Pipelines with stage names and order preserved 1:1. The Freshsales Pipeline builder is configured during migration to match Sanoflow stage names, stage order, and probability percentages. If Sanoflow has multiple Pipelines, we create corresponding Freshsales Pipelines. Stage-specific automation rules in Sanoflow are flagged as non-transferable and documented in the Workflow Specification.

Each Sanoflow Pipeline Stage maps to a Freshsales Deal Stage within the corresponding Pipeline. Stage names, order, and probability percentages transfer directly. Stage completion criteria and stage-gating rules in Sanoflow are documented for the customer's admin to implement as Freshsales Workflow conditions post-migration.

Sanoflow Custom Fields on Contacts (text, number, date, choice) map to Freshsales Custom Fields on Contact. Choice-field option sets map to Freshsales picklist values. We create the destination field in Freshsales with matching label and type before importing any contact records. Custom Field support on Sanoflow requires Growth tier; we verify the source tier during scoping.

Sanoflow Custom Fields on Enquiries map to Freshsales Custom Fields on Lead if the Enquiry-to-Lead mapping is used. Field types are matched (text to text, number to number, date to date, choice to picklist). Choice-field option sets are recreated in Freshsales. Enquiry-level custom fields cannot be preserved if Enquiries are mapped to Tasks instead; we confirm the Enquiry mapping strategy during scoping.

Sanoflow Channels (WhatsApp, Instagram, Messenger, TikTok) represent connected messaging platform credentials and cannot migrate. WhatsApp Business API credentials are bound to the Meta Business account connected in Sanoflow and cannot be transferred to Freshsales. We document the active Channels during scoping and flag that a new WhatsApp Business API connection must be established in Freshsales separately. Instagram and Messenger connections similarly require re-authentication.

Sanoflow Flows have no export endpoint and cannot be migrated programmatically. We extract Flow metadata (name, trigger type, step count, action types) during scoping and produce a written Workflow Specification Document describing each Flow in Freshsales Workflow DSL terms. The customer's admin uses this document to rebuild Flows in Freshsales. This specification is included in the migration deliverable at no additional cost.

Sanoflow Enquiry Forms (inbound entry points creating Enquiry records) are documented with field names, field types, and routing rules. Freshsales Forms capture lead information and create Lead records directly. We document each Sanoflow form and its routing logic so the customer's admin can recreate equivalent Freshsales Forms and configure form-to-Lead routing post-migration.

Sanoflow Teams and role assignments map to Freshsales Teams. Role names and team membership are preserved. Permission granularity differences between the two platforms may require simplification; we document the original permission scope in the migration notes and flag any gaps for the customer's admin to address in Freshsales Role settings.