Migrate from Sales Mantra to Odoo CRM

Sales Mantra Lead records map to Odoo crm.lead with type=lead. We extract contact name, email, phone, source attribution, status fields, and owner assignment from the CSV. The Odoo crm.lead model handles the lead entity natively; no split is required as there is no separate Contact object in Sales Mantra to reconcile against. Owner assignment resolves by email match against the Odoo res.users table.

Sales Mantra Account records map to Odoo res.partner with customer_rank set to distinguish companies (customer_rank > 0) from individual contacts. We preserve the account name, address fields, industry classification, and any custom fields exported. res.partner is created before crm.lead import to satisfy the partner_id lookup on lead records.

Sales Mantra Deal records map to Odoo crm.lead with type=opportunity. Deal name becomes the opportunity name; deal value maps to Odoo's Expected Revenue field; expected close date maps to date_deadline; pipeline stage from Sales Mantra maps to the Odoo stage_id with probability values configured per stage. The associated Sales Mantra Account ID resolves to an Odoo res.partner record at migration time.

Each Sales Mantra pipeline stage becomes an Odoo crm.stage record within the corresponding Odoo team pipeline. We map Sales Mantra stage names to Odoo stage names and configure probability percentages that match the source stage close rates. The Odoo stage ID is referenced on each crm.lead record during opportunity import.

If Sales Mantra uses multiple deal pipelines, each maps to a separate Odoo crm.team with its own pipeline Kanban view. Odoo crm.team corresponds to a Sales team; pipeline configuration is per-team. We verify the pipeline count during the data audit and configure the appropriate number of crm.team records in the destination Odoo instance before deal import.

Sales Mantra Activity records (calls, emails, tasks, notes) linked to Leads, Accounts, or Deals migrate to Odoo mail.activity entries and mail.message records. Activity type maps to Odoo's activity_type_id; description and timestamp preserve; owner resolves by email match to Odoo res.users. Not all Sales Mantra activity types may be present in the standard export; we verify completeness during the data audit phase.

Sales Mantra contact classification values stored as custom fields or delimited CSV columns migrate to Odoo crm.tag records. We normalize the classification data during the transform phase: multi-value delimited columns are split into individual tag records and linked via crm.tag.rel on the crm.lead. Tags are visible on the Odoo lead form and filterable in the pipeline Kanban view. The customer chooses during scoping whether to use tags or custom selection fields for the classification data.

Sales Mantra Owner records referenced on Deals and Activities map to Odoo res.users. We extract the owner roster from the CSV (typically a small list given Sales Mantra's 8-employee vendor size) and match by email address to Odoo users. Owners without a matching Odoo user are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Sales Mantra document attachments linked to Accounts or Deals migrate as Odoo ir.attachment records. We attempt to extract document URLs from the Sales Mantra export and resolve them as attachment links on the corresponding Odoo res.partner (for Account documents) or crm.lead (for Deal documents). If Sales Mantra stores documents as internal platform references rather than public URLs, we flag these for manual retrieval before migration cutoff. Binary file migration is attempted where accessible; file references are preserved as notes if binary extraction is not possible.

Any custom fields exported on Sales Mantra Account records that are not part of the standard schema migrate to Odoo custom fields created via Odoo Studio. We create fields of the appropriate type (char, selection, integer, date, etc.) on res.partner before the account import phase. Fields that are no longer relevant or contain stale data are flagged for the customer's review before inclusion.

Sales Mantra Deal custom fields migrate to Odoo crm.lead custom fields created via Odoo Studio. Any field that stores deal-specific metrics (advertising spend tracking, win/loss notes, custom deal flags) is preserved as a custom field on the opportunity record. We verify the field type mapping during the data audit and handle type conversion (e.g., delimited multi-value to selection field) where the Sales Mantra export uses non-standard formats.

The Sales Mantra data export may or may not include a separate product catalog. If product records exist in the Sales Mantra instance, they migrate to Odoo product.product with product.template. We verify product data availability during the data audit phase and include product migration only if the export contains a Products object. Line items on Deals migrate to Odoo sale.order.line records linked to the parent crm.lead opportunity if the Sales Mantra instance tracks product associations on deal records.