Migrate from PropertySimple to Odoo CRM

PropertySimple contacts map directly to Odoo res.partner records. The email, phone, name, and address fields carry over as-is. ZIP-code marketing flags from PropertySimple migrate as custom boolean or selection fields on res.partner. The contact's owner (agent) resolves to Odoo res.users by email match.

PropertySimple contacts with an active deal/listings association split into two records: the base contact lands in res.partner, and the listing context creates a crm.lead entry. This dual-write approach preserves the full contact record while giving Odoo a pipeline record to manage the deal lifecycle.

PropertySimple company records — representing brokerages, property management firms, or landlord entities — map to res.partner with is_company=True. The company name, domain, industry, and website fields transfer directly. Parent‑child hierarchies map via Odoo's parent_id on res.partner. Any custom fields such as tax_id or regulatory_status are created as additional custom fields on the partner record before load.

PropertySimple listing objects have no direct Odoo equivalent. We transform listing records into crm.lead entries, adding custom fields for listing_address, listing_price, listing_mls_number, property_type, and listing_status. The crm.lead name field holds the listing address or MLS description so it appears correctly in Odoo's pipeline kanban view.

PropertySimple deal records map 1:1 to Odoo crm.lead entries. The deal name populates crm.lead.name, the amount maps to expected_revenue, and the stage links to crm.stage via stage_id. Deal probability follows the stage probability in Odoo. Owner assignment resolves by email match to res.users; unmatched owners are flagged for user creation before load. Any deal-specific custom fields such as deal_source or referral_channel are created on crm.lead prior to migration.

PropertySimple pipelines map to Odoo crm.team (one team per pipeline). Within each team, stages map to crm.stage records with sequence ordering and probability values that mirror the original PropertySimple stage definitions. If PropertySimple uses custom pipeline names, we create matching crm.team records in Odoo before loading data.

Stage names are mapped value-by-value from PropertySimple to Odoo crm.stage. We preserve stage sequence, probability percentages, and the lost/won flags. Stage-entered timestamps from PropertySimple carry over as crm.lead.date_last_stage_update. If stages differ between pipelines in PropertySimple, each gets its own crm.stage group within the corresponding crm.team.

PropertySimple owner_id fields (agent assignments on contacts and deals) resolve by email to Odoo res.users. Agents without existing Odoo accounts are flagged in the pre-migration audit; your team can create the users first or assign records to a fallback agent. This prevents crm.lead.user_id null violations at load time.

PropertySimple activity log entries map to Odoo mail.message records linked to the corresponding res.partner or crm.lead. Call type logs create crm.activity records with subtype phone; email logs create mail.message with email subtype. Original timestamps, owners, and activity body text are preserved. Odoo chatter will display the imported history in the record's activity stream.

PropertySimple custom properties — zip_exclusivity_flag, listing_source, agent_tier, autopilot_status — require Odoo custom field creation before data loads. We deliver a custom field manifest specifying field name, type (boolean, selection, char, float), and target model (res.partner or crm.lead). Fields are created via Odoo Settings > Technical > Models before migration runs, then populated during the data load phase.

PropertySimple file attachments linked to contacts, listings, or deals download and re-upload to Odoo ir.attachment. Files attach to the corresponding res.partner or crm.lead record via res_model and res_id. File name, mimetype, and create date are preserved. Odoo's 25MB per-file limit applies; large files are flagged before migration.

PropertySimple Autopilot social media sequences and ZIP-code marketing rules have no Odoo equivalent. FlitStack exports the rule definitions — trigger conditions, content templates, posting schedules — as a JSON reference document. Your Odoo admin uses this to rebuild the logic in Odoo Automations or a compatible marketing app from the Odoo Apps Store.