Migrate from Salesmate to Odoo CRM

Salesmate Contacts map to Odoo res.partner records with partner_type=contact. The Contact's primary Company in Salesmate becomes the parent_partner_id on the Contact partner record. Lifecycle stage from Salesmate migrates as a selection field on res.partner. Email, phone, address fields map directly; custom Contact fields map to Odoo custom res.partner fields. Parent-partner lookup resolution is computed before Contact insert to satisfy the foreign key constraint.

Salesmate Companies map to Odoo res.partner records with partner_type=company. A Company partner record serves as the parent for all Contact partner records linked to that company. Company-level custom fields migrate as custom fields on the company res.partner. The Odoo partner model supports multiple addresses per company via the res.partner.address field approach; each Salesmate Company address field set becomes a child res.partner contact with type=contact and the company as parent_id.

Salesmate Deals map to Odoo crm.lead records with type=opportunity. Deal stage maps to Odoo stage_id within the CRM pipeline. Deal value, expected close date, probability (if set in Salesmate), and owner assignment migrate as crm.lead fields. Salesmate deal custom fields map to custom fields on crm.lead. Pipeline association in Salesmate maps to Odoo team_id (sales team) and optionally to a separate CRM pipeline view if the customer has configured multiple Odoo pipelines.

Salesmate Tasks map to Odoo mail.activity records linked to the parent crm.lead (Opportunity) or res.partner (Contact/Company). Activity type, due date, assigned user (resolved via email match to Odoo res.users), status, and notes migrate. Closed tasks migrate with state=done and completed date preserved; open tasks migrate as pending activities. Salesmate's task associations to Deals map to Odoo's activity_res_model= crm.lead with activity_res_id set to the opportunity ID.

Salesmate email history maps to Odoo mail.message records linked to the relevant crm.lead or res.partner via model and res_id. Email body content, sender, recipient, and timestamp migrate. Odoo's mail.message is the base object for all threaded discussion on Odoo documents. Thread metadata from Salesmate's email module maps to mail.message fields. Note that full email body migration depends on Salesmate's API export path for message content; we coordinate this during the discovery phase.

Salesmate Team Inbox shared conversations are a non-standard schema that maps partially to Odoo mail.message records. The conversation threading model (which Salesmate organizes by inbox and thread ID) does not have a native Odoo equivalent because Odoo organizes messages by document (Partner, Opportunity, Project). We preserve thread metadata as custom fields on the linked mail.message records and generate a thread_id field to preserve conversation grouping in Odoo's Chatter. Team member attribution migrates via user email matching. Email message bodies migrate when accessible via the Salesmate API export path.

Salesmate Products map to Odoo product.template records with type=product (or service). Product name, description, list price, standard cost, and SKU migrate. Currency handling is resolved during scoping: if Salesmate stores prices in a single currency, we map directly to Odoo list_price; multi-currency requires pricelist configuration in Odoo before product import.

Salesmate Owners map to Odoo res.users records. We resolve owners by email match against the destination Odoo instance's res.users table. Any Salesmate owner without a matching Odoo user is held in a reconciliation queue for the customer's Odoo admin to provision before record import resumes. Owner assignment on Deals, Tasks, and other records depends on this lookup being satisfied.

Salesmate custom fields across Contacts, Companies, Deals, Tasks, and Products map to Odoo custom fields created via Odoo's Settings > Technical > Custom Fields interface. We create fields with matching field types (char, selection, integer, float, boolean, date, datetime) before any data import begins. Custom field API names in Salesmate's Customize > Create Form interface (internal_name) map to Odoo ir.model.fields names with appropriate x_ prefix.

Salesmate Tags on Contacts and Companies map to Odoo crm.tag records linked to crm.lead via crm.tag.rel (many2many). Tags stored as string arrays in Salesmate are split and matched against existing Odoo tags or created as new crm.tag records during import. Tags used for contact classification map to crm.tag on the associated Opportunity records post-conversion.

File attachments associated with Salesmate Contacts, Deals, and Companies map to Odoo ir.attachment records linked via res_model and res_id to the corresponding res.partner or crm.lead record. Attachment storage in Odoo uses the database or filestore depending on Odoo configuration. We flag files approaching Odoo attachment size limits and coordinate with the customer on storage provisioning.

Smart Flow automation definitions are not fully exposed via the Salesmate public API, so migration of automation logic as executable code is not possible. We export Smart Flow membership data (which contacts are enrolled in which campaigns, with enrollment dates) and preserve this as a custom field or related record on the contact in Odoo for audit. We deliver a written inventory of every active Smart Flow with its trigger type, conditions, action steps, and a recommended Odoo Automation or server action equivalent. The customer's Odoo admin rebuilds automations post-migration.