Migrate from HomeSpotter Spacio to Odoo CRM

Spacio guest leads map directly to Odoo crm.lead records. The crm.lead type field distinguishes 'lead' from 'opportunity' — all migrated Spacio guests land as lead type. Contact details (name, email, phone) populate crm.lead fields; additional contact data stores on the linked res.partner record. Original Spacio lead creation timestamp preserved as a custom datetime field.

Every Spacio lead's email address creates or matches a res.partner record in Odoo. Odoo's mail.thread on res.partner aggregates email conversations on the contact. If the email already exists in Odoo, the crm.lead links to the existing partner; otherwise a new partner is created. This prevents duplicate contact records.

Spacio property records (title, price, beds, baths, address, MLS number) become Odoo product.product entries with type='service' or 'product' depending on whether the brokerage treats listings as sellable assets. The Spacio property price maps to product.list_price; MLS number maps to a custom Char field (x_mls_number). Property images are downloaded from S3 and re-uploaded as product images via ir.attachment.

Spacio natively links a guest lead to the property at sign-in. Odoo crm.lead has no native M2M to product.product for this use case. We create a custom M2M field (x_spacio_property_ids) on crm.lead to preserve the property association. Alternatively, the property is set as the lead name or stored in a custom Char field (x_spacio_property_address) for quick reference.

Spacio open house events (event date, property, agent) migrate to Odoo calendar.event records. The calendar.event is linked back to the associated crm.lead records via a custom relational field (x_open_house_event_id). This preserves the event context — which open house generated each lead — in Odoo's calendar and CRM modules simultaneously.

Spacio agent records (name, email, ukey) are matched to Odoo res.users by email address. Unmatched agents are flagged before migration for manual Odoo user creation or assignment to a fallback owner. Team-level data from Spacio (team hierarchy, brokerage) populates crm.team records and team membership on res.users.

Spacio enriches leads with LinkedIn and other social profile URLs when contacts are verified. These URLs migrate to custom Char fields on res.partner (e.g., x_linkedin_url, x_social_profile). Odoo has no native social-enrichment field; these are stored as reference-only data for agents to use manually during outreach.

Some Spacio brokerages assign guest quality ratings to leads. Odoo crm.lead has no native quality field. We migrate this as a selection field (x_lead_quality) on crm.lead with values matching the Spacio rating scale. Alternatively, a crm.tag is applied to the lead for filtering in Odoo's Kanban view.

Spacio records the capture method (QR code, manual form, MLS link) as a lead source attribute. Odoo CRM has a native source_id field on crm.lead referencing utm.source values. We map Spacio source strings to Odoo utm.source records — this populates Odoo's lead source reporting without requiring a custom field.

Spacio file attachments on leads (form metadata, signed-in guest lists) are downloaded and re-uploaded to Odoo ir.attachment linked to the corresponding crm.lead. File naming preserves the original Spacio reference (spacio_{lead_id}_{filename}) for traceability. Odoo's ir.attachment is accessible from the crm.lead form view under the Documents smart button.

Spacio generates branded seller report PDFs listing attendees, lead quality, and open house metrics. Odoo has no native seller report export. We preserve the PDF URL or attach the last-generated report as an ir.attachment on the related crm.lead and calendar.event. The report must be rebuilt manually in Odoo using the Odoo Spreadsheet app or exported to a BI tool.

Spacio sends automated post-open-house emails to every guest using platform-managed templates. Odoo has no automated email-sending trigger native to the open house event model. We document the Spacio email templates (subject, body, timing) as a reference export so your Odoo admin can rebuild equivalent mail.template records driven by crm.lead stage-change or calendar.event end-date triggers.