Migrate from HomeSpotter Spacio to Nutshell

Open house event context has no native Nutshell equivalent — requires custom field strategy

Spacio's core value is capturing a visitor's relationship to a specific open house event — the event name, date, and listing address. Nutshell has no native open house event object. If you rely on Spacio's event reporting to attribute leads back to specific open houses, that context is lost unless you create custom fields (Open_House_Event_Name__c, Open_House_Date__c) on the Nutshell Person record. We include these in every migration plan, but your team needs to configure the custom fields in Nutshell before data lands so the migration can write to them. Open house performance reporting then requires building custom Nutshell reports on these fields — it is not available out of the box.

Spacio follow-up email automations cannot transfer and must be rebuilt in Nutshell

Spacio sends an automated follow-up email to every open house visitor after the event closes. These email templates and the automation that triggers them are not exposed via Spacio's API and cannot be exported. The email send log migrates as an activity note on the Nutshell Person record, but the automation itself must be recreated in Nutshell's email sequence builder (available in Nutshell Pro and Enterprise). If your current Spacio follow-up sequence uses specific timing, content, or conditional logic, that design must be recreated from scratch using Nutshell's sequence tools after the migration is complete.

Spacio per-agent data extraction requires role-aware API key configuration

Spacio's JSON-RPC API requires an agent-level API key (ukey) to retrieve property and visitor data for that agent's account. Brokerage-level data aggregation requires either multiple per-agent API calls or a brokerage-level credential. If your migration plan covers multiple agents under one brokerage, FlitStack AI sequences extraction per agent key, resolves duplicate contacts (same visitor signing in at multiple open houses), and consolidates them into a single Nutshell Person record with all open house event references preserved. Unresolvable duplicates are flagged in the pre-migration diff report.

Spacio visitor contacts without email addresses require manual enrichment or exclusion

Spacio allows visitors to sign in with a name and phone number only, skipping the email field. Nutshell's People object does not strictly require email for creation, but email is the primary deduplication key for subsequent delta runs and for linking to Nutshell's email sequence automation. Contacts migrated without an email address will be flagged in the migration report and can either be manually enriched pre-migration or imported as a separate 'no-email' batch that your team follows up on directly. We recommend enforcing an email requirement in your Spacio sign-in form post-migration to prevent this gap from recurring.

Nutshell contact deduplication is name-and-email based, not source-ID based

If the same person visited multiple open houses, Spacio creates one visitor record per event. Nutshell deduplicates People by name-and-email match. FlitStack AI resolves these duplicates during migration by email match, collapsing multiple Spacio visitor records into a single Nutshell Person with all open house event references accumulated in the Open_House_Event_Name__c custom field. If the same person used different email addresses across visits (e.g., personal vs. work email), deduplication falls back to name match and flags the record for manual review.