Migrate from Property Raptor to Odoo CRM

Property Raptor Contacts migrate as Odoo res.partner records. Odoo's name field holds the full contact name split from Property Raptor's firstname and lastname fields. Partner type (customer, instructor, etc.) is set via Odoo's is_customer flag based on the contact's role in Property Raptor.

Property Raptor Companies migrate as res.partner records with is_company=True. Odoo resolves the company-parent relationship for individual contact records so that each agent or buyer is linked to their parent company partner. Street, city, and country fields map directly using Odoo's address fields format.

Property Raptor listings have no direct Odoo CRM equivalent. We migrate listing data as product.product records with custom fields (bedrooms, bathrooms, property_type, listing_status) added via Odoo's custom field interface. Active listings also link to a crm.lead opportunity so the pipeline tracks the listing as an asset.

Property Raptor Deals migrate as Odoo crm.lead records. The lead_type field distinguishes between 'opportunity' (active deal) and 'lead' (inbound enquiry). Stage names from Property Raptor pipelines map to Odoo crm.stage records. Each Odoo sales team (crm.team) can have its own stage configuration, so multi-pipeline setups in Property Raptor map to separate crm.team records in Odoo.

Each Property Raptor pipeline becomes a dedicated Odoo crm.team. The pipeline stages migrate as crm.stage records ordered by sequence within that team. Stage probability percentages are stored on crm.stage records and are used by Odoo's forecasting engine. Stage names are preserved as Odoo stage names for reporting continuity.

Property Raptor records stage-transition timestamps on deal history. Odoo crm.lead stores only current stage_id and date_closed. We preserve historical stage transitions as a custom Stage_History__c text field in JSON format (stage name + ISO timestamp) for audit and reporting continuity.

Property Raptor Viewing records migrate as Odoo calendar.event records. The event is linked to the res.partner (contact) and the product.product (listing) using Odoo's many2one fields. Start and stop datetimes are preserved. Viewing outcome (attended, cancelled, no-show) stored as a custom field.

Property Raptor Offer objects have no Odoo equivalent. We migrate offer data (offer_amount, offer_status, offer_date, offer_notes) as custom fields on crm.lead for the related listing opportunity. Offer documents and attachments are stored in Odoo's ir.attachment model linked to the lead.

Property Raptor logged calls and emails map to Odoo mail.activity records attached to crm.lead or res.partner. Activity type, subject, date, and outcome (completed, cancelled) are preserved. Odoo's mail.activity model supports a subtype field that we map from Property Raptor's activity type.

Property Raptor owner IDs are resolved by matching the Salesforce User's email address to an existing Odoo res.users record. We generate an owner mapping report before migration that lists every Property Raptor owner, their email address, and their Odoo user status — whether the user exists, is inactive, or is not found. Your Odoo admin can create the missing Odoo user accounts ahead of migration, or accept reassignment of unmatched owners to a designated fallback sales team member.

Property Raptor file attachments on listings, offers, and deals are downloaded and re-uploaded to Odoo's ir.attachment table. Files are linked to their parent record (product.product for listings, crm.lead for offers) using Odoo's res_model and res_id fields. Odoo's 25MB per-file limit applies to each attachment during migration.

Property Raptor lead source data (portal enquiry, referral, website, listing portal) is mapped to Odoo crm.lead source_id using Odoo's utm.source records. Source name and medium are both preserved so that Odoo's lead attribution reporting remains functional after migration. Odoo utm.campaign links are created for multi-touch attribution tracking across multiple touchpoints.

Property Raptor's custom Salesforce fields (e.g., pre-qualification_status, mortgage_approved, property_requirement) are migrated as Odoo custom fields. Field type mapping follows this pattern: text → char, pick-list → selection, number → float, date → date. Each custom field requires Odoo Technical Mode setup before migration data loads — we deliver a field manifest specifying every field name, type, and target model.

Property Raptor workflows built on Salesforce Flow do not have an Odoo equivalent. We export your workflow definitions as JSON documentation so your Odoo developer can rebuild them using Odoo's Automations (Settings > Automations > Automated Actions) or the Studio module. This is a manual step — plan 2–4 weeks for complex workflow recreation.