Migrate from Real Estate CRM to Odoo CRM

Real Estate CRM contacts map directly to Odoo res.partner records. Contacts flagged as companies in Real Estate CRM set is_company=True on the corresponding Odoo partner record, preserving the distinction between individuals and organizations. Email, phone, address, and job title all map to equivalent Odoo partner fields, while any custom contact fields are carried over as additional ir.model.fields on the res.partner model.

Real Estate CRM company records map to Odoo res.partner with is_company=True. Company name maps to the partner name field, domain maps to website, and industry or employee count fields translate to Odoo's industry_id and employee_count where applicable. The Real Estate CRM parent-company hierarchy translates to Odoo's parent_id on res.partner, preserving the organizational structure in the target system.

Real Estate CRM property records carry listing price, address, property type, bedrooms, bathrooms, square footage, and status. Odoo has no native property model, so all these fields must be created as custom fields on crm.lead before migration. We map property.street, property.city, and property.state to the crm.lead street, city, and state fields respectively.

Real Estate CRM deals map to Odoo crm.lead records. The deal name becomes the lead name, deal amount becomes planned_revenue, and close date becomes date_closed. The crm.lead type field is set to 'opportunity' for migrated deals. The Real Estate CRM contact on the deal links to the corresponding res.partner record via the partner_id field.

Real Estate CRM pipelines map to Odoo crm.stage records scoped by crm.team. Each Real Estate CRM pipeline name becomes a crm.stage sequence within the target Odoo sales team. Stage sequence order and probability values are configured per Odoo's stage model.

Stage names such as 'Showing Scheduled', 'Offer Made', and 'Closed Won' map value-by-value to corresponding Odoo crm.stage records. We preserve stage sequence order and assign probability percentages matching the Real Estate CRM stage configuration. Stage color and legend labels are carried over as Odoo stage name and display name attributes.

Inbound leads captured in Real Estate CRM without an associated deal map to Odoo crm.lead records with type='lead'. Contact information maps to res.partner, and the lead source field maps to Odoo's source_id (linked to crm.tracking.source records). These leads are available in Odoo's pipeline kanban view for sales team qualification.

Real Estate CRM call logs and meeting records migrate as Odoo mail.message records attached to the corresponding crm.lead via the res_id and model fields. Call duration, outcome, and attendee information is preserved in the message body or as custom fields on the lead. Notes from Real Estate CRM become Odoo notes attached to the partner or lead.

Property photos, contracts, and listing documents from Real Estate CRM are re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead or res.partner. The original file names and creation timestamps are retained in the ir.attachment metadata where possible. File size limits and attachment storage location (database vs. filestore) depend on the Odoo configuration, and any oversized files are flagged for manual review before upload.

If Real Estate CRM has a dedicated Property Type object with its own fields and associations, FlitStack creates a custom field on crm.lead and maps the type name as a selection field value. Any sub-associations between Property Type and contacts are preserved as additional custom fields.

Real Estate CRM owner and agent assignments resolve to Odoo res.users by email matching. Unmatched owners are flagged before migration so your team either invites them as Odoo users or assigns records to a fallback user. The owner_id on crm.lead is set after user resolution is complete.

Real Estate CRM tags applied to contacts, companies, or deals map to Odoo crm.tag records and are linked via the tag_ids many2many field on crm.lead. Tag labels, colors, and any associated metadata are preserved where they exist in Real Estate CRM. Tags are created in Odoo during the migration if they do not already exist, ensuring consistent taxonomy across the new system.

Real Estate CRM listing status values (Active, Pending, Sold, Off Market) map to a custom selection field on crm.lead. Each status value is mapped explicitly so the Odoo sales team sees the same pipeline state after migration. Archived listings are migrated with their original status flag preserved.

Real Estate CRM lead source values such as Zillow, Referral, Website, or MLS map to Odoo crm.tracking.source records. The source_id on crm.lead links each migrated opportunity to its original lead origin. If no matching source record exists, FlitStack creates it during migration.

Real Estate CRM stores the timestamp when a deal entered each stage. Odoo's stage history is tracked differently, so we create custom datetime fields such as stage_entered_date__c on crm.lead to preserve original stage-entry timestamps for reporting continuity. These custom fields enable analysts to calculate stage durations, compare pipeline velocity, and maintain historical pipeline performance metrics after the migration.

The original Real Estate CRM record ID is stored as a char field on the crm.lead record (such as source_system_id__c) for traceability and delta-run de-duplication. This allows FlitStack to identify and update records on subsequent migration runs without creating duplicates.