Migrate from Captorra to Odoo CRM

Captorra's lead record maps 1:1 to Odoo's crm.lead model. The crm.lead model handles both inbound leads and converted opportunities, so Captorra leads land as Odoo leads by default. Any lead-to-matter conversion logic in Captorra maps to Odoo's lead-to-opportunity action. All standard lead fields such as name, email, phone, and address are transferred directly, preserving original timestamps and owner assignments.

Captorra stores contact details (name, email, phone, address) as fields on the lead record. These extract to a res.partner record in Odoo with partner_id populated on the crm.lead. Odoo's crm.lead.name defaults to the partner's display name if only partner_id is set.

Captorra's company field on a lead maps to a res.partner record with company_type='company'. Odoo resolves the parent-partner relationship automatically when partner_id is set on the contact-level partner record. Multiple leads from the same Captorra company consolidate to one Odoo company partner.

Captorra's custom intake-status values (e.g., New Lead, Qualified, Intake Complete, Closed) map to Odoo crm.stage records. Each Captorra pipeline maps to one Odoo crm.team's stage set. Stage display order and probability weights re-applied based on Odoo's stage configuration per team.

Captorra referral attribution (referring attorney, partner firm, or channel) maps to an Odoo res.partner record with type='delivery' or stored as a Referral_Source__c char field on crm.lead. The mapping approach depends on whether the firm wants referral contacts visible in Odoo's partner list or kept as a read-only field on the lead.

Captorra per-organization custom fields (e.g., Accident_Type, Insurance_Provider, Statute_of_Limitations) require Odoo custom field creation before migration. FlitStack reads the Captorra field definitions during discovery and generates Odoo field creation YAML for admin approval. Field types map: text→char/text, picklist→selection, date→date, number→float/integer. The generated YAML can be applied via Odoo Studio or directly in developer mode, and the fields become part of the crm.lead model for subsequent data loading.

Captorra's case reference number stores as a custom char field on crm.lead. If the firm also uses Odoo's project management app, case matters can map to project.project records linked via crm.lead.project_id. FlitStack recommends the custom field approach for law firms that only need CRM-level matter tracking.

Captorra engagement logs (call recordings, email threads, note bodies) map to Odoo mail.message records linked to the crm.lead. Odoo's mail.thread mechanism displays these in the lead's chatter. Original timestamps and owner IDs preserved. Call duration and outcome stored in mail.message.fields or custom fields on the message.

Captorra's assigned user resolved by email match to Odoo res.users records. Unmatched owners flagged before migration. Unassigned Captorra leads land on a fallback Odoo user (configurable). Odoo's crm.lead.user_id field holds the owner reference. The fallback user is set in Odoo's CRM settings, and any unmatched owners are listed in a pre‑flight report for the admin to resolve prior to the final load.

Captorra original create_date migrates as crm.lead.create_date (set at insert time). Captorra's last_modified timestamp maps to crm.lead.write_date or a custom Original_Modified_Date__c field for reporting continuity. Odoo's native audit fields capture the migration run date separately. The custom field, if created, stores the original modification timestamp to support historical reporting without altering Odoo's internal write_date.

Captorra's internal record ID stored as a custom field on crm.lead for traceability and delta-run de-duplication. The x_studio prefix applies when Odoo Studio creates the field; the field name is configurable per deployment. This field allows FlitStack to match source records during subsequent delta imports, preventing duplicate entries and enabling audit trails across migration cycles.

Captorra file attachments on leads (intake documents, uploaded forms, referral letters) download and re-upload to Odoo's ir.attachment model linked to the crm.lead record. Odoo's document management app enhances this if installed; otherwise files attach directly to the lead record. All attachments retain original filenames and MIME types, and the ir.attachment's create_date reflects the upload time in Odoo.