Migrate from CRM for real estate to Odoo CRM

CRM for Real Estate contacts map to Odoo res.partner records. Since Odoo uses res.partner as a unified model for both individuals and organizations, a contact record with a company association sets parent_id to the corresponding company partner record. Contacts without a company land as individual partner records. Email serves as the unique external ID for de-duplication.

CRM for Real Estate companies map to res.partner records with is_company=True. Odoo's parent_id field handles multi-office hierarchies (parent company / branch office) that CRM for Real Estate may store as separate company records. Child company records reference the parent via parent_id. Industry, annual revenue, and employee count become custom fields on the company partner record.

CRM for Real Estate property records — which contain address, listing price, MLS number, property type, bedrooms, bathrooms, and status — have no native equivalent in Odoo CRM. FlitStack splits the property record into multiple custom Char, Float, and Selection fields on crm.lead (x_property_address__c, x_listing_price__c, x_mls_number__c, x_property_type__c, x_bedrooms__c, x_bathrooms__c, x_listing_status__c). Each deal in CRM for Real Estate links to one property; that property becomes a group of custom fields on the migrated crm.lead.

CRM for Real Estate deals (transactions) map to Odoo crm.lead records. The crm.lead type field is set to 'opportunity' for active transactions. Deal amount becomes x_transaction_value__c as a custom Float field. The property address from the linked CRM for Real Estate Property object becomes x_property_address__c on the lead. stage_id maps from the CRM for Real Estate pipeline stage to the Odoo stage_name pick-list.

CRM for Real Estate transaction stages (New, Showing Scheduled, Offer Made, Under Contract, Inspection, Closing, Closed Won, Closed Lost) map to Odoo CRM stage records via a value-mapping table. Each stage gets a stage_id GUID from Odoo after your admin creates the stages in Settings > CRM > Stages. Probability and team assignment are preserved per stage. Custom real-estate stages that do not match Odoo's default set require pre-migration stage creation in Odoo.

CRM for Real Estate stores listing agent, buyer agent, and showing agent as separate fields on each deal. Odoo has no native agent object. FlitStack maps agent email to res.partner records and stores agent references as x_listing_agent_id__c (Many2one to res.partner), x_buyer_agent_id__c, and x_showing_agent_id__c custom fields on crm.lead. Agents not found in Odoo by email are flagged before migration for admin creation.

CRM for Real Estate logged calls, emails, meetings, and notes become Odoo mail.message records attached to the corresponding res.partner or crm.lead via model and res_id. Meeting records with start/end times become calendar.event records linked to the lead or partner. Original timestamps, owners (by email match to res.users), and body content are preserved. Call disposition notes migrate as message body text.

CRM for Real Estate file attachments on contacts, companies, or deals re-upload to Odoo as ir.attachment records linked to the migrated res.partner or crm.lead via res_model and res_id. Binary file content is stored in Odoo's filestore. File size limits (default 25MB per file in Odoo) are enforced; oversized files are flagged before migration. Inline images in notes are downloaded and rehosted in Odoo's attachment storage.

CRM for Real Estate custom fields added to Property or Deal objects — such as HOA fees, lot size, year built, or showing instructions — become custom fields on crm.lead with type-appropriate Odoo field definitions (Float for monetary values, Char for text, Date for dates). The migration plan lists every custom field before import so your Odoo admin can pre-create them in Settings > Technical > Custom Fields.

CRM for Real Estate deal owners and contact owners are resolved by email match against Odoo res.users records. Unmatched owners are flagged before migration runs — your Odoo admin either creates the user in Odoo first or assigns records to a fallback user. No record lands in Odoo without a valid user_id on the crm.lead or res.partner owner field.