Migrate from SalezShark to Nutshell

SalezShark Lead records with auto-assignment rules and conversion scoring map directly to Nutshell Lead. The Lead's assigned owner resolves to a Nutshell User by email match. Conversion scoring from SalezShark transfers as a numeric custom field on the Nutshell Lead. If the Lead has been converted in SalezShark before migration, the converted Contact and Account map separately under People and Companies, and the original Lead record is flagged as converted.

SalezShark Contact records map to Nutshell People, the primary person record with name, email, phone, and address fields. Standard field names are consistent enough for direct mapping. Email address becomes the primary dedupe key during Nutshell import. Any enrichment data attached to the SalezShark Contact (headcount, revenue range) is flagged as candidate enrichment data that should be re-enriched via a third-party tool post-migration.

SalezShark Account records map to Nutshell Companies. The company name serves as the primary dedupe key during import. Any linked Contacts from SalezShark resolve their Company reference after the Companies batch completes. Multi-currency field values from SalezShark Professional tier map to Nutshell's currency fields, with currency code preserved on the record.

SalezShark Opportunity records map to Nutshell Deal. Pipeline stage from SalezShark maps to a corresponding Nutshell pipeline stage using the stage name and probability as the matching key. Deal value, close date, owner, and associated Account/Company are preserved. Nutshell's Deal model supports a single pipeline at Foundation tier; multiple SalezShark pipelines require the customer to choose a primary pipeline for import or Enterprise tier for multi-pipeline support.

SalezShark's pipeline configuration (stage names, stage order, probabilities) is exported as a settings snapshot during scoping. We re-map stage names to Nutshell pipeline stages, preserving probability percentages where Nutshell allows them. If the customer used multiple SalezShark pipelines for separate lines of business, we document each pipeline's stage structure and recommend how to consolidate or keep separate in Nutshell, subject to the Enterprise tier multi-pipeline feature.

SalezShark Task and Activity records map to Nutshell Activities with status, due date, type (call, email, meeting, note, task), owner, and association to the linked Contact/Lead, Account/Company, or Opportunity/Deal preserved. Activity timestamps migrate to maintain timeline ordering. Activities with no linked record are associated at the account or contact level based on the original relationship.

Custom Fields on Contacts, Accounts, Leads, and Opportunities are extracted from SalezShark settings as a schema definition step before any record import. We create matching custom fields in Nutshell (People, Company, Lead, Deal tabs) with equivalent field types. Field types that differ — for example, SalezShark picklists that Nutshell represents differently — are transformed during the data load. Any custom fields that exist only in SalezShark are flagged as candidate fields to create in Nutshell before the relevant record batch imports.

Document Management files attached to SalezShark records export as file metadata with the parent record reference. We re-associate files to the corresponding Nutshell People, Company, Lead, or Deal using the original attachment name and parent record as the matching key. File content migrates as attachments; URLs pointing to external document storage do not migrate and are flagged in the handoff documentation.

SalezShark User records map to Nutshell User for owner and assignee resolution. We resolve by email match against the Nutshell destination account's user list. Any SalezShark Owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes, avoiding orphaned records.

SalezShark Workflow Automations (Professional tier only) are exported as written specifications describing trigger conditions, filter logic, and downstream actions. We do not migrate them as executable automation rules because Nutshell's workflow engine is a separate implementation. The specification document includes trigger type, criteria fields, action sequence, and a recommended Nutshell equivalent so the customer's admin can rebuild them. Custom Event Triggers receive the same treatment as a separate configuration document.