Migrate from Sanoflow to Microsoft Dynamics 365 Sales

Sanoflow Contacts migrate to Microsoft Dynamics 365 Sales Contact. The Contact record carries name, phone (WhatsApp number), email, and owner assignment. Custom Fields on Contact migrate to typed fields on the Dynamics Contact entity. We use the contact's email address as the dedupe key. Owner resolution maps Sanoflow owner email to the corresponding Dynamics User. If a Contact in Sanoflow is associated with an Enquiry from a WhatsApp conversation, the Enquiry history migrates as Activity records attached to the Contact.

Sanoflow Enquiries represent individual WhatsApp conversations or inbound messages linked to a Contact. We migrate Enquiry body, source channel, status, assigned agent, and timestamp as a Task record in Microsoft Dynamics 365 Sales with TaskSubtype=Task and the channel (WhatsApp, Instagram, Messenger) stored in a custom field. The Enquiry's message thread is preserved as a Note attached to the Task record. Multiple Enquiries per Contact produce multiple Task records, preserving the full conversation timeline in the Contact's Activity timeline.

Sanoflow Pipelines are Kanban boards that manage Enquiry flow. We map each Pipeline to a Microsoft Dynamics 365 Sales Record Type on Opportunity, paired with a Sales Process that defines the stage values. If a Sanoflow customer has 4 active Pipelines (e.g., Sales, Support, Onboarding, Re-engagement), we create 4 Record Types so that each pipeline's stages are isolated. Pipeline stage names and order migrate to the corresponding StageName values in the Sales Process.

Each stage within a Sanoflow Pipeline becomes a stage value in the corresponding Dynamics Sales Process. Stage probability percentages migrate to the StageProbability field on each stage. Stage completion criteria in Sanoflow are noted in the Workflow Specification Document for manual recreation in Microsoft Dynamics 365 Sales Flow or as Opportunity field validation rules.

Sanoflow Custom Fields on Contacts (text, number, date, choice) migrate to typed fields on the Microsoft Dynamics 365 Sales Contact entity. Choice-field option values map to Dynamics Picklist values. Growth-tier and above customers typically have multiple custom fields; we pre-create all custom field definitions in the Dynamics destination org before the Contact import phase begins.

Sanoflow Custom Fields on Enquiries migrate to custom fields on the Task entity in Microsoft Dynamics 365 Sales . Field types are mapped: text to Single Line of Text, number to Whole Number or Decimal, date to Date Only, choice to Option Set. These fields allow the customer's team to retain Enquiry-level attributes (source URL, campaign tag, custom ticket type) in the migrated records.

Sanoflow Teams and role assignments govern which agents see and manage which Enquiries. We map team membership and role names to Microsoft Dynamics 365 Sales Teams. Sanoflow role granularity (Admin, Manager, Agent) maps to Dynamics Security Roles that the customer's admin assigns post-migration. Full permission-level parity requires manual configuration in Dynamics because Sanoflow's permission model is not exportable.

Sanoflow Enquiry Forms are inbound entry points that create Enquiry records. Form field definitions migrate as metadata for documentation, but actual form functionality requires rebuild in Microsoft Dynamics 365 Sales . Inbound form submissions from Sanoflow can map to Dynamics Leads if the destination uses a lead-capture strategy, or to Contacts if the customer prefers a contact-first model. We note the routing decision during scoping.

Sanoflow WhatsApp Broadcast records (audience segments, message templates, send history) migrate as Campaign records in Microsoft Dynamics 365 Sales with the audience list imported as Campaign Members. The WhatsApp message template content is preserved in a Note attached to the Campaign for documentation. Template approval status does not carry over; all WhatsApp message templates must be re-submitted for Meta approval in the destination Meta Business account.

Sanoflow Channels represent connected messaging platforms tied to specific WhatsApp Business API credentials or social accounts. Channel configurations cannot be migrated because WhatsApp Business API credentials and Instagram/Facebook page tokens are bound to the Sanoflow Meta Business account. We document the Channel configuration (platform, phone number, account name) in a Channel Inventory Note so the customer can re-configure Channels in their new platform's Meta Business account. TikTok integration is a separate API setup in the destination platform.