Migrate from Sharpspring to Nutshell

SharpSpring People map directly to Nutshell People. All standard fields (name, email, phone, address, title) transfer with original values. The SharpSpring contact's company link resolves to a Nutshell Company record using domain or name matching. Owner is resolved by email against Nutshell users.

SharpSpring Companies map to Nutshell Companies. Company name, domain, industry, employee count, and annual revenue transfer directly. Parent/child company hierarchies in SharpSpring map to Nutshell's parent company field. Multi-company associations on a SharpSpring contact collapse to the primary Company in Nutshell.

SharpSpring Leads (distinct from People) map to Nutshell Leads. Lead name, email, phone, company, status, and source fields transfer directly. Nutshell's Lead status pick-list is populated with SharpSpring's lead status values. Custom fields on SharpSpring Leads migrate to Nutshell custom fields on the Lead record.

SharpSpring Deals map to Nutshell Deals. Deal name, amount, expected close date, and responsible user transfer directly. SharpSpring deal stage names map to Nutshell pipeline stage names via a value-mapping table. The deal's primary contact link resolves to a Nutshell Person record.

SharpSpring supports multiple independent pipelines. Nutshell uses a single customizable pipeline. When SharpSpring has one pipeline, its stages map directly to Nutshell stages. When multiple pipelines exist, we map each to Nutshell stages and tag deals with a custom 'Source Pipeline' field to preserve the original grouping context.

SharpSpring call logs migrate as Nutshell Activities with type='Call'. Subject, date/time, duration, outcome, and related person/company links are preserved. The original call timestamp and owner are transferred to maintain activity history continuity. Call disposition codes from SharpSpring map to Nutshell's outcome field using value mapping.

SharpSpring email logs migrate as Nutshell Activity records with type='Email'. Subject, body, send date, and recipient are preserved. Email attachments are re-hosted in Nutshell's file storage. Nutshell's Activity timeline displays these alongside other contact interactions. Email tracking data (opens, clicks) from SharpSpring is stored as custom fields since Nutshell Activities do not natively capture engagement metrics.

SharpSpring meeting records migrate as Nutshell Activities with type='Meeting'. Start/end time, subject, location, attendees (from SharpSpring's participant list), and notes transfer directly. Meeting outcome and related person/company links are preserved. SharpSpring meeting recurrence patterns are simplified since Nutshell Activities do not support recurring meeting definitions — each occurrence becomes a standalone Activity record.

SharpSpring notes migrate as Nutshell Activity records with type='Note'. Note content, create date, last modified date, and related person/company are transferred. Rich text formatting in SharpSpring notes is simplified to plain text in Nutshell's note field. Embedded images or file attachments within SharpSpring notes are extracted and re-attached as separate file records in Nutshell to preserve the full context.

SharpSpring custom fields on People, Companies, Deals, and Leads require creation of corresponding Nutshell custom fields. Nutshell stores custom field definitions separately from record data — we create the field definition first (type-aware: text, number, date, picklist) then populate values during migration. Picklist fields require value-by-value mapping between SharpSpring options and Nutshell options.

SharpSpring visual workflow definitions do not migrate. Workflows are a core product capability with conditional branching that has no Nutshell equivalent. We export the SharpSpring workflow definitions as a structured JSON reference document your team can use to rebuild equivalent logic in Nutshell's sequence system or an external automation tool.

SharpSpring lead scores are numeric values calculated from engagement, page tracking, and time-decay rules. Nutshell has no native lead scoring field. We preserve the most recent SharpSpring score as a static custom number field on the Nutshell Person record, but the score will not update automatically — rebuilding dynamic scoring requires a third-party tool or manual process.

SharpSpring tags applied to People and Deals have no direct Nutshell equivalent. Tags are migrated as a multi-value custom text or picklist field on the respective Nutshell record. Nutshell's native tagging is limited to campaign membership, so custom fields hold the full tag list for reference.

SharpSpring campaigns migrate as Nutshell Campaigns with campaign name, type, status, and start/end dates. SharpSpring campaign membership (which contacts received which campaign emails) migrates as Nutshell Campaign recipients. SharpSpring's per-contact open/click engagement data is stored as a custom field on the Nutshell Campaign record since Nutshell Campaigns do not track engagement per contact.

SharpSpring VisitorID tracks anonymous website visitors by IP and associates them with contacts after form submission. Nutshell has no visitor tracking or anonymous web identification feature. VisitorID data cannot migrate to Nutshell and must be discontinued or managed via a separate website analytics tool after migration.