Migrate from Clientify to Odoo CRM

Clientify Contact records map to Odoo res.partner with type=contact. The Clientify contact's linked Company association becomes res.partner.parent_id pointing to the company-type Partner record. Standard fields (name, email, phone, mobile, website) migrate directly; custom properties require pre-creation in Odoo via Settings > Technical > User Interface > Views or Studio before import. Partner addresses (street, city, state, zip, country) migrate to res.partner address fields with country_id resolved from Odoo's country table by ISO code match.

Clientify Company records map to Odoo res.partner with type=company. The company flag is set at import time. Industry, size, and address fields migrate directly. Each company Partner is created before any linked Contact import so that the parent_id lookup is satisfied. Company records without contacts become standalone Partner records with no children.

Clientify Lead object maps directly to Odoo crm.lead. The crm.lead.type field is set to lead for unqualified prospects. Lead score from Clientify's AI scoring migrates to a custom float field (x_clientify_lead_score__c) pre-created in Odoo before migration. Lead source and status fields map to crm.lead.source_id and stage_id with stage resolved from Odoo's configured pipeline stages.

Clientify Deals map to Odoo crm.lead with type=opportunity. The crm.lead.partner_id is resolved to the res.partner record created from the Deal's linked Contact and Company during the partner import phase. Expected revenue and probability migrate to planned_revenue and probability fields. Stage mapping uses Clientify's dealstage to Odoo's stage_id with a mapping table created during schema design. Closed-Won and Closed-Lost outcomes from Clientify map to Odoo's wonln stage and the configured lost stage.

Clientify pipeline stage names and their sequence order migrate to Odoo crm.stage records within the relevant sales team pipeline. Stage probability percentages are stored on crm.stage.probability. We create the stage records in Odoo Settings > CRM > Stages before the Deal import begins so that stage_id references resolve at import time. Stage-automation actions (stage-change triggers) are not migrated; they are documented in the automation inventory for Odoo Studio rebuild.

Clientify engagement records (calls, emails, meetings, tasks) attached to Deals and Leads migrate to Odoo's crm.lead activity history (mail.message records with res_model=crm.lead). Each activity's date and subject map to mail.message.date and subject respectively. Call duration and disposition migrate to custom fields on the activity record if present. Activity type classification (call vs email vs meeting) is preserved in a custom activity_type field or through the subtype_id if Odoo's mail subtype configuration is active.

Clientify custom fields on Contacts, Companies, and Deals require pre-creation in Odoo before migration begins. We map field types during scoping: Clientify text, number, and date fields map directly to Odoo Char, Float/Integer, and Date field types; picklist fields require Odoo Selection fields with the same allowed values pre-populated or the import will reject records with unknown picklist values. Multi-select picklist values are stored as comma-separated Char in Odoo unless a dedicated many2many relationship is configured during schema design.

Clientify campaign records including open rates, click rates, and send volumes migrate as campaign metadata attached to crm.lead records via the source_id or utm_campaign fields. The campaign automation logic (A/B tests, trigger conditions, send-time rules) lives in Clientify's campaign builder and cannot be extracted; we migrate the performance history as data, document the campaign structure for Odoo email marketing rebuild, and note that Odoo's email marketing module (mass_mailing) requires separate configuration to replicate the sending logic.

WhatsApp message threads linked to Clientify Contact records migrate where Clientify's API exposes the conversation data at migration time. We extract message text, sender, timestamp, and message count as metadata; media attachments and delivery/read receipts depend on Clientify's export capability. The migrated data lands as mail.message records with a WhatsApp subtype on the related crm.lead or res.partner. We flag completeness gaps in the pre-migration audit and document the WhatsApp rebuild options in Odoo (native module or third-party WhatsApp Business API connector).

Clientify Owner records (sales reps, admin users) map to Odoo res.users by email match. We export all Owner IDs referenced on Contact, Company, Deal, and Activity records and match against the destination Odoo User list. Users not yet provisioned in Odoo are placed in a reconciliation queue; the customer admin creates the missing User accounts before record import resumes. Active/inactive status is preserved from Clientify.

Clientify tags attached to Contacts and Deals migrate to Odoo crm.tag records. Tags are linked to crm.lead via crm.tag.rel many2many table. Segment definitions built on dynamic filters in Clientify cannot be extracted; we document the filter criteria for manual reconstruction in Odoo CRM's group and filter system.

Clientify workflow rules stored in its proprietary automation builder have no portable export format. We do not migrate automations. We provide a structured automation inventory worksheet during scoping that documents every active rule's trigger, conditions, actions, and delays. The customer's Odoo admin rebuilds these in Odoo Studio (trigger actions, automated actions, server actions) post-migration. This is a manual step outside standard migration scope.