Migrate from Sanoflow to monday CRM

Sanoflow Contacts map to Monday.com People records with name, phone, and email preserved. Custom Field values on Contacts transfer to Monday.com People column values during import. The phone field maps from Sanoflow's contact phone property to Monday.com People's phone column. Owner assignment in Sanoflow maps to a Monday.com workspace member, though Monday.com CRM does not have a Salesforce-style OwnerId lookup on every record type. We extract all active Contact records and validate email and phone format consistency before import to avoid Monday.com column validation errors.

Sanoflow Enquiries represent inbound customer messages or form submissions and have no direct Monday.com CRM equivalent. We scope the customer's use of Enquiries during discovery: Enquiries that track customer issues or support requests map to Items on a dedicated Support Board; Enquiries that represent sales pipeline opportunities map to Monday.com Deals. The Enquiry body, source Channel, status, and assigned agent transfer as Board Item fields and assignee columns. Tag associations and custom Enquiry Field values map to Monday.com column values. Teams using Enquiry Forms as a primary lead-capture method should plan to deploy Monday.com Forms as the replacement entry point.

Sanoflow Pipelines (Kanban-style workflow boards) map directly to Monday.com Boards. Pipeline names become Board names, and Pipeline Stages become Groups within the Board, preserving stage order. Stage-specific automation rules in Sanoflow do not transfer — these are documented in the Workflow Specification Document for manual rebuild in Monday.com Automation Recipes. Sanoflow's tier limits (5 on Starter, 20 on Growth, 50 on Premium) are enforced at migration time; we flag any customer with Pipeline counts exceeding their Sanoflow plan so the migration plan can account for consolidation or plan upgrade before extraction.

Each Sanoflow Pipeline Stage maps to a Group within the corresponding Monday.com Board. Stage names and order transfer 1:1. Sanoflow stage-specific completion criteria do not have a Monday.com equivalent and are documented for manual configuration post-migration. Stage probability percentages (if set in Sanoflow) do not map to Monday.com Groups — probability tracking belongs on a Deals Board if the customer uses Monday.com Deals, or on a custom numeric column.

Sanoflow Channels (WhatsApp, Instagram, Messenger, TikTok) represent messaging platform connections and cannot migrate to Monday.com CRM. WhatsApp Business API credentials are tied to the Sanoflow Meta Business account and cannot be transferred to a new platform. We document all active Channel configurations during scoping, noting the channel type and connection status, and recommend a Meta Business account reconnection process with the customer's IT or marketing team post-migration.

Sanoflow Flows are no-code automation workflows built with Triggers, Messages, and Actions and have no documented export endpoint. We cannot extract Flow definitions programmatically. We extract Flow metadata — name, trigger type, step count, and active status — and generate a Workflow Specification Document describing each Flow's trigger conditions, step sequence, and action types. The customer's team rebuilds equivalents in Monday.com Automation Recipes post-migration. Sanoflow's WhatsApp Drip Flows require a replacement WhatsApp automation tool if campaign sequences are central to the sales process.

Sanoflow Custom Fields on Contacts and Enquiries (Growth tier and above) map to Monday.com Board columns. Field types supported include text, number, date, and choice/dropdown, which map to Monday.com Text, Numbers, Date, and Dropdown column types respectively. Choice-field options transfer as Dropdown column labels. We flag any Sanoflow field types without a Monday.com equivalent (such as complex conditional fields) during scoping and document them for manual column configuration post-import.

Sanoflow Teams and role assignments govern which agents see and manage which Enquiries. We extract team membership and role names from Sanoflow and map them to Monday.com workspace members. Monday.com CRM's permission model is less granular than Sanoflow's custom roles — workspace members have viewer or editor access per Board, without a direct equivalent of Sanoflow's per-Enquiry routing rules. We document the role-to-permission mapping for the customer to configure post-migration and flag any team structures that will require simplification.

Webhook configurations in Sanoflow (Premium and Enterprise only) point to destination-specific URLs and cannot be transferred between platforms. Webhook endpoints reference live Sanoflow-internal systems or third-party services that will not function after migration. We document all active Webhook configurations during scoping and note the endpoint URL and trigger event so the customer's IT team can reconfigure equivalent webhooks in their target systems post-migration.

Sanoflow Enquiry Forms are inbound entry points that create Enquiry records. We extract form field definitions during scoping and map them to Monday.com Form fields. Form routing rules (which Flow a submitted Enquiry triggers) do not transfer and are documented in the Workflow Specification Document. Form submission data from historical Enquiry records migrates as Board Item fields as described under Enquiry mapping. The customer deploys a new Monday.com Form linked to the target Board as the replacement lead-capture mechanism.