Migrate from Real Properties to Odoo CRM

Real Properties contacts map to Odoo res.partner. The partner record receives name, email, phone, and address fields directly from the source. Odoo's partner_type logic (customer/supplier/contact distinction) defaults to 'contact' during migration — your admin sets the type flag afterward if needed. Because Odoo requires a value in this field, the migration supplies a default contact_type value to avoid field validation errors; the admin can adjust this to customer or supplier after the migration is complete.

Real Properties company records map to res.partner with the 'is_company' flag set to True. Odoo stores company address fields (street, city, state_id, country_id, zip) on the partner record. Parent-child relationships between companies in Real Properties map to Odoo's parent_id on res.partner, preserving any corporate hierarchy present in the source data. The migration tool handles both flat and nested company structures through recursive parent lookups during the partner creation phase.

Real Properties links each contact to one primary company. In Odoo, the contact's parent_id is set to the mapped company partner. Odoo's address_ids on the company partner hold multiple address records; the primary company is set as parent_id for query and reporting consistency.

Real Properties deals map to Odoo crm.lead records with type='opportunity'. The lead's name maps to Odoo's name field, expected revenue to planned_revenue, and close date to date_closed. Stage mapping uses a value_map from the source stage names to Odoo stage_id records.

If Real Properties distinguishes early-stage leads from closed deals, we split them: leads without a deal value or close date become Odoo crm.lead with type='lead'; deals with a value and close date become type='opportunity'. This preserves pipeline segmentation that Real Properties manages through separate record states.

Real Properties pipeline stages map to Odoo crm.stage records scoped to a crm.team. If Real Properties has multiple pipelines, we create a corresponding number of crm.team records in Odoo, each with its own stage sequence. Probability and forecast_category from Real Properties stage settings map to Odoo's probability and legend_priority fields.

Real Properties property records (address, type, status, owner, assessed value) have no Odoo CRM native equivalent. We create custom fields on res.partner or crm.lead — property_address__c, property_type__c, property_status__c, property_owner_id__c — to preserve the data. Alternatively, if your team uses Odoo Sales, property records can map to product.template; we surface both options in the migration plan for your decision.

Real Properties activity logs (calls, meetings, notes) with timestamps and owner information map to Odoo mail.activity records. The res_model is set to 'crm.lead' or 'res.partner' and res_id points to the migrated parent record. activity_type_id maps the activity category (call, meeting, note) to the corresponding Odoo activity type.

Real Properties user records resolve to Odoo res.users by email match. Unmatched owners are flagged before migration — your team either creates Odoo user accounts for them first or assigns their records to a fallback user. The migration does not create Odoo users autonomously.

Real Properties file attachments associated with contacts, companies, or deals migrate to Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. File content is base64-encoded and inserted via the Odoo API. Odoo's attachment storage limit applies (default 25MB per file).

Real Properties custom fields not present in the standard object schema are created as Odoo custom fields (ir.model.fields with custom=True) on the appropriate model before data loads. Field types are mapped: text to char/text, number fields to float or integer, date fields to date, and pick-lists to selection fields with value mapping.

If Real Properties classifies properties by type (residential, commercial, industrial, land), we create a property_type__c selection field on the relevant Odoo model and map source values one-by-one. Custom values not in the Odoo selection list are added before migration runs.