Migrate from Sanoflow to Zoho CRM

Sanoflow Contacts with no associated Enquiry or pipeline stage map to Zoho Contact directly. Contacts with Enquiry history but no closed-won pipeline stage map to Zoho Lead. Contacts attached to a Sanoflow pipeline with a closed-won Enquiry map to Zoho Contact linked to a Zoho Account (created from the Contact's company name if present). We preserve Sanoflow custom field values in Zoho custom fields created during schema setup. Owner assignment migrates by email match to Zoho User, with unresolvable owners flagged in a reconciliation report.

Sanoflow Enquiries represent inbound messages or form submissions. Enquiries with a status of open or pending map to Zoho Lead with the Enquiry body in the Description field and the source channel noted. Closed-won Enquiries (converted to a Sanoflow pipeline deal) map to a Zoho Deal with the Account and Contact already resolved from the Contact mapping. Enquiry custom fields migrate to custom fields on the Zoho Lead or Deal depending on routing.

Sanoflow Pipelines map to Zoho Sales Processes. Each Pipeline in Sanoflow becomes a Zoho Sales Process with its own stage sequence. Stage order and stage names migrate 1:1 into Zoho Stage names. Stage completion criteria do not migrate because Zoho Deal stages do not have equivalent completion-rule fields; these are flagged for manual configuration in Zoho Blueprint if the customer requires stage-gating.

Individual Sanoflow Pipeline stages map to Zoho Deal Stage values within the corresponding Sales Process. Probability percentages migrate from Sanoflow where available. Stage-specific Sanoflow automation rules are flagged in the Workflow Specification Document and do not migrate as active rules.

Sanoflow custom Contact fields (available at Growth tier and above) map to Zoho custom fields on the target Zoho module (Contact or Lead). Text, number, date, and choice field types map directly. Choice-field option sets require manual creation in Zoho because Zoho picklist values are managed in field setup rather than inferred from data. We create the Zoho custom fields via the Zoho API before migration begins.

Sanoflow custom Enquiry fields (Growth tier and above) map to Zoho custom fields on the target Zoho module (Lead or Deal depending on routing). Choice-field options are created manually in Zoho field setup. Enquiry tag associations migrate as multi-select picklist fields in Zoho.

Sanoflow Channels (WhatsApp, Instagram, Messenger, TikTok) cannot be migrated because WhatsApp Business API credentials are bound to the specific Meta Business account connected in Sanoflow. The WhatsApp phone number and Business account are Sanoflow-hosted and cannot be transferred. We document all connected Channel types, their names, and the routing rules (which Flow a submission triggers) so the customer can reconfigure Channels in Zoho or a dedicated WhatsApp Business solution post-migration.

Sanoflow Flows have no documented export endpoint or API access. We inventory every active Flow during scoping, capturing the Flow name, trigger type (Enquiry submitted, Contact updated, scheduled), step sequence, message content, action types (assign, tag, notify, update field), and any conditional branching logic. This is delivered as a Workflow Specification Document describing each Flow's logic in Zoho Blueprint and Workflow Rule terms so the customer's admin can rebuild in Zoho without reverse-engineering from memory.

Sanoflow Enquiry Forms create inbound Enquiry records. We migrate form field definitions and map them to Zoho Form fields or Zoho Webforms. Form routing rules (which Flow a submission triggers) are documented in the Workflow Specification Document since they are Flow-dependent and cannot migrate as active routing logic. Webhook-triggered forms are flagged separately because the webhook URL is destination-specific and must be recreated in Zoho.

Sanoflow Teams and Custom Roles map to Zoho Roles with data-sharing rules approximating the Sanoflow permission model. Sanoflow role granularity (which agents see which Enquiries) simplifies in Zoho to Zoho's standard role hierarchy with territory-based record assignment. We document the current Sanoflow role structure and recommend the closest Zoho equivalent during scoping.

Sanoflow WhatsApp Broadcast records migrate as metadata: campaign name, audience segment definition, message template references, and send history dates. Actual WhatsApp message content and approval status do not carry over because templates are tied to the Sanoflow Meta Business account. We flag all active templates with their content for re-submission to Meta under the customer's new WhatsApp Business account. Re-approval timelines (typically 24-48 hours per template) are surfaced during scoping so the customer can plan campaign continuity.

WhatsApp conversation history in Sanoflow (text messages, media attachments, timestamps) is exported as a structured attachment linked to the Contact or Enquiry record. Zoho does not have a native WhatsApp conversation object; we attach conversation exports as Notes linked to the Contact. Individual Enquiry interactions (agent responses, status changes) migrate as Zoho Tasks with ActivityDate set to the original timestamp and the task body containing the interaction summary.