Migrate from Law Ruler to Odoo CRM

Law Ruler leads from intake forms map to Odoo crm.lead records. In Odoo, crm.lead serves as both raw lead and opportunity depending on stage. The lead_type field determines whether the record is a 'lead' or 'opportunity' in Odoo's kanban pipeline view. Original intake form submission date preserved as a custom field.

Law Ruler clients map to Odoo res.partner records. In Odoo, res.partner represents both individual contacts and company records — Law Ruler's separate 'Company' concept (if present) maps to the same partner record with company_name populated. Partner type (client vs. company) stored as a custom field on res.partner.

Law Ruler cases do not have a direct Odoo CRM equivalent — Odoo's CRM module has no native case object. We migrate cases as project.project records, creating one project per Law Ruler case. Custom fields (practice area, venue, opposing counsel) transfer as project.task custom fields. The firm can alternatively request a custom crm.case model built in Odoo Studio.

Every Law Ruler custom intake field (statute of limitations, referral source, retention status, practice area, etc.) requires a corresponding custom field created in Odoo before migration. We generate a field creation manifest from Law Ruler's field definitions and apply it to crm.lead and res.partner as appropriate. Field types (picklist, date, text) map to Odoo selection, date, and char fields respectively.

Law Ruler's lead stages (New Lead, Contacted, Qualified, etc.) map to Odoo crm.stage records. Stage names are mapped value-by-value, preserving the Odoo stage sequence order. If Law Ruler uses a different number of stages than Odoo's default pipeline, we create or rename stages to match the source. Stage-entered timestamps from Law Ruler preserved as custom datetime fields.

Law Ruler logged activities (calls, meetings, tasks) map to Odoo mail.activity records linked to crm.lead. Notes from Law Ruler migrate to Odoo note records (mail.message or note.note). Original activity timestamps, owners (by email match to Odoo users), and activity type preserved. Recurring activities require manual review since Odoo's recurrence model differs.

Law Ruler documents attached to leads, clients, or cases migrate as Odoo ir.attachment records linked to the corresponding crm.lead or project.project. Files are downloaded from Law Ruler's storage and re-uploaded to Odoo's filestore (or an external document management system if Odoo Documents module is in use). Maximum file size follows Odoo's default 25MB per attachment.

Law Ruler's assigned attorney or paralegal on a lead or case resolves to an Odoo res.users record by email address match. Unmatched owners are flagged before migration — firms either create Odoo user accounts for those staff members or assign records to a fallback user. Active/inactive status in Law Ruler maps to Odoo's active flag on res.partner.

Law Ruler automations (task triggers, email sequences, stage-change workflows) have no Odoo CRM equivalent in the base migration scope. They must be rebuilt in Odoo using automated actions (base_automation, Enterprise) or Odoo Studio workflows. We export Law Ruler workflow definitions as a JSON reference document for the firm's Odoo admin to use during rebuild.

Law Ruler's document automation templates (Word, PDF, Excel with mail merge codes per field) do not migrate to Odoo. Odoo's reporting uses a different template engine (QWeb) and does not support direct mail merge code conversion. Templates must be rebuilt using Odoo Reports or third-party document automation tools. We provide a field-mapping reference so the rebuild team knows which Odoo field corresponds to each Law Ruler mail merge code.

Law Ruler email marketing campaigns and subscriber lists do not migrate. Odoo's marketing module (email marketing, mass mailing) uses a different campaign model and contact list structure. Subscriber lists can be exported as CSV and imported as Odoo mailing lists, but automation logic (drip sequences, conditional sends) requires manual rebuild. Marketing contact status (subscribed/unsubscribed) preserved in CSV export.