Migrate from Leadrat CRM for Real Estate to Odoo CRM

Leadrat Lead maps to Odoo crm.lead — both track name, email, phone, source, and stage. Odoo's crm.lead can be a pure lead or flagged as an opportunity via the 'opp' boolean field. The mapping preserves the lead's original create date in a custom field since Odoo's create_date reflects migration time.

Leadrat Contact maps to Odoo res.partner with contact_type='contact'. Odoo merges company and person into one model — Leadrat's company_name text field becomes res.partner.parent_id pointing to a res.partner with contact_type='company'. Unlinked Leadrat contacts without a company get a synthetic parent company partner.

Leadrat Property maps to Odoo estate.property if Odoo Estate module is installed. If not, property data migrates as custom fields on crm.lead (property_type, property_price, property_status) or as linked res.partner records with a custom property_type field. The decision is made during scoping based on whether the team tracks listings as prospects or inventory.

Leadrat Deal transforms into Odoo crm.lead with opp=True flag and stage_id aligned to the target Odoo stage. The deal's monetary value becomes crm.lead.planned_revenue, and associated Leadrat contacts are linked via crm.lead.partner_id. These partner links enable Opportunity Partner Lines for quotation generation in Odoo's sale module. Original deal create_date is stored in a custom field to preserve historical context.

Each Leadrat pipeline stage (e.g., New Lead, Site Visit Scheduled, Negotiation, Booked) maps to a corresponding Odoo crm.stage in the team's stage_ids. Stage sequence order is preserved. Custom stage properties like probability or fold_status are set per Odoo stage configuration.

Leadrat follow-up tasks map to Odoo mail.activity records with activity_type_id (call, meeting, email, todo), date_deadline matching the original scheduled date, and user_id matching the assigned agent. Activity description maps to mail.activity.note. The parent res.partner or crm.lead id is stored in res_id/res_model.

Leadrat team members map to Odoo res.users by email match. Leadrat's team structure becomes Odoo crm.team records, and team membership is set via crm.team.member_ids. If a Leadrat user has no matching Odoo email, they are flagged for admin creation or owner reassignment.

Leadrat custom lead fields (e.g., portal_source, budget_range, property_type_preference) are created as custom fields on Odoo's crm.lead model via Studio or a custom module. Field type mapping: Leadrat text → char, number → float, picklist → selection, date → date. Custom field IDs are stored in the migration audit log for traceability.

Leadrat lead_source values (Organic, Portal, Referral, Facebook, Property Portal) map to Odoo utm.source records. Each unique Leadrat source becomes a utm.source record in Odoo. If a source name does not already exist in Odoo, it is created during migration. The crm.lead.source_id field links the migrated lead to its UTM source for reporting continuity.

Leadrat file attachments on leads, contacts, or properties are downloaded and re-uploaded to Odoo ir.attachment. Each file is stored with res_model='crm.lead' or 'res.partner' and res_id pointing to the migrated target record. Original filename, create date, and file size are preserved in Odoo's ir.attachment fields. Odoo's attachment storage size limit applies (default 25MB per file).

Leadrat lead notes migrate to Odoo mail.message records with message_type='comment'. The original note body and create date are preserved in the mail.message body and create_date fields. Notes attached to Leadrat leads are posted on the crm.lead record in Odoo; notes attached to contacts are posted on the res.partner record, maintaining the full conversation history.

Leadrat workflow rules (if/then triggers for task creation, stage changes, email alerts) have no Odoo CRM equivalent in base Odoo. These must be rebuilt using Odoo Studio Automations, Server Actions, or base_action_rule criteria. FlitStack exports the Leadrat rule definitions as a JSON reference document for your Odoo admin to re-implement.