Migrate from Sanoflow to HubSpot

Sanoflow contacts map directly to HubSpot contacts. The Sanoflow phone number becomes the HubSpot phone property. If a Sanoflow contact has multiple channel associations (WhatsApp + Instagram DM), we store the primary channel as a HubSpot contact property and the secondary as a custom property. Contacts without an email address are migrated with phone as the primary identifier.

Sanoflow records the channel (WhatsApp, Instagram DM, Messenger, TikTok) on which a contact was first reached. HubSpot has no native equivalent — we create a custom contact property (channel_source__c) as a pick-list with the four channel values. This property is used to segment contacts by acquisition channel in HubSpot reports and workflows.

Sanoflow custom contact properties (beyond name, email, phone) are created as HubSpot custom contact properties with matching types — pick-list values become HubSpot pick-list options, numeric fields become number properties, and text fields become single-line text. We preserve the Sanoflow property name as a label for admin clarity during the transition period.

Sanoflow stores individual WhatsApp messages as separate records with timestamp, direction (inbound/outbound), content, and delivery status. HubSpot has no WhatsApp message object — we transform each message into a HubSpot Activity (Task with Type='WhatsApp Message') attached to the contact, preserving the original timestamp and direction. Delivery status (sent, delivered, read) is stored as a custom field on the activity record.

Sanoflow enquiry flows are the primary sales automation object — a contact entering a flow creates a flow run record. HubSpot has no native flow-run object. We map each flow run to a HubSpot deal, with the Sanoflow flow name stored as the deal name, flow status as deal stage, and flow metadata (steps completed, current step, flow ID) as custom deal properties. If Sanoflow tracks deal value within a flow, that amount maps to the HubSpot deal amount.

Each Sanoflow flow step (welcome message, qualification question, proposal send, etc.) is tracked as a custom deal property. The current step and step status (completed, skipped, waiting) are stored as text and pick-list fields on the HubSpot deal record. This preserves the enquiry funnel progress without a native flow-run equivalent in HubSpot.

Sanoflow business profiles (company name, industry, website, employee count if stored) map directly to HubSpot company properties. If Sanoflow stores multiple contacts per company, the HubSpot company is created first and all associated contacts are linked via the primary company association. Parent-child company hierarchies in Sanoflow map to HubSpot's company hierarchy model.

Sanoflow broadcast campaigns send WhatsApp messages to contact lists. HubSpot has a Campaign object for marketing attribution. Each Sanoflow broadcast campaign is mapped to a HubSpot campaign, with the list of recipients linked as campaign members. HubSpot campaign membership tracks which contacts received which broadcast, enabling attribution reporting if the Marketing Hub is active.

Sanoflow team members and agents map to HubSpot users by email address match. Each Sanoflow agent's assigned conversations and flows are linked to the corresponding HubSpot user as the contact and deal owner. Unmatched Sanoflow agents are flagged before migration — teams either create HubSpot users first or assign records to a fallback owner.

Sanoflow WhatsApp media files (images, PDFs, documents) are re-uploaded to HubSpot Files and attached to the relevant contact or deal record. HubSpot's file storage limits apply (25MB per file). Very large files or video media may be stored externally with a link URL stored on the HubSpot record, as HubSpot is not optimized for large media hosting.

Sanoflow tags applied to contacts or companies (e.g., 'VIP customer', 'follow-up pending') are mapped to HubSpot contact or company properties as single-line text or multi-checkbox fields depending on tag count. High-frequency tags are converted to HubSpot contact properties; low-frequency tags are stored as a comma-separated text field for reference.

Sanoflow flow automations (trigger-action sequences built in the Sanoflow flow builder) have no native equivalent in HubSpot and cannot be migrated. They must be rebuilt in HubSpot's Workflows object using enrollment criteria and action sets. FlitStack exports the Sanoflow flow definitions as a structured document the team can use as a reference when rebuilding in HubSpot.

Sanoflow WhatsApp Business API template messages are stored outside HubSpot's data model. These template definitions are exported as a reference document. Teams using HubSpot's WhatsApp integration will need to recreate approved WhatsApp templates in the Meta Business Manager and connect them to HubSpot workflows manually.

Sanoflow tracks WhatsApp message delivery status (sent, delivered, read) and read timestamps. HubSpot activities do not natively store delivery receipt data. We store the most recent delivery status as a custom property on the activity record (e.g., whatsapp_delivery_status__c) as a reference field. Historical receipt data is preserved in the migration audit log.