Migrate from Legistify to Odoo CRM

Legistify matters map directly to Odoo crm.lead records. The matter ID is preserved as x_legistify_id for traceability. Stage mapping routes matter status to the nearest Odoo pipeline stage value — New, Qualification, Proposal, Won, or Lost — via value mapping.

Legistify contracts map to Odoo crm.lead with a custom field x_contract_type set to 'Contract' to distinguish them from matters within the same pipeline. Contract value maps to expected_revenue; the contract ID is stored as x_legistify_contract_id. Party links are resolved to res.partner contact records.

Legistify parties (internal and external contacts on a matter or contract) merge into Odoo res.partner records. Each party role is stored as x_party_role on the res.partner record. Person parties and company parties are both imported as res.partner and distinguished by the type field (person vs. company). Email is the deduplication key.

Legistify company-level records map to Odoo res.partner with type='company'. Company name maps to name; domain becomes website. If a company appears both as a Legistify company and as a party on a matter, the records are merged to a single res.partner.

Legistify clause library entries attached to contracts have no Odoo native equivalent. We preserve the clause library reference and standard clause identifiers as x_clause_library_ref on crm.lead. Clause templates must be rebuilt in Odoo using the Documents app or custom models after migration.

Legistify compliance check metadata (status, reviewer, due date, regulatory reference) migrates as a set of custom fields on crm.lead: x_compliance_status, x_compliance_reviewer, x_compliance_due_date, and x_regulatory_reference. These preserve the compliance audit trail from Legistify within Odoo records. Ongoing compliance workflows, reviewer notifications, and escalation rules must be rebuilt in Odoo Automations (ir.cron) or server actions, as Odoo has no native compliance workflow engine.

Legistify documents attached to matters and contracts are exported and re-uploaded to Odoo ir.attachment linked to the corresponding crm.lead record. File metadata (original filename, create date, uploader) is preserved as attachment field values. Inline document links in Legistify are re-hosted in Odoo.

Legistify risk-level metadata on contracts migrates as x_risk_level (selection field) on crm.lead with values Low, Medium, High, Critical. Risk category and assessment date migrate as companion custom fields x_risk_category and x_assessment_date. Odoo has no native risk-scoring model for CRM leads; the risk logic is preserved as static metadata for reference and reporting.

Legistify automation rules, approval chains, and rule-based triggers tied to contract lifecycle stages do not migrate to Odoo. We export workflow definitions as a structured reference document listing triggers, conditions, and actions. Your Odoo admin uses Odoo Studio (no-code) or server actions to rebuild workflows from the exported definitions. Data migration covers records only; automation logic requires separate configuration in Odoo.

Legistify users and team members are matched to Odoo res.users by email address as the key. Unmatched users are flagged in a pre-migration report; their records in crm.lead are assigned to a fallback owner during import. Active and inactive status in Legistify maps to the active field on Odoo res.users. User permissions and group assignments require Odoo-specific configuration after migration.

Legistify logged activities on matters and contracts migrate as Odoo mail.message records linked to the target crm.lead. Original timestamps, activity type (call, email, note), and owner (user) are preserved in the mail.message fields. Meeting records map to Odoo calendar.event objects. Activity threading is preserved by referencing the parent crm.lead on each message record.

Legistify custom object fields on matters and contracts are created as custom fields on the Odoo crm.lead model. Custom fields on parties become custom fields on res.partner. Field type is preserved (char, selection, date, etc.) using Odoo's custom field type selection.