Migrate from Enrich-CRM to Odoo CRM

Enrich-CRM's enriched company records map to Odoo Partner with is_company=True. Firmographic fields (industry, employee count, revenue, tech stack, SIRENE data) migrate to Odoo partner standard fields or custom Char/Integer fields created during schema setup. The original HubSpot company ID and Enrich-CRM enrichment timestamp migrate as custom fields (x_hs_company_id__c, x_enrichment_date__c) to preserve audit trail. Odoo Partner Name maps from the Enrich-CRM company name field; if Enrich-CRM stores a domain, it maps to Partner website.

Enrich-CRM's enriched contact records map to Odoo Partner with is_company=False and a parent_id pointing to the company Partner record created in the company mapping phase. Personal fields (name, email, phone, title, seniority, LinkedIn URL, location) map to Odoo standard partner fields (function, email, phone, website). Any Enrich-CRM-specific properties (seniority tier, enrichment confidence score) migrate as custom Char fields on the Partner. The HubSpot contact ID migrates as a custom field (x_hs_contact_id__c) for source tracking.

Enrich-CRM job change alerts are not standard CRM records; they are enrichment signals attached to contacts. We capture each alert as a mail.message note attached to the relevant contact Partner record. The message body contains the old company, new company, old title, new title, and detection date sourced from the Enrich-CRM alert payload. A custom Partner field (x_job_change_date__c) stores the date so the customer's team can build Odoo Studio automations to act on recent job changes. This signal does not trigger Odoo native automations without manual rebuild in Odoo Studio.

Enrich-CRM custom lead scoring models and contact segments are not exportable via API. We document the scoring criteria (score thresholds, property conditions, segment names) during scoping from screen captures and customer interviews, then design an equivalent scoring model in Odoo using crm.tag records for segment labels and a custom integer field (x_enrichment_score__c) for numerical scores. The rebuild is a configuration task performed by the customer's Odoo admin after migration and is scoped separately from the data migration engagement.

HubSpot Company records (the base records Enrich-CRM enriches) map to Odoo Partner with is_company=True. This is the parent record for enriched contacts. The HubSpot company domain maps to the Odoo Partner website field as a dedupe key. If the customer runs multiple pipelines in HubSpot, Odoo's crm.team (sales team) and stage configuration handles pipeline scoping without needing a separate Deal object for pipeline isolation.

HubSpot Contact records map to Odoo Partner with is_company=False. The parent_id references the Partner record created from the corresponding HubSpot Company. Lifecycle Stage from HubSpot migrates as a custom Char field (x_hs_lifecycle_stage__c) on the Partner for audit and reporting. Any Enrich-CRM enrichment properties appended to the HubSpot Contact (seniority, job_change_detected, confidence_score) migrate as additional custom fields to the same Partner record.

HubSpot Deal records map to Odoo crm.lead with type='opportunity'. The HubSpot dealstage property maps to an Odoo crm.stage value within the designated crm.team pipeline. Deal amount and currency migrate to Odoo's expected_revenue and currency_id fields. Odoo does not have a standalone Deal object separate from crm.lead; pipeline isolation is handled via crm.team and stage assignment rather than a separate deal entity.

HubSpot deal pipelines map to Odoo crm.team records (one per pipeline) with corresponding stage sequences (crm.stage records within each team). Each HubSpot pipeline name becomes the crm.team name. HubSpot deal stages map to crm.stage stage_name values with probability percentages preserved from HubSpot. This configuration is deployed into the Odoo Sandbox before any data import begins.

HubSpot Owners are resolved by email match against Odoo res.users. Any HubSpot Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision the corresponding Odoo user before record import resumes. Active/inactive status on the Odoo User matches the active/inactive status of the original HubSpot owner to preserve team assignment and quota alignment.

HubSpot call engagements map to Odoo crm.phonecall if the crm_phone module is installed in the target Odoo instance; otherwise they map to calendar.event. The mapping preserves call direction, duration (call_duration in seconds), disposition, and the original HubSpot timestamp. The activity links to the migrated Partner record via the partner_id field on crm.phonecall or the related Partner on calendar.event.

HubSpot email engagements (body content, subject, direction) map to Odoo mail.message records attached to the relevant Partner or crm.lead. Email direction (INBOUND/OUTBOUND) migrates as a custom Char field since Odoo mail.message does not have a native direction field. The original HubSpot engagement timestamp maps to mail.message.date for timeline ordering. Attachments migrate as ir.attachment records linked via mail.message.attachment_ids.

HubSpot meeting engagements map to Odoo calendar.event with start_datetime, stop_datetime, and location preserved. Attendee resolution maps the HubSpot contact and company IDs to the migrated Odoo Partner records. If the Odoo instance uses calendar.visibility='portal', meeting records are visible to portal contacts. Meeting notes from the HubSpot engagement body migrate as mail.message content attached to the calendar.event.

HubSpot engagement notes (engagement type NOTE) map to Odoo mail.message records attached to the relevant Partner or crm.lead. The note body migrates as plain text in mail.message.body. Author resolution matches the HubSpot hubspot_owner_id to the migrated Odoo res.users record by email and sets mail.message.author_id accordingly. Rich text formatting from HubSpot notes is simplified to plain text since Odoo mail.message body rendering differs from HubSpot's.

HubSpot task engagements map to Odoo project.task records. Task status, priority, and due date migrate to project.task status, priority, and date_deadline respectively. The task subject maps to project.task name. If the customer does not use Odoo Project, tasks can alternatively map to crm.lead activity records (mail.activity), in which case we configure the mapping to crm.lead during scoping. Task assignment resolves hubspot_owner_id to Odoo res.users via the owner lookup table.

HubSpot Ticket records (Service Hub, if applicable) map to Odoo crm.lead with type='lead'. The HubSpot ticket pipeline maps to a separate crm.team distinct from the sales opportunity team, and ticket stages map to crm.stage values within that team. Ticket priority migrates to crm.lead priority. Ticket conversations migrate as mail.message records attached to the crm.lead. If Odoo Helpdesk module is installed, we scope a separate migration path to helpdesk.ticket instead.

HubSpot Products map to Odoo product.product records linked to a product.template record for naming and pricing. HubSpot SKU (hs_sku) maps to product.product.default_code. Standard Price Book entries from HubSpot map to Odoo product.pricelist.item records. If HubSpot Quoting is in use, Odoo Sale Orders replace the quoting workflow post-migration.

HubSpot Line Items map to Odoo sale.order.line records attached to a sale.order that corresponds to the HubSpot Deal. We resolve the product.product reference, price unit, quantity, and discount from the HubSpot line item during migration. The parent sale.order is created from the migrated HubSpot Deal record with partner_id resolved to the Odoo Account (Partner) mapped from the HubSpot Company.

HubSpot contact and company tags map to Odoo crm.tag records applied to the corresponding Partner or crm.lead via the tag_ids many2many field. We create the crm.tag records during schema setup, then apply them during data load. If the customer has more than 50 distinct tag values, we recommend using a custom Char field (x_segment_tags__c) as a comma-separated value rather than individual crm.tag records, to avoid tag proliferation in Odoo.