Migrate from ContactWise CRM to Odoo CRM

ContactWise Contacts map directly to Odoo res.partner records with partner_type set to 'contact'. The ContactWise contact_name becomes res.partner.name; email, phone, mobile, website, and address fields map to their Odoo equivalents. Custom contact properties on ContactWise require pre-creation of custom fields in Odoo via Studio or direct field definition. ContactWise stores purchase history and demographics as related properties; these migrate as custom fields on res.partner with type transformation (for example, multi-select picklists convert to Odoo char or many2many tags). res.partner is the central record; all other CRM objects in Odoo reference it via partner_id.

ContactWise Leads map to Odoo crm.lead records with type = 'lead' (as opposed to type = 'opportunity'). Lead status and source attribution from ContactWise map to crm.lead stage_id and source_id respectively. The ContactWise lead_name becomes crm.lead.name. We resolve partner_id by matching the ContactWise contact associated with the Lead against the imported res.partner records. If the Lead has no associated Contact, the lead is imported without a partner_id and the Odoo admin links it during review.

ContactWise Opportunities map to Odoo crm.lead records with type = 'opportunity'. The opportunity name maps to name, amount maps to planned_revenue, expected close date maps to date_deadline, and owner assignment maps to user_id via email matching to Odoo res.users. Stage mapping is handled via the Pipeline Stage configuration step. The ContactWise deal value and stage are preserved in the stage_id and tag_ids fields.

ContactWise Companies map to Odoo res.partner records with partner_type set to 'company'. Company name maps to name; registered address, phone, and website map to their Odoo equivalents. res.partner records with partner_type=company serve as the parent record for res.partner records with partner_type=contact (individual contacts under a company account). We create Company records before Contact import to satisfy the parent_id lookup during Contact insert.

ContactWise pipeline stage names and order are documented during discovery and mapped to Odoo crm.stage records within the relevant crm.team. Stage probability percentages from ContactWise map to Odoo stage sequence and probability fields. Odoo uses a Kanban-stage architecture; each stage is tied to a crm.team (sales team). We create stage mapping documentation and apply the mapping during the Opportunity import phase.

ContactWise service desk tickets map to Odoo helpdesk.ticket records. Ticket subject maps to name; ticket state maps to stage_id (Odoo Helpdesk stages include New, In Progress, Pending, Solved, Closed); priority maps to priority. We perform field-level mapping for every ContactWise ticket attribute because the field schemas differ substantially. Ticket-to-contact association is preserved via partner_id linking the migrated res.partner record. Conversations and comments on tickets migrate as mail.message records attached to the helpdesk.ticket. Odoo Helpdesk must be installed as an additional app on top of the base CRM module.

ContactWise time entries associated with Contacts, Tickets, or Projects do not map to a standard Odoo CRM object. In Odoo's base CRM module, time tracking is not native. If the customer has Odoo Timesheets or Project management installed, time entries migrate to account.analytic.line with project_id, task_id, name (description), unit_amount, and partner_id linked to the associated res.partner. If Odoo Timesheets is not in scope, we export time entries to a structured CSV and document the recommended Odoo configuration to activate the timesheet module post-migration.

ContactWise documents and attachments associated with Contacts, Opportunities, or Tickets migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding Odoo record (res.partner, crm.lead, or helpdesk.ticket). We export files to cloud storage and create attachment records pointing to the stored files. Attachment migration requires careful path mapping to preserve the association between the file and the parent record in Odoo.

ContactWise custom properties on Contact and other objects do not always correspond to standard fields in Odoo res.partner. We identify every custom property during scoping, create matching fields in Odoo via Studio (or direct ir.model.fields definition) before import, and apply value transformations where data types differ. Multi-select picklists convert to Odoo char fields or many2many tags depending on the cardinality of values. Date fields use the Odoo-expected datetime format. Custom fields are created in a development or sandbox Odoo environment before production migration.

ContactWise Workflow rules store automation logic (triggers, conditions, actions) as platform configuration and do not export as records. We document every active ContactWise workflow during discovery: trigger type, conditions, and actions. This inventory is delivered to the customer as a written handoff document. The Odoo admin rebuilds equivalent automation in Odoo using Studio Automations or server actions. Time-based reminder triggers in ContactWise have no direct Odoo equivalent and are flagged explicitly in the inventory for manual design decisions.

ContactWise Owners map to Odoo res.users records. We resolve owners by email match against the Odoo destination database. Any ContactWise Owner without a matching res.users record is held in a reconciliation queue; the customer's Odoo admin provisions the missing user before record import resumes. Active/inactive status in ContactWise maps to active=True/False in Odoo res.users.

ContactWise note engagements map to Odoo mail.message records linked to the parent record via res_model and res_id. The note body migrates as mail.message.body (HTML) and displays in the Odoo chatter on the parent record (res.partner, crm.lead, or helpdesk.ticket). We preserve the original timestamp in mail.message.date and set message_type to 'comment'.