Migrate from SalesCaptain to Twenty CRM

SalesCaptain Contact records map directly to Twenty Person objects. The primary email, phone, name, and address fields map 1:1. We preserve the SalesCaptain contact's original created date and last_modified timestamp on the Twenty record for audit. Any SalesCaptain custom properties on a Contact map to Twenty custom fields on Person, which we pre-create via the /metadata API before migration begins.

SalesCaptain Company records map 1:1 to Twenty Company objects. Domain name, address, industry, and employee count migrate directly. Company is imported before Person so that the Company-Person relationship is satisfied at Person insert time. We use the SalesCaptain company domain as the dedupe key if duplicate companies exist in the source.

SalesCaptain Lead records map to Twenty Lead objects. Lead status, source, and score properties from SalesCaptain migrate as custom fields on the Twenty Lead since Twenty's native Lead model includes standard status and source fields. If the customer has qualified Leads in SalesCaptain that should become People-Company relationships in Twenty, we flag this during scoping and offer a Lead-to-Person convert step post-migration.

SalesCaptain Deal records map to Twenty Opportunity objects. Deal name, amount, stage, expected close date, and owner migrate directly. The SalesCaptain deal pipeline maps to a Twenty pipeline that we configure before migration. Closed-won and closed-lost reasons from SalesCaptain custom properties become Twenty custom fields for loss and win analysis.

SalesCaptain conversation threads export as activity records with timestamps, participants (contacts or leads), direction (inbound or outbound), and message content. We map these to Twenty Activity records (calls, emails, tasks) with the body preserved as the activity note. Participant resolution uses email matching against the migrated Person and Lead records. This is the highest-risk mapping because SalesCaptain conversation threading does not map to a standard Twenty object type without enrichment.

SalesCaptain custom field definitions export as JSON schemas alongside standard field values. We rehydrate custom fields in Twenty by calling the /metadata API to pre-create each field with the correct type (text, number, date, picklist, multi-select). Date-only fields from SalesCaptain that may import as datetime receive explicit type coercion during the transform phase. Multi-select picklist values are delimiter-normalized to match Twenty's format before insert.

SalesCaptain channel profile data (phone numbers used for calling, messaging account identifiers) exports as metadata on the Contact. We map these to custom fields on the Twenty Person record (e.g., sms_phone__c, calling_number__c) rather than a native channel object since Twenty does not have a separate Communication Channel Profile concept. Channel-specific routing rules are flagged as configuration items for the customer's admin to review post-migration.

SalesCaptain user records export with name, email, role, and assignment data. We match SalesCaptain users to Twenty WorkspaceMember records by email address. Any SalesCaptain user without a matching Twenty workspace member goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated Deals and Leads is resolved at migration time using the User mapping.

SalesCaptain workflow automation rules are not exposed via API and do not migrate. We deliver a Workflow Inventory worksheet during scoping that documents every active rule's trigger conditions, filter logic, and actions so the customer's admin can recreate them in Twenty's settings-based automation. This inventory is a required deliverable before cutover because losing automation rules without a documented replacement causes immediate process disruption.

SalesCaptain deal pipelines map to Twenty Pipeline configurations. Each SalesCaptain pipeline becomes a Twenty Pipeline with stage values migrated as stage entries. Stage probability percentages migrate from SalesCaptain to Twenty stage probability fields, rounded to the nearest integer. We configure the pipeline in Twenty's settings before Deal migration begins.