Migrate from Jarvis Legal to Odoo CRM

Jarvis contacts map directly to Odoo res.partner records. The contact's UUID is stored as a custom field (x_jarvis_id) for traceability. Primary company link resolves via Odoo's partner_id field; contacts without a company land as individual partners. Email, phone, and address fields map field-for-field.

Jarvis matters do not have a direct Odoo equivalent — they split into two objects. Active/open matters route to crm.lead (with type='opportunity'), while closed-won matters create crm.opportunity records that can link to Sale Orders. The matter's internal status (Open, Pending, Closed) drives the Odoo stage assignment during migration.

Jarvis matter types (e.g., Litigation, Corporate, Family Law, Immigration) map to Odoo CRM lead types. Each type value requires explicit pick-list mapping before migration — types not found in Odoo are created as new type records. This ensures matter categorization survives the migration intact.

Jarvis time entries map to project.task records under a default Odoo project created for the migration. Each task preserves the original duration (hours), entry date, description, billable flag, and employee attribution. Unbilled entries remain as tasks; billed entries are linked to corresponding account.move records post-migration.

Jarvis billing records map to Odoo account.move (invoice-type) records. Line items, taxes, and payment terms transfer with original values preserved. Status mapping: Jarvis 'Paid' maps to Odoo 'posted' (reconciled), 'Sent' maps to 'posted' (open), 'Draft' maps to 'draft'. Customer and supplier invoices both route through account.move.

Documents stored in Jarvis's document space transfer to Odoo ir.attachment records. Each attachment is linked to its parent record (contact, matter, or task) via res_model and res_id. Filename and binary content are preserved; large documents may require chunked upload via Odoo's attachment handler. Inline images in notes are rehosted as binary attachments.

Jarvis custom fields on contacts (identified by UUID in the API) are created as Odoo x_def fields on res.partner before migration. The field label, type (text, selection, date, etc.), and help text are carried over from Jarvis's field metadata. Selection-type custom fields require value-by-value mapping to Odoo selection options.

Jarvis custom fields on matters (e.g., court jurisdiction, opposing counsel, filing deadline) migrate to x_def fields on crm.lead. The same pre-creation workflow applies — Odoo fields must exist before records load. Date-type custom fields map to Odoo datetime fields with timezone adjustment if Jarvis stores UTC.

Jarvis task and reminder records map to project.task with their original due dates and assigned user preserved. The task description carries over completely; completion status (done/pending) maps to Odoo's stage_id field. Overdue flags are recalculated from the due date post-migration. Assigned user resolution follows the same email-matching logic used for matter owners.

Jarvis users are matched to Odoo res.users by email address. Unmatched users are flagged before migration — firms either invite them to Odoo first or assign their records to a fallback user. Inactive Jarvis users create inactive Odoo users by default to preserve historical attribution.

Jarvis automated workflows, email templates, and sequence rules do not migrate to Odoo. These must be rebuilt using Odoo's workflow engine, server actions, and email templates. We export workflow definitions as a JSON reference file for your Odoo admin to use as a rebuild guide.

Jarvis report configurations and custom dashboards do not transfer. The underlying data (billing, time entries, matters) migrates, but the report layouts must be rebuilt in Odoo's reporting tools or BI app. Saved filter configurations are exported as reference for manual rebuild.