Migrate from Lawmatics to Odoo CRM

Lawmatics Matters are the primary legal-intake record and map to Odoo crm.lead. The Matter's intake_status maps to stage_id via a value-mapping table built during the pre-migration audit. Law-firm-specific fields (practice_area, court_jurisdiction) migrate as custom fields on crm.lead. The original Lawmatics matter ID is stored in x_lawmatics_id for traceability.

Lawmatics Contacts map to Odoo res.partner with partner_type = 'contact'. When a Lawmatics contact has an associated primary company, the migration sets parent_id to the migrated company partner. Email and phone are stored as email and phone on res.partner. All custom contact fields (e.g., bar_number, client_type) become custom fields on the partner record.

Lawmatics Companies map to Odoo res.partner with company_type = 'company'. The parent-child hierarchy in Lawmatics (parent_company_id) maps to the parent_id field on res.partner. Lawmatics company domains and industry values are mapped to the website and industry_id fields in Odoo. Annual revenue and employee count from Lawmatics become custom fields if they do not have a native Odoo equivalent.

Lawmatics automations are stored as separate workflow objects with triggers, entry conditions, and multi-step action chains. Odoo CRM has a separate Automated Actions module with different schema and trigger semantics. FlitStack exports all automation definitions as a JSON reference document so the Odoo administrator can rebuild each automation in Odoo's Automated Actions UI or via server actions.

Lawmatics tasks (calls logged, emails, follow-ups) map to Odoo crm.activity records linked to the crm.lead via res_id. The activity_type (call, email, meeting) maps to the activity_type_id field. Original owner, create date, and completion status are preserved as fields on the activity record.

Lawmatics notes migrate as Odoo mail.message records with message_type = 'note' linked to the crm.lead or res.partner. Note body text maps to the body field. Rich-text formatting from Lawmatics is preserved in HTML where the source note uses it. Multiple notes on a single matter may create multiple Odoo message records.

Lawmatics file attachments linked to matters or contacts migrate as Odoo ir.attachment records. Files are downloaded from Lawmatics storage and uploaded to Odoo's filestore with the original filename preserved. Each attachment is linked to the target record (crm.lead or res.partner) via the res_model and res_id fields. File size limits from Odoo's configuration apply.

Every Lawmatics custom field defined on Matters becomes a custom field on Odoo's crm.lead model. The migration plan documents each field name, type (char, date, selection, etc.), and current values so the Odoo admin can create the corresponding field via Studio before the migration run. Values are loaded in the same sequence as standard field data.

Lawmatics contact-level custom fields (e.g., bar_license_number, referral_source) map to custom fields on Odoo res.partner. The migration plan lists each field name and type. Odoo Studio or direct XML field creation is required before the full data load, and the field mapping plan is delivered before the migration run.

Lawmatics intake_status values (e.g., New Inquiry, Under Review, Intake Complete) map to Odoo CRM stage records. Each unique status value in Lawmatics becomes a crm.stage entry in Odoo's pipeline. Probability values are assigned per stage. Stage-entry timestamps from Lawmatics are preserved in a custom datetime field x_stage_entered_date for reporting continuity.

Lawmatics user accounts are resolved against Odoo res.users by email address matching. The user's Lawmatics ID and display name are stored in a custom field x_lawmatics_owner_id on the migrated record so audit trails remain traceable. Users without an Odoo match are flagged before migration; a fallback owner (admin) is assigned to prevent orphaned records.

Lawmatics events (appointments with date, time, location, and attendees) map to Odoo calendar.event records. The event is linked to the corresponding crm.lead via res_model and res_id. Attendee information from Lawmatics creates calendar.attendee records linked to the event. Start and end times are preserved from the source.

Lawmatics tags applied to matters and contacts map to Odoo crm.tag records. Tags are associated with crm.lead via the tag_ids many2many field. Tag names are preserved exactly as they appear in Lawmatics. If a tag name collides with an existing Odoo tag, the existing tag is used to avoid duplicates.

Lawmatics invoices and payment records are legal-financial records that require the Odoo Accounting app (account.move model) rather than the CRM module. FlitStack can export invoice data as a structured file for import via Odoo's accounting import wizard, but full invoice-to-payment reconciliation requires the accounting app to be installed and configured. This is flagged in the pre-migration scope discussion.