Migrate from Sales Flow Technologies to Nutshell

Salesflow Contacts migrate to Nutshell Contacts with all standard fields (name, email, phone, company, job title, LinkedIn URL) plus any custom fields. The LinkedIn URL migrates as a custom text field since Nutshell does not have a native LinkedIn field. We deduplicate by email during import and flag any records with missing email for the customer's admin to resolve before the next phase.

Salesflow Prospect Lists are named groupings of Contacts used to organize outreach targets. Nutshell does not have a native list object, so we recreate list membership as Nutshell Tags on each Contact record. Each unique Salesflow Prospect List name becomes a Tag, and Contacts retain all list memberships as multiple Tag values. The customer chooses whether to rename Tags to match Nutshell naming conventions during scoping.

Salesflow Sequences define cadence and channel steps (LinkedIn connection, follow-up email, InMail) for enrolled Contacts. Nutshell has no native sequence or cadence object, so we preserve sequence metadata as custom fields on the Contact: sf_sequence_name__c, sf_sequence_step_count__c, sf_enrolled_date__c, and sf_last_step_completed__c. Step ordering and timing data are stored in a separate Sequence Steps CSV attached to the Contact for admin reference. The customer rebuilds cadence logic in Nutshell Automations using this documentation.

Salesflow Campaigns bundle multiple Sequences under a single objective. Since Nutshell does not have a Campaign object in the CRM core, we map Campaign membership to a lookup table stored as a custom field on the Contact (sf_campaign_name__c) and as a Nutshell Person record named after the Campaign for cross-referencing. Associated Sequence data attaches to the same contact records.

Salesflow Workflows define conditional branching logic (e.g., 'if no reply after 3 days, send template B'). Workflow configuration is not accessible via CSV or API export and lives in Salesflow's application state. We produce a written Workflow Migration Summary documenting every active Workflow: trigger conditions, step order, timing delays, action types (email, InMail, task creation), and conditional branches. The customer's admin rebuilds these in Nutshell Automations post-migration. This is the most significant automation gap and the most common source of post-migration surprise.

Salesflow User accounts (Admin, Standard roles) map to Nutshell Users by email match. We extract every distinct owner referenced on Contact, Sequence enrollment, and Campaign records. Any Salesflow User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role labels (Admin vs Standard) migrate as a custom field on the Nutshell User for access-control reference.

Salesflow provides per-sequence open rates, reply rates, and connection acceptance rates as Analytics exports. Nutshell does not have equivalent native reporting dimensions for LinkedIn outreach metrics, so we migrate these as custom fields on the Contact: sf_sequence_open_rate__c, sf_reply_rate__c, and sf_connection_acceptance_rate__c. These values serve as historical reference; the customer uses Nutshell's standard activity reporting for post-migration metrics.

Inbox messages in Salesflow represent the conversation thread between the rep and the prospect across LinkedIn and email. These are stored in LinkedIn's infrastructure and are not accessible via Salesflow export or API. We do not migrate Inbox messages. Reps continue accessing historical LinkedIn conversations directly in LinkedIn or LinkedIn Sales Navigator. We document this gap in the Migration Summary so the customer's team sets appropriate expectations.