Migrate from HomeSpotter Spacio to Pipedrive

Spacio guest records map directly to Pipedrive People. Each guest has name, email, phone, and optional custom form field values. Primary company association in Spacio translates to a Pipedrive Organization linked via person-organization relationship. Guest records without email are flagged for manual review — Pipedrive requires at least a name for Person creation.

Spacio properties (listing title, address, MLS number, price, beds/baths) map to Pipedrive Organizations. The Spacio property address maps to Organization address fields. Spacio's parent-child property hierarchy (if used) translates to Organization ParentId in Pipedrive. Properties without a contact association are imported as standalone Organization records for later linking.

Spacio events (open house sessions tied to a property on a date) have no direct Pipedrive equivalent. By default they translate to Pipedrive Activities (type=meeting) with custom fields for event name, property address, and agent. If the client tracks open house performance as sales pipeline opportunities, events can alternatively map to Deals — each open house session becomes a Deal with a custom pipeline.

Spacio agents (individual agent accounts) map to Pipedrive Users by email match. Spacio agent-level custom properties (branding color, default form questions, subscription tier) become Pipedrive custom fields on the User record. Brokerage-level agents in Spacio are flagged — their Pipedrive User must be assigned a visibility group matching their brokerage office before migration.

Spacio brokerages map to Pipedrive Organizations at the top of the hierarchy, establishing the root node for the entire organizational structure. All agent User records and property Organization records link up through the brokerage Organization as their parent, preserving the hierarchical relationships that Spacio maintains. Spacio brokerage-level custom properties such as white-label branding settings, onboarding completion status, and billing tier information become Organization custom fields in Pipedrive. This mapping ensures that brokerage-level context travels with the data and is available for filtering and reporting across the migrated dataset.

Spacio allows custom sign-in form questions beyond the standard name/email/phone. Each custom question becomes a Pipedrive custom field on the Person object (for guest answers) or Activity object (for event-level responses). Pipedrive requires custom fields to be pre-created — we deliver a custom field creation plan before migration data lands.

Spacio enriches verified contacts with social profile links. These are URL references stored as custom fields on the guest record. Since Pipedrive does not natively pull social data, we preserve the enrichment links as read-only custom fields (Social_Profile_URL__c) and recommend re-enriching via Pipedrive add-ons like Clearbit or FullContact post-migration.

Each Spacio sign-in records a check-in time. This becomes a custom datetime field (Spacio_CheckIn_Time__c) on the Pipedrive Activity created for the associated open house event. Original timestamps are preserved for reporting continuity — Pipedrive's CreatedDate reflects migration time, not the original open house date.

Spacio links guest sign-in records to open house events. In Pipedrive, Activities are linked to People via the Activity-Person association. We preserve this by creating a Pipedrive Activity per event and associating all guest People records to it, maintaining the relationship that Spacio stores natively.

Spacio events have status values (scheduled, completed, cancelled). These map to Pipedrive Activity status (completed/not completed) by default. If events map to Deals, status values map to the appropriate Deal stage in the client's Pipedrive pipeline. Status value mapping is confirmed during the sample migration phase.

Some Spacio setups include a lead quality rating or hot/warm/cold classification as a custom field. This maps to a Pipedrive custom number field (Lead_Quality_Score__c) on the Person record. If no score exists in Spacio, this field is omitted and can be added post-migration via Pipedrive's own scoring tools.

We tag every migrated record with a source attribution custom field (Spacio_Source__c) set to 'Spacio Migration' on each Pipedrive Person created from Spacio data. This preserves full audit traceability by allowing Pipedrive reports and filters to isolate all records originating from the migration, distinguishing them from records created manually after cutover. The source attribution field also supports de-duplication logic in future delta migrations, enabling the migration pipeline to identify and skip records that were already transferred in previous runs without re-importing duplicates into the Pipedrive dataset.