Migrate from ArkCase to Odoo CRM

ArkCase persons (individuals) map to Odoo res.partner with type='contact'. The person's name splits into firstname/lastname on Odoo. Address fields from ArkCase's dm_location map to partner address fields (street, city, state_id, country_id, zip). Email and phone map directly. A custom field arkcase_person_id__c stores the source ArkCase ID for traceability.

ArkCase organizations map to Odoo res.partner with type='company'. Organization name becomes partner name. Website, industry, and employee count map to Odoo website, industry_type, and employee counts. Parent-child org hierarchies in ArkCase map via Odoo's parent_id field on res.partner — the parent org must migrate first to resolve the foreign key.

ArkCase supports many-to-many relationships between persons and organizations. Odoo CRM has no native equivalent — a person can have one primary company via parent_id but N:N associations require Odoo Contacts module or a custom relation object. We map primary associations via parent_id and surface secondary associations as a custom notes field for admin review.

ArkCase cases map to Odoo crm.lead. The case title becomes the lead name, case status maps to Odoo stage_id via value mapping, priority maps to priority field, and case_type maps to a custom field arkcase_case_type__c. Original case create date preserved as a custom datetime field since Odoo's create_date reflects migration time. Owner resolved by email match to Odoo res.users.

ArkCase complaints (a subtype of case) map to crm.lead with a custom field arkcase_complaint_id__c storing the original complaint number. Complaint category and subcategory values map to custom picklist fields in Odoo or to tags on the lead. The complainant person links to crm.lead partner_id (the person who filed the complaint).

ArkCase tasks map to Odoo mail.activity records linked to the parent entity (partner, lead, or project.task). Task summary becomes activity name, description maps to note, due date maps to date_deadline, and status maps to activity type. The task assignee resolves to an Odoo res.users record by email match — unassigned tasks in ArkCase surface as unlinked activities flagged for review.

ArkCase documents (dm_document records) export with their binary content and re-upload to Odoo as ir.attachment records. The attachment's res_model and res_id point to the migrated parent record (crm.lead for cases, res.partner for persons/organizations). Original filename, create date, and creating user are preserved. Files exceeding Odoo's upload size limit are flagged for manual retrieval.

ArkCase FOIA and public records requests are a specialized case type. These map to crm.lead with custom fields tracking request_type, request_date, due_date, exemption codes, and response status. The request's associated documents migrate as ir.attachment records linked to the lead. Odoo does not have a native FOIA module — legal teams use custom fields and Studio views to replicate the request workflow.

ArkCase case parties (complainant, respondent, interested party roles) link persons to a case. In Odoo, the crm.lead partner_id stores the primary contact. Additional parties require the Contacts module's partner relation feature or a custom partner multiple-relation approach — we map the primary party to partner_id and surface role-based associations as custom text fields for admin reconciliation.

ArkCase calendar entries for hearings, deadlines, or meetings map to Odoo calendar.event records. Event title, start datetime, end datetime, and attendees (linked to res.partner) migrate. The event's related case or complaint links via a custom reference field. Odoo calendar invites (attendee notifications) require Odoo to be configured with a mail server.

ArkCase notes and comments attached to cases, persons, or organizations map to Odoo mail.message records on the related model. Author, body content, create date, and attachment references migrate. Mail messages in Odoo display in the chatter of the parent record (crm.lead or res.partner).