Migrate from FilePro to Odoo CRM

FilePro clients map to Odoo res.partner records. The partner's address, phone, and email fields map directly. For law firms, clients are typically stored as companies (type='company') rather than individuals — the is_company flag is set based on FilePro's client-type indicator.

FilePro contact records within a client matter (e.g., opposing counsel, referrer contacts, co-counsel) map to res.partner with type='contact' and a parent_id linking to the primary client partner. Name fields split into firstname/lastname using Odoo's name_split logic. If FilePro stores only a full-name field without a separator, the migration applies standard name parsing heuristics to extract the components correctly.

FilePro matters are the primary work units — they map to Odoo crm.lead records representing opportunities or cases. The matter description becomes the lead description field. Matter status (open, closed, billed) maps to crm.lead stage_id through a value-mapping defined during discovery.

Each FilePro UDF requires an Odoo custom field to be created on the appropriate model before data loads. String-type UDFs become char or text fields, numeric UDFs become float or integer, date UDFs become date fields, and pick-list UDFs become selection fields with value-mapping entries.

FilePro time entries map to Odoo account.analytic.line records linked to the matter's analytic account. Unit_amount carries the duration in hours, product_id links to the service item, and staff initials resolve to Odoo res.users via the operator mapping table created during discovery.

FilePro document attachments linked to matters are downloaded and re-uploaded to Odoo's ir_attachment table via the /web/binary/attachment XML-RPC API. Each file's binary content transfers as base64-encoded data through the datas field. The res_model and res_id fields link each attachment to the corresponding crm.lead record representing the matter. FilePro file metadata such as creation dates and author information is preserved in the attachment's create_date and create_uid fields during upload.

FilePro invoice records map to Odoo account.move with move_type='out_invoice'. Each invoice header creates one account.move record, preserving the invoice number, date, and partner_id from FilePro. Line items generate account.move.line entries linked to the matter's analytic account for cost tracking. Tax amounts and discounts from FilePro map to appropriate tax and analytic fields on the line entries. Trust account transactions from FilePro's billing system map to separate journal entries on the trust account journal configured in Odoo Accounting.

FilePro trust ledger entries (receipts, disbursements, transfers) map to Odoo account.move records on the trust account journal configured in Odoo Accounting. Receipt transactions create journal entries that debit the trust receivable account and credit the appropriate client-specific trust liability account. Disbursement transactions reverse this pattern with debits to the trust payable account and credits to the operating account. Each transaction maps to the firm's chart of accounts entries established during Odoo schema setup. The matter_id on each entry links to the corresponding analytic account for client-level trust balance reporting.

FilePro operator IDs map to Odoo res.users records. Matching is performed by email address where available in FilePro staff records, or by full name if email is absent. Staff without an identifiable match are flagged as 'Unresolved Owner' for manual assignment before the migration commits.

FilePro calendar entries linked to matters map to Odoo calendar.event records. The start datetime and stop datetime fields carry over directly from FilePro, preserving the original appointment duration and timing. The event's res_id links to the corresponding crm.lead record representing the matter, and the res_model field is set to 'crm.lead' to establish the relationship. Staff assignment uses the mapped res.users record from the operator mapping table created during discovery. For all-day events or multi-day appointments, the allday flag and start_date/stop_date fields are set appropriately in Odoo.