Migrate from Lead Docket to Odoo CRM

Lead Docket leads map directly to Odoo crm.lead records. The Odoo crm.lead model stores both pre-conversion leads and post-conversion opportunities in one object differentiated by the type and stage_id fields. Original Lead Docket create dates are preserved as Original_Create_Date__c (via x_ prefix field) because Odoo's create_date reflects migration insertion time.

Lead Docket contacts migrate to Odoo res.partner records. In Odoo, res.partner is the unified contact/person record used across CRM, Sales, and Accounting modules. Linked contacts are inserted before leads so crm.lead.partner_id foreign keys resolve correctly during migration sequencing. Email addresses serve as the deduplication key, and any duplicate contacts detected are merged into a single res.partner record with multiple x_lead_docket_contact_id references preserved for traceability.

Lead Docket's 11 default lead statuses (New, Attempted Contact, Bad Contact Info, Consultation Scheduled, Consultation Completed, Signed Up, Not Interested, Lost Lead, etc.) map value-by-value to Odoo crm.stage records within the default CRM pipeline. Custom account-specific statuses require stage creation in Odoo before value mapping runs.

Lead Docket case types — the legal-matter classification that drives case-type–dependent custom fields — have no Odoo CRM native equivalent. FlitStack creates a custom Selection field (x_case_type) on crm.lead and migrates each lead's case type as a selection value. If Odoo Enterprise with Studio is available, the field can be built there; otherwise it requires module definition or direct database field insertion.

Every Lead Docket lead custom field (dropdown, text, date, currency, etc.) is recreated in Odoo using the x_ field-name prefix convention. Field type is preserved — text fields become Char, date fields become Date, currency fields become Monetary (linked to res.currency). Multi-select dropdowns become Char with comma-delimited values unless Odoo custom.selection is configured.

Lead Docket contact custom fields — tied to a contact record rather than a lead — migrate as x_ custom fields on Odoo's res.partner model. This preserves the per-contact metadata (e.g., referral source, intake channel) that Lead Docket allows clients to attach directly to contacts. Note: Lead Docket contact custom fields cannot be made dependent on case type because they are contact-level, not lead-level.

Lead Docket source rules automate marketing source selection when inbound leads arrive. This Odoo automation has no direct equivalent. We preserve the source rule output (the selected marketing source) as a custom Char field x_source_rule on crm.lead for reporting continuity. The automation logic itself must be rebuilt in Odoo using Server Actions or Odoo Workflow triggered on lead creation.

Lead Docket attorney rotation distributes incoming leads fairly among attorneys based on configurable rules. In Odoo CRM, team-based lead assignment is managed via crm.team membership. FlitStack maps each Lead Docket assigned attorney (stored as a user reference) to the matching Odoo user by email lookup and preserves the pre-assignment as x_original_attorney_id. The rotation algorithm itself must be re-implemented as an Odoo Server Action or Assignment Rules on crm.team.

Lead Docket file attachments on leads and contacts are downloaded and re-uploaded to Odoo's ir.attachment model, linked to the corresponding crm.lead or res.partner record. Odoo stores attachments in its filestore; large files (over 25MB per file) are handled in chunks. Inline images embedded in Lead Docket notes are extracted and rehosted as ir.attachment records linked to the note body.

Lead Docket's 1:1 contact-to-lead association becomes crm.lead.partner_id pointing to the migrated res.partner record. Lead Docket allows each lead to have one primary contact; this maps cleanly to Odoo's partner_id link. N:1 associations from Lead Docket (if any lead has multiple contacts) are handled by storing the primary contact as partner_id and additional contacts as a Char field x_secondary_contact_ref for manual resolution in Odoo.

Lead Docket integrates with Filevine for case management and Vinesign for document signing. Odoo has no native Filevine connector. These integrations must be disconnected before migration and rebuilt separately after go-live. FlitStack preserves the Filevine case reference stored in Lead Docket's custom fields as x_filevine_ref for post-migration reconnection.

Lead Docket automations (a paid add-on) trigger status changes, lead form submissions, and Filevine/Vinesign sends based on lead events. Each automation is audited as a JSON definition before migration. FlitStack exports the automation configuration as a rebuild reference document so your Odoo admin can recreate equivalent Server Actions on crm.lead triggered by the same events.