Migrate from SalesCaptain to Microsoft Dynamics 365 Sales

SalesCaptain Contacts with a lead or prospect status map to Microsoft Dynamics 365 Lead. SalesCaptain Contacts with a customer or active status map to Dynamics 365 Contact tied to a corresponding Account. We compute the split at migration time by reading the SalesCaptain contact status field and assigning the record to the correct Dynamics object with the original status preserved in a custom field sc_original_status__c on both Lead and Contact for reconciliation and reporting.

SalesCaptain Company records map directly to Microsoft Dynamics 365 Account. The Company domain name or website field becomes the Account Website field and serves as a dedupe key during import. Dynamics 365 Account hierarchy support allows us to model parent-child Company relationships if the source data contains multiple locations under a parent entity. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert.

SalesCaptain Deals map to Dynamics 365 Opportunity. The deal stage maps to a configured Dynamics Opportunity Stage. We pre-create the Sales Process and Record Type in the target environment that corresponds to each SalesCaptain deal pipeline before migration begins. Closed-won and closed-lost reasons from SalesCaptain custom properties migrate to Dynamics Loss Reason and Win Reason fields if those fields are present in the destination schema.

Each SalesCaptain deal stage becomes a Dynamics 365 StageName value within the configured Sales Process. We map stage probability percentages from SalesCaptain to the Dynamics StageProbability field, rounding to the nearest integer allowed by the platform. Stage ordering and pipeline assignment migrate as part of the Sales Process design step.

SalesCaptain conversation threads (SMS, voice call logs, and message exchanges) export as activity records with timestamps and participant references. We map these to Dynamics 365 Task records with the TaskSubtype field set to Call for voice threads and TaskSubtype set to Task for message threads. Conversation body content migrates as the Task Description. The resolved Contact or Lead serves as the WhoId and the Account as the WhatId for timeline integrity.

SalesCaptain custom field definitions export as JSON schemas with field type metadata. We map these to equivalent Dynamics 365 column types during schema design: text fields to Text, numeric fields to Number or Decimal, date fields to DateTime with timezone normalization, and multi-select values to Option Set with the delimiter-preserving transformation applied. Custom fields are created in the destination environment before any data import begins.

SalesCaptain channel profile data (phone numbers, messaging account identifiers) exports as metadata attached to Contact records. We map phone numbers to the Dynamics Contact phone and mobilephone fields, and messaging identifiers to a custom text field sc_channel_id__c on Contact. Channel-specific routing rules that cannot translate to Dynamics native fields are flagged in the migration report for admin review.

SalesCaptain user records export with name, email, and role assignment data. We resolve owners by email match against the Dynamics 365 User table. Users without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before record import resumes. Role-based assignments from SalesCaptain are documented in the Workflow Inventory worksheet and must be reconfigured in Dynamics 365 security roles post-migration.