Migrate from The Real Estate CRM to Odoo CRM

Direct map. res.partner stores both individual contacts and companies in Odoo. Individual contacts require partner category 'Individual'; company contacts require partner category 'Company'. The Real Estate CRM contact's primary company is set via parent_id on res.partner — additional company associations use Odoo's partner relations (res.partner.relation) model.

Direct map to res.partner with is_company=True. The Real Estate CRM company address, phone, domain, and industry fields map to res.partner street, phone, website, and industry fields respectively. Parent-company hierarchies map to res.partner parent_id. If the company has a website, Odoo stores it in the website field. The industry field references res.partner.industry; unmapped industry values are created on import. Multi-location hierarchies represented by linking partner records to the parent via parent_id.

Deals in The Real Estate CRM become crm.lead records with type='opportunity'. Odoo's crm.lead model handles both leads and opportunities in one table — the type field distinguishes them. Deal pipeline and stage map to crm.lead stage_id (crm.stage record) keyed by the Odoo sales team pipeline.

Odoo organizes pipelines by crm.team (sales team) and stages within each team via crm.stage. Each crm.team has its own Kanban stage sequence. The Real Estate CRM pipeline maps to a specific crm.team in Odoo; pipeline stages map to crm.stage records ordered by sequence within that team.

Stage names from The Real Estate CRM are mapped value-by-value to Odoo crm.stage records. Odoo stages have a probability field (percentage) and a stopour flag that must be set per stage. Stage display names in Odoo's Kanban are set on the crm.stage.name field. Stage sequence within the pipeline is set by the sequence integer on crm.stage.

The Real Estate CRM listing data — listing ID, property address, property type, listing price, status, bedrooms, bathrooms, square footage — maps to Odoo's estate.property model if the Real Estate module is installed. If not, all listing fields migrate as custom fields on crm.lead or res.partner. The Real Estate module must be installed and configured before the property data loads.

The Real Estate CRM association labels between contacts and deals (Buyer, Seller, Tenant, Agent) map to Odoo's res.partner.relation model with a typed relation (type_id). Each association label type requires a res.partner.relation.type record to be defined in Odoo before migration. If the Real Estate module is present, listing-related roles may map to its partner roles.

Phone calls, emails, and meetings from The Real Estate CRM map to Odoo's mail.activity records on the related crm.lead or res.partner. Odoo requires an activity type (mail.activity.type) to be defined for each activity category. Original timestamps and owner (user_id) are preserved. Email content becomes mail.message records with mail.activity.res_id linking to the parent record.

Notes and file attachments from The Real Estate CRM migrate to Odoo's ir.attachment table. Each attachment is linked to the target record (res_model='crm.lead' or 'res.partner') with res_id pointing to the record ID. Text notes also create mail.message records for Odoo's chatter thread visibility. File size limits on the Odoo instance apply; attachments over 25MB require chunked re-upload.

The Real Estate CRM custom objects (such as custom property types, showing records, or offer tracking) map to either a new custom Odoo model (created via Settings > Technical > Models) or as additional custom fields on crm.lead. If a new model is required, FlitStack creates the model definition and migrates records via XML-RPC after the model is registered.

The Real Estate CRM owner IDs (agent assignments) resolve by email match against Odoo res.users records. Unmatched owners are flagged before migration — either inviting the agent to Odoo first or assigning their records to a fallback res.users record. No crm.lead lands without a user_id owner in Odoo.

FlitStack does not migrate automations, action plans, drip sequences, or email templates from The Real Estate CRM. These are platform-native logic with no export format compatible with Odoo. We export workflow definitions as a structured reference document so your Odoo administrator can rebuild them using Odoo's Automated Actions (base.automation) and CRM pipeline action rules.