Migrate from Snovio to Nutshell

Snovio Prospect records map to Nutshell Contact with standard fields (name, email, company, role) mapped 1:1. If the customer maintains a separate unqualified-prospect queue, we split by a qualification flag to Nutshell Lead; qualified prospects map directly to Contact with an Account reference. Snovio's custom fields (up to 30 per prospect) map to Nutshell typed custom fields (text, number, date, picklist, checkbox) based on the Snovio field schema exported during discovery. We validate field type compatibility before migration and flag any Snovio fields that cannot be typed in Nutshell (e.g., HTML content stored as a text field).

Snovio supports up to 30 custom fields per prospect. We export the full custom field schema alongside the data during discovery — field name, type, and placeholder variable (e.g., {{personalization}}). Each field is mapped to a corresponding Nutshell custom field of equivalent type. Fields with more than 65,000 characters of content are truncated at Nutshell's storage limit. Fields that do not have a matching type in Nutshell are flagged for admin decision before migration begins.

Snovio campaign structures (sequence steps, timing rules, channel assignments) are exported as structured metadata rather than executable automation. Nutshell does not run outreach sequences natively on the Foundation plan, and its Sales Automation on Growth and above uses a different trigger-action model. We deliver a written campaign-structure document listing every campaign name, step count, delay between steps, channel, and variable usage so the customer's admin can rebuild sequences in Nutshell's Sales Automation or a third-party sales engagement tool.

Snovio Recipients are unique leads charged on first email contact. Each Recipient maps to a Nutshell Contact record with the standard field mapping applied. Engagement status (delivered, bounced, replied) from Snovio is preserved as a custom field or activity entry in Nutshell. We recommend not using Snovio's open and click metrics as a reporting baseline post-migration due to documented pixel-tracking accuracy issues; Nutshell's own activity log becomes the primary engagement record.

Snovio Pipeline Deals map to Nutshell Opportunities. We map deal name to Opportunity name, deal value to Amount, and owner assignment to Owner. Pipeline stage names from Snovio are preserved in a custom field (snovio_original_stage__c) for audit purposes and are mapped to Nutshell pipeline stage values during migration. Contact references from Snovio deals are resolved to Nutshell Contact lookups via email matching before Opportunity insert.

Snovio email accounts (connected mailboxes) and warmup configurations are exported as a reference document listing mailbox address, rotation settings, and warmup status. Actual SMTP credentials and OAuth tokens cannot be exported from Snovio and cannot be imported into Nutshell, which connects via native Gmail or Outlook integration instead. We document the warmup settings so the admin can configure warm-up in Nutshell's connected email account settings post-migration.

LinkedIn automation data only exists in Snovio if the LinkedIn add-on ($69/month) is active. LinkedIn sequence structure and recipient lists are exported as a reference document but cannot be executed in Nutshell because Nutshell does not have native LinkedIn automation. We document the sequence name, step count, channel assignments, and recipient list sizes so the admin can evaluate third-party LinkedIn sales engagement tools (e.g., Phantombuster, OctopusCRM) if multichannel sequences are required post-migration.

Snovio email engagement events (opens, clicks, replies, bounces) migrate as Nutshell Activity records linked to the Contact. The original Snovio timestamp is preserved on the Activity. Open and click counts are documented as metadata but we flag that Snovio's pixel-based tracking is unreliable and should not be used as a performance baseline. Reply and bounce events, which are harder to spoof at the MTA level, are treated as higher-confidence data and prioritized in the activity timeline.