Migrate from Zixflow Marketing Automation to Salesforce Sales Cloud

Zixflow Contacts map to Salesforce Lead for unevaluated or prospect-status contacts and to Salesforce Contact for enriched or converted contacts. We evaluate the contact's status property, enrichment flag, and Collection membership to determine the split at migration time. Any contact with an assigned owner in Zixflow who matches a Salesforce User maps to Contact with an AccountId resolved from a matching Company record. The original Zixflow contact ID is preserved in a custom field zixflow_contact_id__c on both Lead and Contact for audit and cross-reference.

Zixflow Collections are list/grouping containers that can be static or dynamic. We map each Collection to a Salesforce List (if the collection is used for email segmentation) or to a Salesforce Campaign (if the collection drives multi-touch nurturing with Campaign Member Status). Collection membership is preserved by creating ListMembership or CampaignMember records at migration time. Contacts in multiple Collections generate multiple membership records. We flag any Collection with dynamic filter logic because dynamic membership does not export; the customer must configure equivalent list filters in Salesforce.

Zixflow WhatsApp Subscribers map to Salesforce CampaignMember records on a WhatsApp Business Campaign. Opt-in status, subscriber tags, and subscription date migrate as CampaignMemberStatus, custom fields, and CampaignMember custom fields respectively. We flag if the imported subscriber count exceeds the destination WhatsApp Business API approved contact volume; Facebook Business API re-approval may be required before message delivery resumes post-migration. The default 500-subscriber Zixflow cap is noted as a migration boundary check.

Zixflow message logs export with channel type, direction (inbound/outbound), contact association, timestamp, and delivery status. WhatsApp and SMS messages map to Salesforce Task records with TaskSubtype set to the channel. Email messages map to Salesforce EmailMessage records linked to a Task activity. We preserve the original timestamp in ActivityDate to maintain conversation chronology. Delivery status (sent/delivered/open) from Zixflow migrates as custom fields because Salesforce does not natively track WhatsApp/SMS delivery state on Task records. Message content and media attachments migrate as Salesforce ContentDocumentLink records on the parent.

Zixflow Inbox threads aggregate multichannel conversations and are linked to Contacts by contact_id. We export thread metadata (thread_id, created_at, last_message_at, channel) and map thread-level entries to Salesforce Task records with the resolved Contact or Lead WhoId. Thread-to-contact re-linking requires us to resolve the Zixflow contact_id to the new Salesforce Lead or Contact ID during the parent-record lookup phase. Thread associations are restored by matching the conversation metadata to the migrated contact record.

Zixflow Forms capture leads and feed data into Contacts and Collections. We export form field definitions (field name, type, required flag) and map them to Salesforce Web-to-Lead custom fields. Form submission history migrates as Contact records with a custom field form_source__c indicating the originating Zixflow Form. Salesforce Web-to-Lead does not replicate Zixflow's visual form builder; we document each form's field set for the customer's admin to rebuild as a Salesforce Web-to-Lead or Experience Cloud form post-migration.

Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. We match each property to a Salesforce custom field by name and inferred type (text, number, date, checkbox, picklist). AI enrichment fields from Zixflow (such as confidence scores or derived attributes) map to Salesforce custom fields with a zixflow_enrichment__c prefix. Any property that has no Salesforce type equivalent is flagged for the customer to define as a custom field before migration. Zixflow does not have standalone custom objects separate from Contact properties.

Zixflow Company records (if present in the customer's data model) map to Salesforce Account. Company domain, address fields, and industry properties migrate to Account Website, BillingAddress, and Industry. The Account is created before Contact import so that AccountId is satisfied at Contact insert. If Zixflow Companies are linked to multiple Contacts, each Contact receives the same AccountId reference.

Zixflow Wallet credits are a financial balance, not customer data. We exclude wallet balance from migration scope and note the current balance as a reference for the team to drain or forfeit before closing the Zixflow account. We recommend the team purchase any required messaging credits in Salesforce or a connected WhatsApp Business API provider before account closure.

Flow automation credits are a billing metric, not a data record. Credit usage history does not migrate. We note the current Flow credit balance as a reference for the team to adjust their Salesforce Flow usage budget. In Salesforce, Flow invocations are included in platform license limits rather than metered per action.

Zixflow Flows are visual workflow definitions in a proprietary builder format with no export path. We export a documentation snapshot of each Flow including name, trigger type, step summary, condition logic, and action sequence. This inventory is delivered as a written document for the customer's admin or a Salesforce partner to rebuild as Salesforce Flow. Active Flows are flagged separately from archived Flows so the rebuild scope is prioritized correctly.

Zixflow Owners map to Salesforce User records by email match. Any Zixflow Owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Active Owners in Zixflow must have a corresponding active or inactive User in Salesforce depending on whether the person retains a license post-migration. Owner assignments on migrated records (Contacts, Leads, Accounts) are resolved at this step.