Migrate from SalesCaptain to Salesforce Sales Cloud

SalesCaptain Contact records map 1:1 to Salesforce Contact. Email, phone, name, address, and custom property fields transfer directly. We validate email format against Salesforce's email field constraints and apply type coercion for any date or numeric custom fields that may have imported incorrectly from SalesCaptain. Contacts are created after Accounts so that the AccountId lookup is satisfied at insert time.

SalesCaptain Company records map directly to Salesforce Account. Company name becomes Account Name; domain becomes Website. Account is created as the parent record before any Contact import to satisfy the AccountId foreign key. For multi-location accounts, we flag any child-location Company records and discuss Account hierarchy flattening with the customer's admin.

SalesCaptain distinguishes Leads from Contacts at the source. We preserve lead status, lead source, and any scoring properties as custom fields on the migrated Salesforce Lead record. If the customer prefers to merge qualified Leads into Contacts at migration time, we apply that rule as a transformation step during the data extract phase.

SalesCaptain conversation threads (SMS, voice call logs, message threads) export as timestamped activity records. We split these into Salesforce Task records for call logs and Salesforce EmailMessage records for message content, each linked to the parent Contact or Lead via WhoId and to the related Account via WhatId. Conversation metadata (channel type, disposition, recording URL if present) migrates as custom Task or EmailMessage fields.

SalesCaptain custom field definitions export as JSON schemas. We pre-create all destination Salesforce custom fields before migration begins, mapping SalesCaptain data types to Salesforce field types. Date-only fields that may import as datetime from SalesCaptain are coerced. Multi-select picklist values are normalized by delimiter. Custom fields are deployed into the Salesforce Sandbox org first for validation before production migration.

SalesCaptain channel profile data (phone numbers, SMS accounts, messaging credentials) exports as metadata. We map these to Contact-level custom fields (e.g., mobile_phone__c, sms_opt_in__c) rather than as separate objects. Any routing rules tied to channel profiles do not migrate and are flagged in the handoff documentation for the customer's admin to reconfigure in Salesforce.

SalesCaptain user records export with role, team assignment, and ownership data. We resolve owners by email match against the Salesforce destination org's User table. Any SalesCaptain user without a matching Salesforce User goes to a reconciliation queue. The customer's Salesforce admin provisions missing users before record import resumes because OwnerId references are required on most standard objects.

SalesCaptain Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name; deal stage maps to Salesforce StageName via a stage-mapping table defined during scoping. Amount, close date, and owner migrate directly. We resolve the AccountId at migration time by matching the associated SalesCaptain Company to the destination Salesforce Account.

SalesCaptain pipeline stages map to Salesforce Opportunity Stage values. We configure the Salesforce Sales Process to whitelist only the stages that exist in the SalesCaptain pipeline. Stage probability percentages are mapped to StageProbability on each stage entry. If SalesCaptain has custom stage reason fields (Closed-Lost reason, Closed-Won reason), we create equivalent custom fields on Opportunity.

SalesCaptain Automation Flows are not accessible via API and cannot be exported programmatically. During discovery we capture a written inventory of every active automation flow including its trigger, conditions, actions, and delays. This inventory is delivered as a Workflow Inventory worksheet for the customer's Salesforce admin to rebuild in Flow post-migration. The inventory includes the recommended Flow type (record-triggered, scheduled, or screen) and any required Salesforce add-ons.

SalesCaptain's AI voice agent routing logic and agent configurations are platform-specific and not exportable via API. We document the active voice agent flows (call routing rules, prompt templates, disposition mappings) during discovery and deliver them as part of the Workflow Inventory. Salesforce Einstein AI or Voice Service requires separate configuration post-migration.

If SalesCaptain review request automation has generated review submission data, we map these to Salesforce custom fields on Account (for aggregated ratings) or to a custom Review object with a lookup to Account. Review metadata (submission date, rating, source channel) is preserved as structured custom fields.