Migrate from Aderant Milana to Odoo CRM

Milana attorney records map to Odoo crm.lead with type='lead'. The attorney's name, email, phone, and bar number migrate as custom fields on crm.lead. Owner assignment resolves by email match against Odoo res.users. If an attorney email does not match an existing Odoo user, we create a pending user record for activation.

Milana client records map to Odoo res.partner (contact). Client company name maps to partner_name, individual name maps to name. Email and phone migrate as direct fields. Client matter history preserved as a custom many2many field. We also map the client's primary address to the partner's street and city fields.

Milana matters become Odoo crm.opportunity records. Matter number maps to opportunity name with matter type prefix. Matter status (Open/Closed) maps to stage — 'Open' routes to Odoo Qualified stage, 'Closed' routes to Won or Lost based on disposition. We preserve the original matter open date as the opportunity's create_date.

Odoo has no native matter-type concept. Milana matter classifications (e.g., Litigation, Corporate, Real Estate) migrate as a custom selection field Matter_Type__c on crm.opportunity so your team can filter pipelines by legal work type. We also add a corresponding dropdown option list in Odoo Studio to keep the selection consistent.

Milana court deadlines and calendar entries map to Odoo calendar.event records. Start date and stop date migrate with original timestamps. Reminder settings default to 1 day before; your admin can adjust in Odoo calendar settings. If a deadline spans multiple days, we create separate all-day events for each day.

Filing-related calendar entries map to Odoo crm.activity with activity_type='Legal Filing'. The filing deadline date and responsible attorney link migrate so Odoo activities show the owner assignment. We also map the filing description to the activity note field, preserving any attached instructions or references.

Milana documents attached to matters re-upload to Odoo ir.attachment linked to the corresponding crm.opportunity. File size limits: Odoo Community default 25MB per file. Documents over 25MB are flagged for chunked upload. We also verify file integrity by comparing MD5 checksums before and after the upload process.

Milana's court rules library (the core legal compliance feature) has no Odoo CRM equivalent. Rules-based deadline calculation must be rebuilt in Odoo using custom calendar rules or a third-party legal calendar integration. We recommend documenting each jurisdiction's rule set during the audit for accurate rebuilding.

Milana attorney billing rates and timekeeping rules do not map to Odoo CRM. These must be rebuilt in Odoo using the product/pricelist model or the Odoo Timesheet app if your plan includes it. We provide a rate-table export template with service codes, effective dates, and billing tiers for straightforward import.

Opposing counsel contacts merge with the general Milana Contact pool and map to res.partner records. A custom field Opposing_Counsel__c = True flags these contacts so Odoo users can filter the partner list. We also set a default contact type of 'opposing_counsel' on these partner records for consistency.

Milana user accounts resolve by email match to Odoo res.users. Unmatched attorneys are flagged before migration — your team either creates Odoo users first or assigns records to a fallback administrator. We provide a CSV list of unmatched emails for rapid user creation in Odoo's user management panel.

Milana firm-specific custom matter fields (e.g., Jury Trial Demand, Case Judge, Statute of Limitations) create Odoo custom fields on crm.opportunity using the field name as label and appropriate data type (char, date, selection). We also add help text to each field describing the expected data format and example values.

Milana matter notes migrate as Odoo mail.message records attached to the crm.opportunity. Original note text and create date preserved. Rich-text formatting is retained where the export format supports it. If a note includes embedded images, we store them as binary attachments and reference them in the message body.