Migrate from SalesCaptain to Nutshell

SalesCaptain Contact records map directly to Nutshell People. Standard fields (name, email, phone, address) map 1:1. The SalesCaptain lead status property maps to a Nutshell custom field or the built-in Person status field if configured during schema setup. We preserve all custom property values as Nutshell custom fields on People, applying delimiter normalization for multi-select picklists where SalesCaptain stores comma-separated values.

SalesCaptain Company records map to Nutshell Company without transformation. The domain field from SalesCaptain becomes the Company website. Company records are migrated before People so that any People with a Company association resolve their Company lookup at insert time. Duplicate Company records (same domain) are merged during transformation.

SalesCaptain Lead records are distinct from Contacts in SalesCaptain's data model. We migrate Leads as Nutshell People with a lead status field set to match the original SalesCaptain lead source and stage. If the customer used both Lead and Contact objects, we map both to People and flag any records with overlapping email addresses for deduplication before final import.

SalesCaptain Deals map to Nutshell Deals with pipeline, stage, close date, and monetary value preserved. The pipeline assignment in SalesCaptain becomes the Nutshell Deal pipeline, and the deal stage maps to a corresponding Nutshell stage within that pipeline. Loss reason and win reason custom properties migrate to Nutshell custom fields on Deal.

SalesCaptain Conversations are message threads tied to a Contact or Lead. We split each conversation thread into individual activity records in Nutshell: the initial message and each reply become a Note linked to the People record. Thread metadata (participants, direction, channel type) are stored in custom fields on the Note. This preserves conversation context without attempting to recreate the threaded view in Nutshell's flat activity timeline.

SalesCaptain custom field definitions export as JSON schemas alongside field values. We create corresponding custom fields in Nutshell for People, Companies, and Deals before data import. Type coercion is applied: SalesCaptain date-only fields that export as datetime strings are normalized to date format, and multi-select picklist delimiters are standardized to semicolon-separated values per Nutshell's import format requirements.

SalesCaptain Communication Channel Profiles (phone numbers, messaging accounts) export as metadata tied to Contacts. Nutshell does not have a native Communication Channel object, so we map channel data to custom fields on the People record: a phone type picklist, an SMS number field, and a messaging platform identifier. Channel-specific routing rules that cannot be represented as field data are flagged in the documentation deliverable for manual reconfiguration.

SalesCaptain user records (owner, assignee) are resolved by email match against the Nutshell destination account's team members. We extract all owner_id references from Contacts, Companies, and Deals and create a user mapping table. Any SalesCaptain user without a matching Nutshell team member is placed in a reconciliation queue for the customer's admin to provision before the migration continues.

SalesCaptain Workflow automation rules are not accessible via API and cannot be exported programmatically. We document all active workflow rules during the discovery phase using the customer's configured workflow screenshots and configuration notes, capturing trigger conditions, filter logic, and action sequences. The Workflow Inventory worksheet is delivered to the customer as a rebuild guide for Nutshell's automation builder. This is the standard FlitStack AI scope for non-exportable automation.