Migrate from Traffic Ticket CRM to Odoo CRM

Traffic Ticket CRM Client records map directly to Odoo res.partner. The Client's address, phone, email, and attorney assignment fields migrate as standard res.partner fields. If a Client has multiple open Cases in Traffic Ticket CRM, all Cases link to the same res.partner ID in Odoo.

Traffic Ticket CRM stores contact-level records (Client contacts, opposing counsel, court clerks) in a separate Contact Manager object. These merge into res.partner alongside Client records — FlitStack deduplicates by email address and creates one res.partner per unique contact. For contacts with duplicate email addresses, FlitStack performs additional name and company matching to ensure accurate consolidation without losing role-specific information stored in the Contact Manager.

Each Traffic Ticket CRM Case becomes an Odoo crm.lead record. A custom selection field (Case_Type__c equivalent in Odoo: x_case_type) stores the practice area value (Traffic Ticket, Criminal Defense, Mass Tort). The Case status (Open, Closed, Dismissed) maps to crm.lead stage names.

Traffic Ticket CRM case statuses (Open, Pending Court Date, Under Review, Dismissed, Pleaded, Paid) map one-to-one to Odoo crm.lead stage records. We create stage records in Odoo matching the source statuses and preserve any status-change timestamps as stage-history notes. Each stage is assigned a sequence number reflecting the Traffic Ticket CRM workflow order so the case pipeline in Odoo visually matches your original process.

Traffic Ticket CRM court date records map to Odoo calendar.event entries with event type = 'court_hearing'. The event is linked to the corresponding crm.lead via the res_id/res_model fields. Original hearing time, courtroom, and judge name migrate as custom event description fields.

Traffic Ticket CRM document scans (PDFs, images of citations, police reports) attach to their parent Case record. FlitStack downloads each file from Traffic Ticket CRM's storage and re-uploads to Odoo's ir.attachment table, linking each attachment to the corresponding crm.lead record using res_model='crm.lead' and res_id matching the Odoo lead ID.

Traffic Ticket CRM invoice records map to Odoo account.move entries with move_type='out_invoice'. Each invoice line links to an Odoo product (a generic 'Legal Services' product is created as a placeholder). Court costs and filing fees from Traffic Ticket CRM's billing become separate invoice lines with distinct account codes.

Traffic Ticket CRM trust accounting (client funds held in escrow) has no native Odoo equivalent. We preserve trust ledger entries as account.move records in a dedicated Trust Journal that your accountant configures. Full trust reconciliation logic must be rebuilt in Odoo Accounting.

Traffic Ticket CRM Bonding status (Bondsman, Cash Bond, Surety Bond, Released) migrates as a custom selection field on crm.lead: x_bond_status. Bond amount migrates as x_bond_amount (monetary field). Odoo does not have a native bonding construct — these are informational fields for attorney reference.

Traffic Ticket CRM's court-data-based lead source flag migrates as a custom selection field x_traffic_data_source on crm.lead. Values (Court Feed, Client Referral, Online Intake, Mailer Response) are preserved verbatim. The automated lead-pull mechanism must be rebuilt in Odoo via a third-party data connector or custom API job.

Traffic Ticket CRM mailer campaign records and response tracking are consolidated into a custom field x_mailer_campaign_id on crm.lead. Campaign name and response date are stored as text and date fields. Odoo Email Marketing handles future campaigns — the historical campaign IDs serve as reference data only.

Traffic Ticket CRM attorney and staff user accounts are resolved by email match against Odoo res.users. Unmatched users are flagged before migration — your Odoo admin either creates the user account first or assigns records to a fallback attorney in the sales team.