Migrate from m-savvy to Odoo CRM

M-savvy Contact records map to Odoo CRM Partner records. When a m-savvy Contact has a linked Account (Company), we create a parent Partner with is_company=True and a child Partner record with is_company=False for the individual contact. If m-savvy Contact has no Account link, it becomes a Partner with is_company=False. The original m-savvy lifecycle stage, phone, email, address, and owner fields migrate to the corresponding Odoo Partner fields. Custom contact properties discovered during API scoping migrate as custom fields on res.partner.

M-savvy Account records map to Odoo Partner records with is_company=True. Industry, size, billing address, and domain fields from the Account map to Odoo Partner fields including industry_id, website, and address fields. Account is created before Contact import so that the parent relationship is resolved at Contact insert time. If a m-savvy Contact has no linked Account, we create a standalone individual Partner.

M-savvy Deal records map to Odoo CRM Opportunity records. Deal stage, amount, close date, probability, and custom fields migrate directly. The m-savvy pipeline assignment maps to an Odoo CRM Team and pipeline, and Deal stage names are remapped to the destination pipeline stage sequence. Closed-won and closed-lost reasons from m-savvy custom fields migrate as Odoo Lost Reason or custom fields on crm.lead.

M-savvy pipeline definitions and stage names are read from the live API during discovery. Each m-savvy pipeline becomes an Odoo CRM Pipeline (crm.team or crm.pipeline), and stage names are mapped to Odoo stage records within that pipeline. We flag any stage name or count mismatch and propose a stage mapping table for customer approval before migration.

M-savvy Lead records map directly to Odoo CRM Lead records. Lead status, lead source, and any scoring fields migrate as Odoo Lead fields. The m-savvy owner (sales rep) resolves to an Odoo User by email match. If a m-savvy Lead is already qualified and should be treated as a Contact or Opportunity in Odoo, the customer defines the rule during scoping and we apply it at migration time.

M-savvy Activity records are discriminated by type during extraction and mapped to the corresponding Odoo object: email-type activities map to Odoo Mail Message records linked to the Partner or Opportunity; task-type activities map to Odoo Project Task or CRM Activity records; meeting-type activities map to Odoo Calendar.Event records with attendee links to the Partner. We preserve the original timestamp and body content. Archived or deleted activities are excluded.

M-savvy custom objects are not documented in a public schema reference. We inspect the live org via API during the discovery phase to enumerate custom object types, field definitions, and relationships. Each discovered custom object becomes a custom Odoo model with matching field names and types, including many2one lookups to standard objects (Partner, Opportunity) and many2many relationships. The schema map is shared with the customer for confirmation before any data moves.

Attachment files in m-savvy are stored separately from record data and require a dedicated file-export pass using m-savvy's file storage API endpoints. We download files to our staging environment, then upload to Odoo via the ir.attachment model, setting res_model to the destination object (res.partner, crm.lead, etc.) and res_id to the migrated record ID. Any file whose parent record failed to migrate is flagged and held for manual review.

M-savvy Owner records map to Odoo User records by email address match. We extract every distinct owner referenced on Contact, Account, Deal, and Activity records and match against the destination Odoo User list. Any m-savvy owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

M-savvy pipeline and stage assignments on Deal records map to Odoo CRM Teams. Each distinct pipeline in m-savvy becomes a CRM Team in Odoo, and Deals are assigned to the corresponding team member's pipeline view. The customer configures team membership in Odoo before migration begins.

M-savvy Notes attached to Contact, Account, or Deal records migrate as Odoo Mail Message records on the related Partner or Opportunity. Rich text formatting is preserved. Note attachments (files within a note) migrate as ir.attachment records linked to the same parent object.

M-savvy tag values on Contact, Account, or Deal records migrate to Odoo CRM tags (ir.model.data for crm.lead.tag). Tags used for classification purposes become tag records in Odoo and are linked via the many2many relationship on the Lead and Opportunity models.