Migrate from Case.one to Odoo CRM

Case.one Contact maps directly to Odoo res.partner where the contact type is set to 'contact'. Standard fields including name, email, phone, street, city, state, zip, and country migrate on a one-to-one basis. The primary_company relationship from Case.one sets the res.partner.parent_id field to reference the corresponding mapped company partner record, preserving the contact-to-company hierarchy during migration.

Case.one Company maps to Odoo res.partner with type set to 'company'. The company name becomes partner name. Case.one's industry, website, and address fields map to the equivalent Odoo res.partner fields. Parent-child company hierarchies in Case.one become parent_id links in Odoo.

Case.one Cases split into Odoo crm.lead records based on status. Open and Pending cases route to crm.lead type 'opportunity' so they appear in the Odoo pipeline view. Closed and Won cases route to type 'lead'. Each split is configurable based on your case-status-to-pipeline-stage mapping plan before migration runs.

Case.one Case Status pick-list values (Open, Pending, On Hold, Closed Won, Closed Lost) are mapped value-by-value to Odoo crm.stage records. Each stage belongs to a specific Odoo sales team. Stage sequence and probability values are applied per Odoo's stage configuration during the migration plan phase.

Case.one custom fields on Cases (e.g., matter_type, practice_area, court_jurisdiction, lead_attorney) are pre-created in Odoo Studio before migration using the x_studio_ naming convention. Field types (char, selection, float, date) are matched to Odoo's equivalent field types. Custom field values populate after the field is created in Odoo.

Case.one custom fields on Contacts (e.g., bar_number, department, billing_rate) are pre-created in Odoo Studio on res.partner before migration. Values migrate as text, selection, or float depending on the Case.one field type. Billing rate values are stored as float fields on the partner record for use in Odoo Timesheet or Odoo Billing if those modules are activated.

Case.one documents attached to cases are downloaded from Case.one storage and re-uploaded into Odoo as ir_attachment records linked to the corresponding crm.lead. Attachment filename, mimetype, and create_date are preserved. Odoo's attachment size limit (default 25MB per file) applies; files exceeding this are flagged before migration for manual handling.

Case.one users and attorneys are resolved by email match against Odoo res.users. Unmatched users are flagged before migration — your team either creates the Odoo user first or assigns their Case.one cases to a fallback Odoo user. Active status and user_type (internal vs. portal) are set based on Case.one user role. Attorney-specific role data migrates as a custom field on the mapped crm.lead.

Case.one time entries and billable hour records are summarized and stored as custom float fields on the linked crm.lead (for case-based billing) and res.partner (for attorney rate tracking). Odoo's timesheet and billing modules require separate configuration if you want full time-tracking in Odoo; the migration preserves the historical data for reporting continuity.

Case.one case notes and activity logs migrate as mail.message records linked to the corresponding crm.lead in Odoo. Original author, timestamp, and body text are preserved. Odoo's mail thread model displays these as a chronological activity log on each lead or opportunity record in the chatter widget.

Case.one invoicing records (invoice number, amount, status, date) do not map to Odoo Account objects because Odoo Accounting is a separate module. We store invoice metadata as custom fields on the crm.lead so billing history is visible alongside the case record. If Odoo Accounting is activated, invoice records are created separately post-migration.

Case.one tags or categories applied to cases (e.g., litigation, corporate, real_estate) are mapped to Odoo crm.tag records. Tags are linked to crm.lead records via the crm_lead_tag_rel many-to-many table. Tags that have no Odoo equivalent are created during migration as new crm.tag records before records are loaded.