Migrate from PCLaw(r) to Odoo CRM

PCLaw client records map to Odoo res.partner. The client name maps to the partner's display_name, address fields map to street, city, state, country, and the client phone/email map to phone and email fields. Active/inactive client status sets the partner's active flag.

PCLaw matters become Odoo crm.lead records in opportunity mode. The matter description becomes crm.lead.name, the responsible attorney maps to user_id, and matter open date becomes the lead's create_date. Matter status (open/closed) maps to the lead's active flag and stage assignment.

PCLaw matter status values (Open, Pending, Closed Won, Closed Lost) map to specific Odoo CRM pipeline stages. We create a dedicated legal pipeline in Odoo with stages matching your PCLaw status taxonomy. Unmatched statuses default to a generic 'New Lead' stage.

PCLaw billing records map to Odoo sale.order as reference documents. The bill amount, bill date, and bill number become sale.order amounts and names. Odoo does not natively carry PCLaw LEDES billing codes — these are preserved as order line notes for your accountant to rebuild in Odoo Accounting.

PCLaw three-way trust accounting (client ledger, operating account, IOLTA) has no direct Odoo CRM equivalent. We export trust account balances, client trust sub-account numbers, and ledger transactions as a structured CSV for your Odoo accountant to create the chart-of-accounts entries in Odoo Accounting post-migration.

PCLaw time entries map to Odoo analytic account lines. The attorney, date, duration, task description, and billing rate transfer to analytic lines linked to the corresponding matter (project). Rate information becomes a reference note field. Time entries without a valid matter reference are logged separately for manual review and linkage during the post-migration audit.

PCLaw expense entries map to Odoo analytic lines with expense category flags. Vendor name, expense date, amount, and matter reference transfer. Odoo analytic accounting must be enabled for these records to surface in reporting. Expense entries that cannot be matched to a matter are flagged in the migration report for your team to resolve in Odoo after go-live.

PCLaw documents attached to matters are exported and re-uploaded as Odoo ir.attachment records, linked to the corresponding crm.lead by res_id/res_model. File name, binary content, and create date are preserved. Large document batches are migrated in sequence to avoid API timeout.

PCLaw attorney and staff records map to Odoo res.users for CRM owner assignment. Email addresses are used to match existing Odoo users; unmatched staff are flagged as contacts (res.partner) until Odoo user accounts are provisioned. Role-based security groups (groups_id) are assigned based on the staff role mapped during transformation.

PCLaw user-defined client fields become Odoo custom fields on res.partner. We create the fields via Odoo Studio before import, using the same field type (char, date, selection, etc.) and populate values during the bulk import pass. Selection fields require a value map between PCLaw picklist options and Odoo selection keys to ensure data integrity.

PCLaw user-defined matter fields become Odoo custom fields on crm.lead. Custom fields are created pre-migration, and their values are loaded in the same import batch as matter records. Selection-type custom fields require explicit value mapping. Multi-select fields are stored as comma-separated values in Char fields to maintain compatibility with Odoo's field type constraints.

PCLaw matter deadlines and court dates map to Odoo calendar.event records linked to the crm.lead. Event name, start date, and responsible user transfer. Recurrence rules are not preserved — recurring events are loaded as individual records. Reminder alerts and attendee notifications are disabled during import to prevent premature notifications before the CRM is live.