Migrate from Sanoflow to Pipedrive

Sanoflow Contacts migrate directly to Pipedrive People. The Contact's name, phone (primary for WhatsApp), email, and Custom Field values map to the equivalent Pipedrive Person fields. Owner assignment (the agent assigned to manage the contact) migrates by email match against Pipedrive Users. If a Sanoflow Contact has no email, we use phone as the deduplication key. Custom Field definitions (text, number, date, choice) on Sanoflow Contacts are pre-created as custom fields in Pipedrive before migration; choice-field option sets must be recreated manually in Pipedrive as the option labels are not exported programmatically.

Sanoflow Enquiries represent inbound customer messages or form submissions and map to Pipedrive Deals. Each Enquiry's body, source channel (WhatsApp, Instagram, Messenger, TikTok), status, and assigned agent transfer to the Deal's title, notes, stage, and owner. The linked Contact becomes the Deal's Person association. If a single Contact has multiple Enquiries, each Enquiry becomes a separate Deal; we preserve the original Enquiry identifier in a custom field sanoflow_enquiry_id__c for audit and cross-reference.

Sanoflow Pipelines (the Kanban board structure) map to Pipedrive Pipelines with stage names and order preserved 1:1. We extract the pipeline name and the ordered list of stage names from Sanoflow's admin panel export and configure matching Pipelines in Pipedrive before Deal migration begins. If Sanoflow's pipeline count exceeds Pipedrive's pipeline limits on the target plan (Essential allows 1; Advanced allows 5; Professional and above allow unlimited), we flag the excess and recommend consolidation or plan upgrade during scoping.

Each Sanoflow Pipeline Stage becomes a Pipedrive Stage within the corresponding Pipeline. Stage order, names, and completion criteria migrate as Stage configuration. Stage-specific automation rules (e.g., auto-assign on stage entry) in Sanoflow cannot be transferred; we document them in the Workflow Specification Document for manual Pipedrive Automation rebuild. Stage probability values from Sanoflow map to Pipedrive Stage probability fields where present.

Sanoflow Custom Fields on Contacts (available at Growth tier and above) map to Pipedrive Person custom fields. We pre-create field definitions in Pipedrive with matching types (text, number, date, single-select) before contact migration. Multi-select choice fields from Sanoflow map to Pipedrive multi-select custom fields. Option labels from Sanoflow choice fields must be recreated as Pipedrive field options since the export does not include the option set definition.

Sanoflow Custom Fields on Enquiries map to Pipedrive Deal custom fields with the same pre-creation and type-mapping approach as Contact custom fields. Enquiry-specific fields (e.g., enquiry_source, enquiry_status_detail) become deal-level custom fields in Pipedrive. The mapping preserves the field-to-record relationship so that historical Enquiry metadata is queryable on the migrated Deal.

Sanoflow Teams and role assignments govern which agents see and manage Enquiries. We preserve team membership and role names from the admin panel export. Pipedrive Teams are configured in Settings > Teams. If Sanoflow roles have granular permissions not supported in Pipedrive's team model, we flag the delta and recommend a simplified team structure for the Pipedrive destination.

Sanoflow Enquiry Forms are the inbound entry point for customer submissions. We migrate form field definitions and map them to Pipedrive Lead fields or custom fields on the resulting Deal. Form routing rules (which Flow a submitted form triggers) are documented in the Workflow Specification Document as they cannot be transferred across platforms. We recommend Pipedrive's Web Forms or a native form embed as the replacement inbound capture mechanism.

Sanoflow Channels (WhatsApp, Instagram, Messenger, TikTok) represent connected messaging platform integrations. Channel configurations cannot be migrated across platforms because WhatsApp Business API credentials are destination-specific and tied to the connected Meta Business account. We extract Channel metadata (connected platforms, Channel names, assigned agents) and document it in the migration handoff. The WhatsApp Business account must be reconnected in Pipedrive after migration with new API credentials.

WhatsApp conversation history cannot be transferred as native message objects because Sanoflow has no documented API. We extract what is available via admin panel exports (conversation timestamps, participant phone numbers, message counts per conversation) and attach this as a structured note on the related Pipedrive Person record. Media attachments and full message content require separate documentation; we flag this limitation explicitly during scoping. Actual message content remains in the WhatsApp Business account and is accessible through the WhatsApp Business app or web client.