Migrate your HomeSpotter Spacio data

Each event is tied to a specific Property/Listing and has a date range, attending agent, and visitor list. We export events as they appear in the brokerage report, including attendance counts and lead quality signals. Custom event types (e.g. community outreach events used beyond real estate) are preserved as-is with their original metadata.

Guest records include name, email, phone, and any custom form field values captured at sign-in. Social profile enrichment (LinkedIn, Facebook, Twitter URLs) is attached per record and migrated alongside the contact fields. Duplicate handling follows the destination CRM's dedup rules by email address.

Properties include title, price, beds, baths, address, MLS number, type, and listing agent email. The API returns these keyed by a numeric property ID (sid). We map these to the destination's Listings or Properties object and flag the MLS number as a reference field. Auto-populated listings from MLS feeds may have formatting variations we normalize at import.

Agent accounts are identified by a unique ukey and associated with their owned properties and events. On export, we pull the full agent roster from the brokerage dashboard. On import to a destination CRM, we match agents to existing user/contact records by email and set permissioned access to leads accordingly.

Seller reports are generated as HTML snapshots per event and include attendee data, lead quality ratings, and follow-up status. We export these as document attachments linked to the corresponding Open House Event. They do not carry forward as active report templates in the destination.

Automated email sequences are triggered by Spacio's internal automation engine post-event. These are platform-native workflows and are not exported as transferable automation rules. We document which leads received automated emails so the destination CRM can reproduce the nurture cadence manually.

Custom questions added to the digital sign-in form (e.g. 'Are you working with an agent?', 'Raffle entry') are stored as key-value pairs per guest record. We export all custom field values as flat properties and map them to equivalent custom fields in the destination CRM.

Spacio attaches LinkedIn, Facebook, and Twitter profile URLs to verified guest contacts. These are stored as separate fields per record. We migrate the URLs as text fields since most destination CRMs do not have native social URL fields.

The brokerage dashboard exposes aggregate reports covering listings, events, and leads across offices and agents within a date range. We pull the full report as a structured export and map each row to the corresponding object. Agent-level drill-down reports are available per-agent within the same export scope.

Spacio pushes leads directly into third-party CRMs via native integrations (Salesforce, HubSpot, Follow Up Boss, and others). During migration, we bypass the push integration and export raw data instead, then map to the destination CRM directly to avoid double-ingestion and field-mapping conflicts.