Migrate from Zixflow Marketing Automation to Nutshell

Zixflow Contacts map to Nutshell Person records. Standard fields (name, email, phone, address) migrate directly. Custom contact properties, including any AI-generated enrichment fields, map to Nutshell custom fields on Person. We resolve duplicate Person records by email address during import and flag any records with invalid email addresses for review before insertion. The original Zixflow contact ID is preserved in a custom field zixflow_original_id__c for audit trail purposes.

If the Zixflow account uses the Company object to store organizational records alongside Contacts, these map to Nutshell Company records. The Company name, domain, and address fields migrate directly. We link Person records to Company via Nutshell's Company association. If Zixflow Companies store custom properties, these map to Nutshell custom fields on the Company object. Company records are created before Person records so that the relationship is satisfied at insert time.

Zixflow Collections (named contact groupings) map to Nutshell Lists. Collection membership is preserved by linking each Person in the Collection to the corresponding Nutshell List via the List membership API. A Person may belong to multiple Collections; we create corresponding Nutshell Lists and assign all relevant memberships. Nutshell Lists are created during the schema phase before Person import so that membership can be written during the Person insert phase.

Zixflow Forms capture leads and populate Contact fields. Form field definitions (field names, types, required flags) export as a field inventory document. We do not migrate forms as functional assets because Nutshell does not host forms natively. Instead, we deliver a field inventory showing each Zixflow form field mapped to the Nutshell Person custom field where it should land. The customer recreates forms in their preferred form tool (Typeform, HubSpot Forms, or native Nutshell web-to-person capture) and maps form fields to the Nutshell custom fields we created.

Zixflow Inbox threads aggregate multichannel conversations. Thread metadata (subject, participants, timestamps) and individual message records export via API. We map conversation threads to Nutshell Notes attached to the corresponding Person record. Message attribution (sender, recipient, timestamp) is preserved in the Note body. Nutshell does not have a native multichannel inbox, so WhatsApp and SMS thread continuity is not preserved as an inbox view; instead, the conversation record is stored as an activity note on the Person. Thread IDs from Zixflow are stored in a custom field for reference.

Message logs export from Zixflow with contact association, channel, direction, content, and timestamp. We map each message to a Nutshell Note attached to the corresponding Person record, recording the channel (WhatsApp, SMS, Email, RCS), direction (sent/received), and timestamp. Delivery status (sent/delivered/open) from Zixflow is recorded as a custom Note field; Nutshell does not have native delivery tracking for messages outside its email integration. The customer should be aware that Nutshell's native email tracking applies only to emails logged within Nutshell, not to imported historical messages.

WhatsApp Subscribers in Zixflow carry opt-in status, tags, and subscriber metadata. We export subscriber records and map them to Nutshell Person records with the WhatsApp opt-in status stored as a custom field. Subscriber tags map to Nutshell Tags on the Person record. The subscriber list membership is created as a Nutshell List named 'WhatsApp Subscribers' to preserve the segment for future WhatsApp campaign sends. Nutshell does not have native WhatsApp Business integration; the customer configures WhatsApp separately if needed.

Zixflow custom contact properties, including AI-generated enrichment fields, export as flat key-value pairs. We create matching Nutshell custom fields on the Person object (and Company if applicable) during the schema phase, using the closest matching field type (text, number, date, checkbox, dropdown). AI-generated enrichment field values migrate as text or numeric values depending on the data type. Fields with no direct Nutshell equivalent are created as text fields and flagged in the field inventory document for the customer to review and recategorize if needed.