Migrate from Zixflow to Nutshell

Zixflow Contacts map to Nutshell Person for existing customers and to Lead for prospects not yet in a sales pipeline. We compute the split at migration time using Collection membership signals: Contacts assigned to sales-oriented Collections map to Nutshell Person; Contacts in top-of-funnel or unassigned Collections map to Nutshell Lead. Email, phone, name, and address fields map directly. Nutshell requires a Person to have at least a name or email; Contacts missing both are flagged during reconciliation.

Zixflow Collections (list/grouping constructs) map to Nutshell People Lists and Companies Lists. We preserve Collection membership by generating a membership mapping table alongside the primary export and appending it as a custom field or tag on each Nutshell Person or Company record. If a Contact belongs to multiple Collections, all Collection names are concatenated into a single multi-value field in Nutshell.

Zixflow custom fields on Contacts map to Nutshell custom fields on Person. We export the full custom field schema (field name, type, and options) first, then provision matching custom fields in Nutshell via the Custom Fields API before importing any record data. AI-generated custom fields from Zixflow transfer as read-only or text fields in Nutshell depending on their value type.

Zixflow Flows define automation logic as a node-graph in the visual builder. This structure is not exportable as portable automation code. We inspect each active Flow during scoping, document its trigger conditions, action sequence, and delay logic, and deliver a written rebuild runbook. The customer's admin uses this to recreate the logic in Nutshell's workflow rules or a third-party automation layer. Flows with WhatsApp bot logic cannot be rebuilt in Nutshell's core CRM and require a dedicated WhatsApp Business solution.

Zixflow Inbox conversations (threaded messages across WhatsApp, SMS, Email, and RCS) migrate as Nutshell Activity records. Each message in a thread becomes a Note or Task attached to the corresponding Person or Company. Thread ordering is preserved using timestamps. The conversation-level threading model in Zixflow is flattened in Nutshell; channel metadata (WhatsApp vs SMS vs Email) is stored as a custom field on each Activity record.

Zixflow Form submissions migrate as Contact custom field values (for form field answers) plus a Note record logging submission metadata (form name, submission timestamp, referring URL). The visual form builder structure does not transfer; we document each form's field structure as part of the scope deliverable. Nutshell's web-to-lead or Experience Cloud forms serve as the rebuild target.

Zixflow user accounts migrate as Nutshell User records by email match. Role and permission structures must be recreated at the destination since Zixflow's workspace-scoped permissions do not map to Nutshell's role model. We provide a user mapping table listing each Zixflow user, their email, and their current role so the Nutshell admin can assign the equivalent role during setup.

Zixflow was previously known as Sales Simplify. Some legacy customers may have deal records that originated in the Sales Simplify era and were not migrated during the rebrand. These records have no native Deals object in current Zixflow schema. We detect them during scoping (if present in a legacy export), then reconstruct them as Contact records with a Deals-related custom field carrying deal name, stage, amount, and close date. The customer decides during scoping whether to merge these into existing Contact records or keep them as a separate import batch.