Migrate from HomeSpotter Spacio to Salesforce Sales Cloud

Spacio visitor leads with name, email, phone, and sign-in form responses map directly to Salesforce Lead records. Custom form fields on Spacio become custom fields on the Salesforce Lead object (Spacio_Form_Field__c naming convention). Original capture timestamp stored as a custom datetime field for reporting continuity.

Spacio properties contain address, price, beds, baths, type, MLS number, and image URL. These map to Salesforce Account records using the property address as Account Name, with property details stored in custom fields (Property_Price__c, Beds__c, Baths__c, MLS_Number__c). Spacio supports multiple agents per property, which requires junction objects or primary agent assignment in Salesforce.

Spacio open house events (date, time, property, agent) map to Salesforce Campaigns for aggregate reporting across multiple events, or to Events for individual session tracking. FlitStack surfaces the choice before migration and maps accordingly. Event attendance (visitor list) becomes Campaign Members linked to the migrated leads.

Spacio agent accounts (name, email, brokerage association) are matched to Salesforce Users by email. Unmatched agents are flagged before migration — your team either creates Salesforce users first or assigns their records to a fallback owner. Agent-level Spacio data (open house count, lead volume) migrates as a custom object or fields on the User record.

Spacio brokerages with multi-office structures can map to Salesforce Account hierarchy (Parent Account for the brokerage, child Accounts for offices) or a custom Brokerage__c object depending on reporting needs. FlitStack delivers a schema plan before migration so you choose the model.

Spacio gathers social profile URLs on verified contacts during sign-in. This data has no native Salesforce equivalent and migrates as a custom rich-text or URL field (Social_Profiles__c) on the Lead record for reference by sales reps. Sales reps can click the stored URLs to view profiles directly within the browser, and the field can be included in list views for quick reference during follow-up calls.

Spacio automated follow-up emails trigger on lead capture. These cannot migrate — they require rebuilding in Salesforce using Flow or Sales Engagement tools. FlitStack exports Spacio automation definitions as a reference document for your Salesforce admin. After migration, you can replicate the same triggers in Flow by creating entry conditions that fire when a Lead is created with the Open_House_Source__c flag set, then send templated emails via Salesforce email actions.

Spacio allows custom check-in questions beyond standard name/email/phone. Each custom form field creates a corresponding custom field in Salesforce (Spacio_Custom_Field__c naming). Value types (text, picklist, date) are mapped to Salesforce field types during migration planning. If you have conditional logic or required settings in Spacio, document those rules so your Salesforce admin can replicate them using field-level dependencies or validation formulas in the target org.

Spacio properties can have multiple assigned agents. Salesforce Accounts support multiple contacts, and AccountContactRelation handles additional roles. For agent-primary property relationships, FlitStack maps the primary agent to Contact.AccountId and additional agents via AccountContactRelation. You can also add a custom Agent_Role__c picklist on AccountContactRelation to capture whether an agent is the listing agent, co-listing agent, or showing agent for reporting segmentation.

Spacio auto-populates agent accounts with listings from MLS integrations. MLS listing data (MLS number, status, photos) migrates to Salesforce as custom fields on the Account record or as a separate Listings custom object with a lookup to Account, depending on your Salesforce edition and reporting needs.