Migrate from SalesCaptain to Odoo CRM

SalesCaptain Contact records map to Odoo res.partner with type = 'contact'. Each Contact linked to a SalesCaptain Company becomes a res.partner with parent_id pointing to the corresponding company-type partner. We resolve parent_id at migration time by matching the Contact's company reference to the SalesCaptain Company records migrated in the preceding phase. The original SalesCaptain contact status and any lead-score property migrate as custom fields on the partner record so the customer retains behavioral data in Odoo.

SalesCaptain Company records map to Odoo res.partner with partner_type set to 'company'. The company flag is set to true on the partner so Odoo treats it as an organization rather than an individual contact. Address fields from SalesCaptain (street, city, state, postal_code, country) map to the corresponding Odoo partner address fields. If the SalesCaptain Company has no associated Contact records, it migrates as a standalone organization partner. If multiple SalesCaptain contacts reference the same Company, they become multiple child partner records under a single company-type parent.

SalesCaptain Lead records map to Odoo crm.lead with type = 'lead'. We preserve the SalesCaptain lead status and lead source as custom fields on the Odoo lead record since Odoo uses stage and priority to drive the pipeline rather than a separate status property. The original lead creation date migrates as create_date on the crm.lead. Any lead score value from SalesCaptain maps to a custom float field on the lead for reporting purposes. If the customer used SalesCaptain's distinction between Lead and Contact to represent qualification level, we document the mapping rule during discovery.

SalesCaptain Deal records map to Odoo crm.lead with type = 'opportunity'. The deal name becomes the crm.lead name field, deal amount becomes planned_revenue, and expected close date maps to date_deadline. We resolve partner_id by matching the Deal's associated Company to the migrated res.partner record. SalesCaptain deal stage maps to Odoo stage_id, which we configure during schema design as a pipeline with stages corresponding to the customer's existing deal lifecycle. The original deal creation date migrates as create_date on the opportunity.

SalesCaptain conversation records of type 'call' map to Odoo crm.phonecall. We extract call duration, disposition, and timestamp from the SalesCaptain conversation payload and write them to the corresponding crm.phonecall fields. The phonecall record is linked to the resolved partner (WhoID) and the associated opportunity (WhatID) if the conversation was related to an active deal. Call recordings stored as file URLs in SalesCaptain are preserved as notes or attachments on the crm.phonecall record since Odoo's standard phonecall model does not natively store a recording URL field.

SalesCaptain email and SMS conversation threads map to Odoo mail.message records. Each message in a thread becomes a separate mail.message with mail_message_subtype = 'comment', linked to the partner via model = 'res.partner' and res_id pointing to the migrated partner ID. Message body and timestamp migrate directly. We preserve the full conversation thread ordering by setting message_date to the original SalesCaptain timestamp. If the customer used conversation tags or labels, those migrate as mail.message tags where the Odoo instance has the mail.activity.mixin tags extension enabled.

SalesCaptain custom field schemas require pre-creation in Odoo before any data is loaded. We extract the custom field definitions from SalesCaptain during discovery, map SalesCaptain field types to Odoo field types (Char, Integer, Float, Selection, Many2one, Text), and deploy them as ir.model.fields XML records into the Odoo database before migration begins. This is a prerequisite phase that must complete successfully before any record import starts. Field labels, help text, and mandatory flags are carried over from SalesCaptain's field configuration.

SalesCaptain channel profile data (phone numbers, SMS accounts, messaging endpoint URLs) has no native equivalent in Odoo CRM as a first-class object. We extract channel profile data during extraction and store it as custom fields on the res.partner record, naming them channel_phone, channel_sms, and channel_messaging_url to preserve the customer's ability to identify which communication endpoints belong to each contact. Any routing rules attached to channel profiles do not migrate; we document them in the Workflow Inventory for the customer's admin to reconfigure in Odoo.

SalesCaptain owner records map to Odoo res.users by email match. We extract all distinct owner IDs referenced on Contacts, Companies, Deals, and Conversations during extraction and attempt to resolve each to an existing Odoo User. Owners without a matching Odoo User enter a reconciliation queue where the customer's Odoo admin provisions the missing User before record import resumes. Active versus inactive status on the Odoo User is set based on whether the original SalesCaptain user is active in the source platform.

If the customer used SalesCaptain Products or line items associated with Deals, those migrate to Odoo product.product records. Product name, SKU (if populated), and list price map to name, default_code, and lst_price respectively. We create the product.template record and link the product.product variant at migration time. If SalesCaptain Deals do not have associated product records, this mapping step is skipped.

SalesCaptain workflow automation rules do not export via API and cannot be migrated programmatically. We document all active workflow rules during discovery using a Workflow Inventory worksheet that captures the trigger condition, filter logic, and actions for each rule. This inventory is delivered to the customer at the end of migration so their Odoo admin or implementation partner can rebuild the automations in Odoo Studio or using server actions. Workflows are a common source of post-migration friction when teams expect them to function on day one; the inventory prevents this gap from being a surprise.

SalesCaptain task engagements (manual to-dos, reminders, follow-up items) map to Odoo mail.activity records linked to the res.partner or crm.lead. Task title, due date, and completion status map to activity_summary, date_deadline, and automated activity_type completion respectively. Owner assignment migrates by resolving the SalesCaptain owner to the Odoo res.users record via the User mapping step. Open tasks migrate with their original creation timestamp preserved for activity date ordering.