Migrate from Method CRM to Odoo CRM

Method CRM Contacts map to Odoo res.partner records with partner_type set to 'contact'. We preserve name, email, phone, address fields, and custom field values as individual properties on the partner record. Odoo's partner model uses a single table for both individuals and companies; the is_company flag determines whether a partner is a company or individual contact. We set this flag to False for Method Contacts, and set the parent_id to the mapped Company partner record to preserve the Method one-to-many Contact-to-Company association.

Method CRM Companies map to Odoo res.partner records with is_company set to True. Company name, website, address, and industry fields migrate directly. We import Companies first and establish parent_id on Contact records during the Contact import phase so that the parent relationship is satisfied at insert time. Any Company without a corresponding Contact in Method becomes a standalone company partner with no children.

Method CRM Opportunities map to Odoo crm.opportunity records. The pipeline stage name from Method maps to Odoo's stage_id on crm.opportunity, and we configure the Odoo CRM pipeline stages to match Method's stage names and sequence before migration. Expected revenue, close date, and probability migrate to planned_revenue, date_deadline, and probability respectively. Owner assignment maps via email resolution to Odoo res.users.

Method CRM pipeline stages (as enumerated values on Opportunities) map to Odoo crm.stage records within the relevant team pipeline. We configure each stage with a name matching Method's, set the sequence order to match the original pipeline order, and assign probability values from Method. Odoo requires pipeline and stage configuration before Opportunity records are imported.

Method CRM Activities map to Odoo's mail.activity model for scheduled and pending activities, and mail.message for logged historical activities. Activity type (call, meeting, task, note) maps to Odoo's activity_type_id. Description, date, and owner assignment migrate directly. Odoo's activity model requires a res_model and res_id pointing to the parent record (Contact or Opportunity), so we resolve parent references during the transform phase before writing to Odoo.

Method CRM Estimates map to Odoo sale.order records in draft/quotation state. Line items, product descriptions, quantities, and prices migrate to sale.order.line records. Status mapping preserves Method's estimate status as Odoo sale.order state (draft, sent, cancel). Note that Method Estimates are bound to the QuickBooks sync engine on the source; in Odoo, the equivalent is the native Sale app without external sync. We flag this as a functional change requiring user acknowledgment during scoping.

Method CRM Invoices map to Odoo account.move records with move_type = 'out_invoice'. Line items, tax codes, payment status, and outstanding balance migrate to the corresponding account.move.line records. Payment records in Method (payments received against an invoice) map to account.payment records linked to the invoice. Since Odoo's accounting module manages the full accounts receivable lifecycle, this object requires Odoo's accounting app to be active in the destination database.

Method CRM Sales Orders map to Odoo sale.order records confirmed into a sale state (sale_order.confirmed = True). The confirmed Sales Order creates a related picking in Odoo's stock module if inventory management is active. We map status and line items and flag any Method Sales Order with a QuickBooks entity reference for customer acknowledgment that the QB linkage does not transfer to Odoo.

Method CRM custom fields on Contacts, Companies, and Opportunities require pre-creation in Odoo before migration. For standard Odoo fields we use the crm_custom_fields module from the Odoo App Store (available for Odoo versions 11-16) which allows custom field creation through the UI without a developer addon. For more complex custom field types or multi-object custom fields, we create a custom Odoo addon inheriting from the standard model, deploy it to the destination database, and then import the mapped values. We inventory every Method custom field during discovery, map its data type to an equivalent Odoo field type (char, selection, float, boolean, date), and deploy the schema before data import begins.

Method CRM Users and Owners map to Odoo res.users records. We resolve by email match against the destination Odoo instance's user table. Owners without a matching Odoo user go to a reconciliation queue for the customer's admin to provision. Role and permission sets differ between platforms; we map Method role assignments to Odoo access rights groups where applicable, but permission parity is not guaranteed without post-migration admin review.

Method CRM tags on Contacts and Companies map to Odoo crm.tag records. Tags are stored as tag name strings in Method; we create the tag in Odoo and link via crm.lead.tagrel for Opportunities or via a custom partner_tag_ids many2many field on res.partner if the customer requires tag visibility on Contacts and Companies. The customer chooses tag strategy during scoping based on their segmentation use case.

Method CRM Customer Cases are Enterprise-tier-only objects. If the destination Odoo instance has the helpdesk app installed, Cases map to helpdesk.ticket records with priority, description, and related partner. If the helpdesk app is not active in the Odoo database, we flag Cases as out-of-scope and note that the customer should install the helpdesk app or use crm.opportunity with a support-type tag as a lightweight alternative. Cases require the customer's current Method plan to be CRM Enterprise for the API to expose them.