Migrate from VBOUT to Nutshell

VBOUT Contacts map directly to Nutshell People. Standard fields (name, email, phone, address) migrate 1:1. Custom fields on VBOUT Contacts require pre-creation in Nutshell before import; we create matching Person custom fields during the schema design step. VBOUT Tags on Contacts migrate as Nutshell Tags applied to the Person record. Lead score, source attribution, and custom property values transfer to equivalent Nutshell custom fields. The VBOUT contact's associated pipeline stage encoded as a tag is mapped to a Nutshell custom field for stage preservation.

VBOUT Leads migrate to Nutshell Leads with lead score, source attribution, and owner assignment preserved. The VBOUT Lead status maps to Nutshell Lead status. Any Tags on VBOUT Leads apply as Nutshell Tags on the Lead record. VBOUT custom fields on Leads mirror the Contact custom field migration process and require pre-creation in Nutshell before the Lead import phase begins.

VBOUT Companies map to Nutshell Accounts. Company name, domain, address, phone, and industry fields migrate 1:1. We use VBOUT's company domain as a dedupe key during import to prevent duplicate Accounts. Custom fields on VBOUT Companies require pre-creation as Account custom fields in Nutshell before the import phase. Tags on VBOUT Companies apply as Nutshell Tags on the Account.

VBOUT Deals map to Nutshell Deals with deal value, stage name, stage probability, expected close date, and owner preserved. VBOUT pipeline stage assignments encoded as Tags are mapped to Nutshell's Deal stage field, and we configure Nutshell's stage probability to match the VBOUT pipeline's stage weights. Any deal-associated custom fields migrate to Nutshell Deal custom fields, which must be pre-created before the Deal import phase.

VBOUT pipeline stages are configured in Nutshell as Deal stages with matching stage names and probability weights. Each VBOUT pipeline (if the account uses multiple) is represented as a separate Deal stage configuration in Nutshell. Stage order from VBOUT is preserved in Nutshell's stage sequencing. We configure stage probability percentages to match the VBOUT values for accurate forecasting continuity.

VBOUT Smart Audiences are dynamic segmented lists based on behavioral and demographic criteria. The segmentation rules are proprietary and do not export directly. We export the audience member list (the current snapshot of contacts meeting the criteria) and apply Nutshell Tags to the matching Person and Lead records. The segmentation logic is documented in a rebuild guide for the customer to recreate as Nutshell tag filters or as a reported saved-filter view.

VBOUT sent email campaign history (subject, send date, open rate, click rate, unsubscribe count) migrates as a Note record attached to the campaign's associated Contact or Lead. Email template bodies export from VBOUT and are documented for manual rebuild in Nutshell's email template editor; the visual template layout does not transfer. Campaign-level metrics are preserved as text in the Note for historical reference.

VBOUT automation workflows (multi-step trigger-action sequences) are stored in a proprietary JSON schema that has no direct equivalent in Nutshell, which does not include a native automation builder. We export the full workflow definition as a structured JSON artifact and produce a step-by-step rebuild guide mapped to Nutshell's manual process recommendations. The customer's admin rebuilds active automations in Nutshell or via an external automation tool post-migration. This is a configuration gap, not a data migration gap.

VBOUT Tags on Contacts, Leads, and Companies export as flat tag lists and are re-applied to matching Nutshell Person, Lead, and Account records. Tags used for pipeline stage encoding, lead scoring context, or Smart Audience membership are preserved as-is. Tag cardinality is maintained; tags with fewer than five associated records in VBOUT are flagged during scoping as candidates for consolidation or exclusion.