Migrate from eBrief Ready to Odoo CRM

Each eBrief Ready Matter maps to one Odoo crm.lead record. Matter name becomes crm.lead.name, case number maps to a custom field x_case_number, and jurisdiction maps to x_jurisdiction. eBrief Ready matter IDs are preserved in x_source_matter_id for delta-run de-duplication. Pipeline stages in Odoo are configured to represent matter lifecycle stages (Instructed, Discovery, Hearing, Judgment) rather than nested folders.

eBrief Ready Party records with role type 'Contact' or 'Client' map to Odoo res.partner with partner_latitude type 'contact'. Full name splits into firstname and lastname fields. Email maps directly to email field. Phone and mobile map to phone and mobile fields respectively. Party role labels (Opposing Counsel, Expert Witness, Barrister) are preserved as a custom field x_party_role on res.partner since Odoo does not have native multi-role party labels.

eBrief Ready Party records with role type 'Firm' or 'Organisation' map to Odoo res.partner with partner_latitude type 'company'. Company name maps to name field. Firm address maps to street, city, country fields. These records serve as the commercial entity for associated individual contact records and are linked via the child_ids relationship on the company partner.

eBrief Ready PDF documents and court bundle files are downloaded and re-uploaded to Odoo ir.attachment with res_model='crm.lead' and res_id pointing to the migrated crm.lead record. Original filenames and create dates are preserved in name and create_date fields. File size limits apply per Odoo configuration; large bundles may require chunking. Inline annotations are not extracted as separate files—annotation text migrates separately as mail.message records.

eBrief Ready annotations and highlights on documents are extracted as text snippets with source document reference and page number. These migrate as Odoo mail.message records with model='crm.lead' and message_type='comment', attached to the corresponding lead. Original annotation timestamps and author information map to date and author fields. This preserves the collaboration history without native annotation rendering in Odoo.

eBrief Ready tags applied to matters map to Odoo crm.tag records. Tag names transfer directly. Many-to-many relationship between crm.lead and crm.tag is preserved via the crm_lead_tag_rel linking table. If eBrief Ready uses custom tag categories, these may require Odoo custom tag groups configured in CRM > Tags > Categories.

eBrief Ready chronology tool generates dated event entries (filings, correspondence, orders) that have no native Odoo equivalent. These migrate as mail.message records on the crm.lead with message_type='notification' and subtype='mail.mt_note', plus a custom field x_chronology_date to preserve the original event date for reporting continuity.

eBrief Ready nested folder structure (e.g., Pleadings > Replies > Exhibits > Tab 1) represents document organization that Odoo does not model natively. We map the top-level folder as the Odoo pipeline name, second-level folders as crm.stage stages, and sub-folders as document tags on ir.attachment records. This preserves document location context without Odoo folder objects (which Odoo does not have in CRM).

eBrief Ready matter assignments to barristers or responsible lawyers map by email address match to Odoo res.users records. Unmatched owners are flagged as Odoo res.partner records with x_is_unmatched_owner=True for your admin to reassign post-migration. Odoo's crm.lead.user_id field holds the responsible user; if no match exists, the lead lands in the Odoo Sales Team's unassigned queue.

eBrief Ready user accounts with email, name, and role are mapped to Odoo res.users by email. Passwords do not transfer—users receive Odoo onboarding invitations. User permissions (eBrief Ready owner vs. full user vs. viewer) map to Odoo groups: Administration > User types for admin access, CRM > User for standard sales access. eBrief Ready Pro feature access does not translate to Odoo access rights.

eBrief Ready AI-powered document classification (auto-suggested document name, date, destination folder) generates metadata that has no Odoo equivalent. We preserve this as custom char fields on crm.lead (x_classification_suggestion, x_auto_folder_suggestion) as reference data. The AI classification logic itself cannot migrate and must be rebuilt using Odoo AI Studio or an external integration.

eBrief Ready workflows and automation rules (document classification triggers, sharing rules, follow-up reminders) do not have a migration path to Odoo. These must be rebuilt in Odoo using Studio automations, ir.actions.server, or base.automation. We export eBrief Ready workflow definitions as a reference document for your Odoo admin to use during reconstruction.