Migrate from RunSensible to Odoo CRM

RunSensible Client maps to Odoo res.partner with type='contact'. The primary email, phone, and address fields transfer directly. RunSensible's client-level billing flag (IOLTA vs. operating account) maps to a custom selection field on res.partner — Odoo Accounting handles the actual account routing post-migration.

RunSensible sub-contacts (e.g., opposing counsel, co-counsel, billing contacts) attached to a client merge into Odoo res.partner records linked to the same parent_id. The contact's role label (e.g., 'Billing Contact', 'Primary Attorney') transfers as a custom char field on each partner record. If no parent-child relationship exists in RunSensible, contacts become sibling records without parent linkage.

RunSensible Matters map to Odoo crm.lead when the matter is a prospective or active engagement. Matter name becomes crm.lead name; matter description becomes crm.lead description. Matter status (Open/Closed) maps to crm.lead stage_id — we create a custom stage sequence in Odoo's pipeline for legal-matter lifecycle states.

Matters with active task tracking (court filings, discovery deadlines, client deliverables) may warrant a project.project record. We migrate the matter as crm.lead and surface a flag field (Matter_Needs_Project__c) for your consultant to create the project record and link it via crm.lead x_project_id.

RunSensible Leads map 1:1 to Odoo crm.lead. The lead source field (e.g., 'Referral', 'Website') maps to crm.lead source_id via Odoo's utm.source mechanism. Lead priority (Low/Medium/High) maps to crm.lead priority field using value_mapping. Unqualified prospects from RunSensible become crm.lead records without an assigned user_id.

Billable time entries from RunSensible map to Odoo account.analytic.line with product_id, unit_amount (in hours), and partner_id linked to the associated matter's client. Non-billable entries are imported with product_id left null and a note flag for your billing team to review.

RunSensible invoices and bills migrate to Odoo account.move with move_type='out_invoice' or 'in_invoice'. LEDES billing codes map to Odoo's account.account codes via a value-mapping table. The invoice line items reference the analytic lines so Odoo Accounting can reconcile the full matter ledger.

IOLTA trust transactions require Odoo Accounting with separate IOLTA and operating accounts configured. We migrate the transaction records with a custom trust_transaction_type field (retainer/deposit/disbursement). The account.account routing must be set up by your Odoo accountant before the records can post correctly.

RunSensible matter attachments are downloaded and re-uploaded to Odoo ir.attachment linked to the migrated matter's crm.lead record (res_model='crm.lead', res_id=mapped_lead_id). Large files are batched; inline images in documents are extracted and stored separately to avoid blob-size issues in PostgreSQL. E-signature status is preserved in a custom field on the attachment.

RunSensible matter deadlines and court-date reminders map to Odoo calendar.event with partner_ids linked to the associated res.partner client. Start datetime, stop datetime, and allday flag are preserved. Statute-of-limitations dates surface as all-day calendar events with a custom urgency flag for follow-up.

RunSensible custom matter fields (e.g., 'Court District', 'Case Number', 'Statute of Limitations Date') are created as custom fields on crm.lead via Odoo's ir.model.fields API before data loads. Field types are matched: char → char, date → date, selection → selection, decimal → float.

RunSensible attorney and staff records are matched to Odoo res.users by email. Unmatched attorneys are flagged in a pre-migration report — your Odoo admin either creates the user first or assigns records to a fallback attorney. The RunSensible user role (Partner/Associate/Paralegal) becomes a custom field on res.users.