Migrate from Clarify CRM to Odoo CRM

Clarify Contact records map to Odoo res.partner with is_company=False and partner_latitude/longitude fields preserved. Email maps to email, phone to phone, and job_title to function. We set the commercial_partner_id to the linked Company record's res.partner ID at migration time. All standard contact fields migrate directly; AI-enriched custom fields are flagged during scoping for the customer to review before import.

Clarify Company records map to Odoo res.partner with is_company=True. Domain-based enrichment from Clarify populates the website field. We set parent_id=null on company records and use the commercial_partner_id for hierarchy (company as parent of individual contacts). Company-specific fields like industry, employee_count, and annual_revenue map to custom res.partner fields that we pre-create in the destination Odoo database.

Clarify Deal records map to Odoo crm.lead with type='opportunity'. Deal value maps to planned_revenue, close_date maps to date_deadline, and deal name maps to name. The linked Company res.partner becomes the partner_id on crm.lead; the linked Contact res.partner becomes the contact_id. We set active=True and probability based on the mapped stage_id probability value.

Clarify pipeline stages map to Odoo crm.stage records within a crm.pipeline. We capture the full stage sequence, custom stage names, and probability percentages from Clarify and create equivalent stages in Odoo with corresponding sequence order and is_won/is_lost flags. Stage names are normalized to Odoo's slug-style naming convention for kanban display.

Each Clarify pipeline maps to an Odoo cdoo.pipeline record. Odoo allows multiple pipelines visible in separate kanban views. We create one pipeline per Clarify pipeline and assign the corresponding stage sequence. The pipeline's team_id maps to an Odoo crm.team that we provision during migration.

Clarify tags migrate to Odoo crm.tag records, and tag assignments migrate to crm.tag_rel linking crm.lead to crm.tag. Tags used on Clarify Company records are stored as res.partner category_id entries (using res.partner.category). We deduplicate tag names before import to avoid Odoo raising unique constraint violations on tag creation.

Clarify call activities map to Odoo mail.activity records with activity_type_id='Call'. Activity date, duration, and outcome notes from Clarify populate mail.activity date_deadline, summary, and note fields. The activity's res_model is set to crm.lead and res_id to the migrated crm.lead id.

Clarify email engagement records migrate to Odoo mail.message with message_type='email'. Body content migrates as HTML body, subject as subject. We link mail.message to the migrated res.partner record via model='res.partner' and res_id. Email from/to addresses map to email_from and recipient_ids.

Clarify meeting activities map to Odoo calendar.event records with start, stop, and location fields populated. Attendees from Clarify meeting records resolve to res.partner attendees via partner_ids on the calendar.event. We preserve the original meeting timestamp in calendar.event start_datetime.

Clarify note activities and standalone notes migrate to Odoo mail.message with message_type='notification' and subtype='mt_note'. AI-generated meeting summaries stored as note content are migrated as mail.message body text, flagged with a migration note in the message metadata so the customer knows which content was autonomous-generated in Clarify.

Clarify custom fields on Contact, Company, and Deal objects require pre-creation in Odoo as ir.model.fields before data import. We extract the field type from Clarify (text, number, date, currency, multi-select) and map to the nearest Odoo field type (char, float, datetime, monetary, selection). Many-to-many and multi-select fields on Contact map to res.partner.tag_ids if appropriate, otherwise we create dedicated custom selection or char fields.

Clarify Owner records map to Odoo res.users by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Activity and match against res.users in the destination Odoo database. Owners without a matching user are held in a reconciliation queue for the customer's Odoo admin to provision before record import resumes.