Migrate from Column Case Management to Odoo CRM

Column subject types (witness, victim, suspect) require custom fields — no native Odoo equivalent

Column's subject model supports role classification (witness, victim, suspect, party, informant) with configurable pick-list values per case type. Odoo's res.partner has no native role or subject-type field. We store the original role in a custom pick-list field (x_subject_type) on res.partner during migration. Your Odoo admin can use this field for filtered views or reporting, but Odoo does not enforce role-based access control on subject types the way Column does. If your team relies on role-based visibility rules for sensitive subject types, those rules must be rebuilt as Odoo record rules after migration.

Case custom fields on crm.lead do not auto-copy during Odoo lead-to-opportunity conversion

Odoo's built-in lead conversion action (converting a crm.lead to crm.opportunity and res.partner) copies only standard fields. Custom fields on crm.lead — including x_case_priority, x_case_type, x_jurisdiction, and x_risk_rating — do not automatically copy to the resulting opportunity or partner. We store the full Column case schema as custom fields on crm.lead with original values preserved. If your team plans to use Odoo's native lead-to-opportunity conversion, you must either extend Odoo's conversion wizard with a custom module to carry x_ fields forward, or build a server action that manually copies them after conversion.

Evidence attachment re-attachment requires res_model and res_id repointing post-migration

Column stores evidence files with direct attachment-to-case linkage including chain-of-custody metadata. Odoo stores attachments in ir.attachment with res_model='crm.lead' and res_id pointing to the parent lead ID. During migration, each ir.attachment record is created with the correct res_model and res_id so links are immediately functional. However, Odoo's document management module (documents app) uses a separate ir.attachment variant with a different resource model (documents.document). If your team uses Odoo Documents alongside CRM, evidence attachments must be repointed to the documents.document model manually or via a post-migration script.

Column workflows and automated escalations have no Odoo migration path

Column Case Management includes an investigative workflow engine that automates task routing, deadline escalation, status transitions, and notification triggers based on case events. Odoo has automation rules and Studio workflows, but they operate on different triggers and conditions. We export your Column workflow definitions as a structured JSON document that your Odoo administrator can use as a functional specification for rebuilding automations in Odoo Studio. Timeline-based escalations, conditional task assignment, and status-change notifications require custom server actions or Odoo Enterprise's advanced automation features.

Case priority taxonomy requires custom field — Odoo's native priority is a numeric scale

Column's priority system typically includes four or five named levels (Critical, High, Medium, Low, or equivalent) with configurable labels per case type. Odoo's native priority field on crm.lead uses a 0-1 decimal scale for star ratings, not a named pick-list. We preserve your original Column priority values in a custom selection field (x_case_priority) on crm.lead. This field integrates with Odoo's kanban view grouping and search filters, but kanban stage coloring and dashboard reporting that use Odoo's native priority star scale will reference the numeric field instead. Odoo Studio can be used to replace the native priority field label with your custom pick-list values in all views.