Migrate from Clarra to Odoo CRM

ClarRa clients are organizations or individuals receiving legal services. Odoo res.partner is a unified model for both contacts and companies. We set company_type='company' for organizational clients and company_type='person' for individual clients. All Clarra client properties migrate as res.partner fields or custom fields on the partner record.

ClarRa contacts are individuals linked to clients. In Odoo, contacts are also res.partner records but with company_id set to the parent client partner. We resolve the parent relationship by matching contact.client_id to an existing res.partner record. If no match exists, the contact lands as a standalone partner flagged for review.

ClarRa matters are the core legal entity — each tied to one client with parties, events, deadlines, and documents attached. Odoo crm.lead is a CRM opportunity model without a native matter concept. We map every ClarRa matter to a crm.lead record, setting type='opportunity' and storing legal-specific properties (practice_area, case_number, opposing_counsel, court) as custom fields on the crm.lead. The crm.lead name field holds the matter title.

ClarRa matter status values (Open, Pending, On Hold, Closed Won, Closed Lost) map to Odoo CRM stage records. We read the existing crm.stage records in your Odoo database and create a value-mapping table before migration. Custom ClarRa statuses that have no Odoo stage equivalent are created as new stage records during schema setup, ensuring no matter lands in an unmapped status.

ClarRa parties are contacts with assigned roles (e.g., Opposing Counsel, Plaintiff, Defendant) on a matter. Odoo crm.lead has no native party-role model. We map the primary party as the crm.lead.partner_id and store additional party roles as a serialized custom field (party_roles__c) listing each role and associated res.partner ID for post-migration reconciliation by your Odoo admin.

ClarRa events and deadlines are calendar entries tied to matter records. We map them to Odoo calendar.event records linked to the crm.lead via res_model='crm.lead' and res_id set to the migrated crm.lead ID. The event name maps to calendar.event.name, start_date maps to start_datetime, and event type maps to categ_id via value mapping against Odoo's calendar.category records.

ClarRa documents (PDFs, DOCX, XLSX) attached to matters or contacts migrate as Odoo ir.attachment records. We set res_model='crm.lead' for matter documents and res_model='res.partner' for contact documents, with res_id pointing to the migrated record ID. Files are re-uploaded via Odoo's /web/binary/saveas endpoint; inline images in ClarRa notes are extracted and re-hosted as attachments.

ClarRa matter assignments link to attorney users by email. Odoo crm.lead.user_id is a res.users lookup. We match ClarRa assigned_to_user emails against res.users.login in your Odoo instance. Unmatched users are flagged with a fallback owner assignment before migration commits. This ensures no crm.lead lands without a valid user_id.

ClarRa custom matter fields like practice_area and case_number have no Odoo CRM native equivalent. We create these as x_studio fields (or ir.model.fields custom fields) on crm.lead during the schema setup phase before data migration begins. Each custom field is documented in the field-level mapping plan so your Odoo admin can configure field visibility and access rights per profile before the migration run.

ClarRa matter workflows and rule-based automation triggers have no direct Odoo CRM equivalent. We do not migrate them. Instead, we export ClarRa workflow definitions as a structured JSON document listing each rule, trigger condition, and action — this becomes the rebuild reference for your Odoo admin to reconstruct logic using ir.actions.server, base.automation, or Odoo Studio.

ClarRa matter templates (pre-filled matter structures for common case types) do not transfer to Odoo CRM. Odoo has no native matter-templating feature. We recommend recreating common matter structures as Odoo CRM templates or using ir.actions.server quick-action records. Our migration deliverable includes a template mapping plan that pairs each ClarRa template with the equivalent Odoo record-creation pattern.

ClarRa notes on matters and contacts migrate as Odoo mail.message records with message_type='comment'. We set res_model to 'crm.lead' or 'res.partner' as appropriate and res_id to the migrated record ID. Original note body text, author, and create_date are preserved. Rich-text formatting in ClarRa notes is converted to plain text with line breaks preserved to avoid Odoo mail composer rendering issues.