Migrate from Propertybase to Odoo CRM

Propertybase Company Contacts map directly to Odoo res.partner records with company_type='company'. The company name, domain, industry, employee count, and annual revenue fields translate to Odoo's name, website, industry, employees, and revenue fields respectively. Physical address, phone, and email also map to the corresponding Odoo partner fields, preserving the original address hierarchy.

Propertybase Individual Contacts (buyers, tenants) map to Odoo res.partner with company_type='person'. These records do not link to a Propertybase company; in Odoo they get parent_id=False unless a parent company is specified during migration. The SystemIsIndividual flag is used to distinguish from Company Contacts.

Propertybase's parent_company hierarchy uses the hs_parent_company_id field. In Odoo this maps to res.partner.parent_id — the parent company must be migrated first so the child record can reference it. Circular references (A parent of B, B parent of A) are flagged during the planning scan.

Propertybase Enquiries (inbound requests linked to Listings via Favorites) map to Odoo crm.lead with type='lead'. The original record type name is preserved as a crm.tag for segmentation. Enquiry status (New, Working, Unqualified, Converted) maps to Odoo's stage_id values. Additionally, a 'Source: Propertybase' tag is attached, and any linked Listing ID is stored in a custom field for reference.

Propertybase Listings have no Odoo CRM native equivalent. We create custom Char fields on crm.lead: Listing_Address, Listing_City, Listing_State, Listing_Zip, Listing_Price, Listing_Status, Listing_Agent, and Listing_ID. For brokerages with hundreds of active listings, we recommend the Odoo Real Estate app (Community module) as a future-state option; the migration plan documents the custom-field layout.

Propertybase Offers/Contracts link a Listing to a purchaser contact and carry offer_amount, offer_status, and offer_date. These map to crm.lead as opportunities (type='opportunity') with the offer_amount stored in expected_revenue, offer_status in stage_name, and the purchaser contact linked via partner_id. Listing linkage is preserved via the custom Listing_ID field.

Propertybase Favorites create a many-to-many link between Enquiries and Listings. Odoo CRM has no native equivalent for this association. We preserve the mapping as a text blob in a custom field (Propertybase_Favorite_Listings__c) for reference — your team can recreate using Odoo CRM tags or a custom Many2many field.

Propertybase activity logs (call duration, email subject, meeting date) map to Odoo mail.activity records linked to the parent res.partner or crm.lead. Original activity dates and descriptions are preserved. Propertybase's activity-type picklist maps to Odoo's activity_type_id. Attachments associated with activities are also migrated to ir.attachment, and the responsible Odoo user is assigned via the user_id field.

Propertybase files attached to Listings, Enquiries, or Contacts are downloaded from Salesforce and re-uploaded to Odoo's ir.attachment model, linked to the corresponding res.partner or crm.lead record. File size limits (Odoo default 25MB per attachment) are enforced during migration. Any files exceeding the limit are flagged for manual review.

Propertybase automation (Workflow Rules, Salesforce Flow, Process Builder) does not migrate to Odoo. These must be rebuilt in Odoo's automation tools (automated actions, server actions, CRM activities). We export your Propertybase workflow definitions as a JSON specification for your Odoo admin to reference during the rebuild phase.

Propertybase Reports and Salesforce Analytics (wave) do not migrate — their underlying data migrates, but the report definitions (filters, groupings, charts) are destination-platform constructs. Odoo reporting uses its own dashboard and spreadsheet tools. We flag the report list during discovery so your team can prioritize rebuilds.

Propertybase owner_id is resolved by matching the owner's email address to an Odoo res.users record. Unmatched owners are flagged before migration; your team either creates the Odoo user first or assigns their records to a fallback user. This prevents crm.lead records from landing without a responsible user.