Migrate from Results to Odoo CRM

Results Contacts map to Odoo crm.lead records. In Odoo, a crm.lead can represent either a Lead (unqualified) or an Opportunity (qualified). We use a lifecycle or status property from Results to set the type field and stage_id on the Odoo lead. The original Results contact name, email, phone, and company fields map directly to name, email_from, phone, and partner_name on crm.lead. If Results stores a separate Company record, we create a res.partner (Contact/Company) in Odoo and link it via partner_id on the lead.

Results Companies map to Odoo res.partner records with partner_type = 'company'. The company domain from Results becomes the website field on res.partner. Odoo automatically creates individual Contact records under the Company partner when needed. Company-level addresses, industry classifications, and employee counts map to street/city/country, industry_id, and employee_nbr fields on res.partner.

Results Deals map to Odoo crm.lead records where type = 'opportunity'. The Results deal amount maps to planned_revenue, close date maps to date_deadline, and pipeline stage maps to stage_id within the configured sales team. If Results supports line items on deals, we migrate each line as an optional product_id link or store the amount as a plain currency value depending on Odoo configuration complexity.

Results pipelines map to Odoo sales teams (crm.team) and stage IDs within each team. We configure stage names and probabilities in Odoo Studio or via XML before migration so that the imported Deals land in the correct stage. If Results uses multiple pipelines with different stage sets, we create separate crm.team records in Odoo and assign the appropriate team_id to each imported opportunity.

Results activity records (calls, emails, meetings, notes) migrate to Odoo mail.message records linked to the parent crm.lead via res_id and model='crm.lead'. Activity type, timestamp, and body content map to message_type, date, and body on mail.message. Call duration and disposition store in custom fields on the message. Note attachments migrate as ir.attachment records linked via the relation field.

Results owners map to Odoo res.users by email match. We resolve each Results owner to a user_id on the crm.lead record during import. Any Results owner without a matching Odoo user goes to a reconciliation queue for your admin to provision before record import resumes.

Results custom properties on Contact, Company, or Deal migrate as custom fields on the corresponding Odoo model. We create the field definitions via Odoo Studio or direct XML before migration and map source values during import. Custom field types (text, date, integer, selection) must be matched to Odoo field types (char, text, date, integer, selection) during scoping.

Results attachments associated with Contacts, Companies, or Deals migrate as Odoo ir.attachment records. We map the original filename, mimetype, and binary content. Attachments link to the parent record via res_model='crm.lead' or 'res.partner' and res_id pointing to the migrated record ID.

We preserve the original create_date and write_date from Results on migrated Odoo records. Where Results tracks a first_contact_date or last_activity_date, we store these in custom fields on the crm.lead record for historical accuracy. This preserves pipeline tenure and recency metrics without relying on Odoo's native activity logging timestamps.

Results tags or labels on Contacts and Deals migrate to Odoo crm.tag records. We create the tag if it does not exist and link it via crm.lead.tag_ids (many2many relation). Multi-value tags from Results with comma-separated or multi-select storage map to multiple crm.tag records.

Results custom objects migrate to Odoo custom models defined in a custom module. We create the model definition (Python class inheriting from models.Model), add field definitions via _columns or _fields, and register the model in the module's __init__.py and __manifest__.py. Custom object data imports after the standard objects and after any lookup dependencies are resolved.

If Results stores quotes or proposals attached to Deals, we migrate these as Odoo sale.order records in draft state. The linked opportunity (Results Deal) maps to crm.lead via the opportunity_id field on sale.order. Line items from the quote map to sale.order.line. The customer admin decides whether to activate the Odoo sale module during migration configuration.