Migrate from Bilr to Odoo CRM

Bilr Client records map directly to Odoo res.partner. Name, email, phone, address, and website fields translate field-for-field. Multiple contacts per client collapse to one primary res.partner — additional contacts migrate as Contact records linked via 'Contact' type on the partner.

Individual Bilr Contact records (within a Client) map to res.partner with type='contact'. Email, phone, name, and job title translate directly. Parent company link uses res.partner's Parent Partner field to maintain client-contact hierarchy. If a contact has multiple phone numbers, additional entries store as separate contact subrecords under the same partner.

Bilr Matters have no native Odoo equivalent — they bridge contact and billing data. We map Matter to crm.lead as Opportunities, with Matter name as Opportunity name, status as stage, and client as the linked res.partner (partner_id). Billing-specific fields (rate, billing method) become custom fields on the crm.lead record.

Time entries carry description, hours, date, and billing rate. In Odoo, these become CRM activities (mail.activity) with type='Other', original date preserved, description in the activity note, and hours stored in a custom Duration field. If Odoo Timesheet module is active, entries link to crm.lead as timesheet lines.

Bilr Invoice records (number, date, amount, status, line items) do not have a direct CRM counterpart. If Odoo Sale is active, invoices map to sale.order with state='sale'. If Odoo Account is active, they map to account.move. In all cases, invoice ID, amount, and status migrate as custom fields on the linked res.partner for historical reference.

Bilr Payment records (date, amount, method, reference) link to an Invoice. In Odoo, payments belong to account.payment tied to account.move invoices. We store payment date, amount, method, and reference as custom fields on the res.partner record — actual payment objects require Odoo Account module activation.

Bilr custom properties on Client records require Odoo custom fields. Property names become field technical names prefixed x_bilr_ (e.g., x_bilr_referral_source). Field type maps per Bilr type: text→char, number→float, date→date, dropdown→selection. Odoo Studio (Enterprise) or custom module (Community) needed before import.

Matter-level custom properties migrate to crm.lead as custom fields prefixed x_bilr_matter_*. Billing-specific properties (e.g., matter rate, billing method) become Odoo custom fields on the opportunity record. Custom field creation in Odoo is a prerequisite before migration data can land correctly.

Bilr file attachments on matters and time entries re-upload to Odoo as ir.attachment records linked to the target crm.lead. If Odoo Documents app is installed, files go to documents.document for the CRM workspace. Re-upload step required — attachments are downloaded from Bilr and pushed to Odoo via API.

Bilr user accounts (staff names, email, role) match Odoo res.users by email. Active Bilr users get mapped to Odoo users with matching email; inactive accounts flagged. If Bilr roles don't map to Odoo groups, we assign to 'Sales / User' group and note the role name in a custom field.

Bilr billing rate rules (per-attorney rates, matter-type rates, discount rules) have no Odoo CRM equivalent. Odoo Sale uses pricelists for product pricing, not per-staff billing rates. We export rate rules as a CSV reference sheet for the Odoo admin to configure as product pricelist rules in Sale if needed.

Bilr trust accounting records (client trust balance, ledger entries) are legal-specific and have no Odoo CRM equivalent. These require the Odoo Accounting module for proper handling. We export trust ledger as a separate CSV for an accountant to import into Odoo Account or reconcile manually.