Migrate from LawPracticeZA to Odoo CRM

Audit LawPracticeZA data via API and manual export

FlitStack connects to the LawPracticeZA XML-RPC API to pull invoices, trust transactions, and fee postings. For entity types not exposed by the API (matters, clients if partially covered), we extract via CSV from the LawPracticeZA UI. The audit report lists every object, record count, and custom field discovered, forming the basis of the migration scope document and Odoo field-creation plan.

Create Odoo schema — custom fields, groups, trust journal

Before any data loads, FlitStack creates the required custom fields on crm.lead (x_lpza_matter_ref__c, x_jurisdiction__c, x_practice_area__c, x_billing_rate__c) and on res.partner (x_company_reg_no__c, x_trust_balance__c) as identified during the audit. It also sets up a dedicated trust accounting journal in Odoo's accounting module and configures res.groups to replicate LawPracticeZA zone permissions. The Odoo administrator reviews and approves the schema, ensuring that all custom fields and groups are in place before the migration run begins.

Resolve fee earners and create Odoo users

LawPracticeZA fee earners are matched to Odoo res.users by email address. FlitStack generates a user‑match report that lists which fee earners already have Odoo accounts, which need new accounts created, and which have no matching email at all. Firms create any missing Odoo user accounts before the migration run, ensuring that every matter links to a valid user_id rather than remaining unassigned. This pre‑flight step prevents orphaned records and speeds up the subsequent data load.

Migrate clients to res.partner first

Client records are loaded into Odoo res.partner before any matters or invoices so that foreign‑key resolution works correctly. After the client load, FlitStack runs a validation pass to confirm that all emails are unique, no duplicate partners were created, and every custom partner field received a value. Any client that had no associated matter in LawPracticeZA migrates as a plain contact record, preserving its name, address, and contact details for future use.

Migrate matters to crm.lead with custom field enrichment

Matters are loaded into Odoo crm.lead with partner_id pointing to the resolved res.partner record and user_id pointing to the matched fee earner. The original matter reference, jurisdiction, and practice area are written into their respective custom fields on the lead. FlitStack then runs a field‑level diff that compares the source matter count, stage distribution, and date ranges against the Odoo crm.lead record count and field‑population rate, highlighting any gaps for manual review before final sign‑off.

Load invoices, WIP entries, and trust transactions

Invoice records are loaded into account.move using the partner_id resolved during the client migration, and WIP entries are loaded into account.analytic.line linked to the matter’s analytic account. Trust transactions are directed into the dedicated trust journal created earlier. FlitStack produces a reconciliation report that contrasts LawPracticeZA invoice totals and trust balances with Odoo account.move totals and partner trust balances, helping to spot any discrepancies before the delta‑pickup window opens.

Delta-pickup window and cutover validation

A delta‑pickup window of 24–48 hours after the full migration captures any records created or modified in LawPracticeZA during the cut‑over period. FlitStack generates a final reconciliation report that compares source and destination record counts, amounts, and stage distributions, while an audit log records every operation performed. If reconciliation identifies discrepancies that exceed the defined tolerance threshold, a one‑click rollback restores the Odoo environment to its pre‑migration state, minimizing risk and ensuring data integrity.