Migrate from HomeSpotter Spacio to Twenty CRM

Each Spacio visitor becomes a Twenty People record. Name splits into firstName / lastName using the source fullname field. Email, phone, address components, LinkedIn URL, and social links map directly. The Spacio visitor record's eventId foreign key links the person to the corresponding open house event in Twenty.

Spacio's custom sign-in form questions and answers per visitor have no native equivalent in Twenty's standard People fields. We create a custom field for each active check-in question in Settings → Data Model before import. The answer value is stored as the field value on the People record at migration time.

Spacio auto-captures social profile links on verified contacts. Twenty has no native multi-social-field on People, so we store the most-used profile (LinkedIn) as a custom URL field (Social_LinkedIn__c) and remaining links as a custom text field (Social_Other__c) with comma-separated URLs. This preserves the full social context for agents to reference during follow-up without losing any captured data.

Spacio Property maps to Twenty Company. The property title becomes Company.name, full address composes into address fields, price becomes annualRevenue (approximate), and beds/baths stored as custom number fields (Bedrooms__c, Bathrooms__c) if the team uses them in follow-up. The Spacio Agent UKEY links to the managing agent.

Spacio open house events translate to Twenty Opportunities using event title as opportunity name, event date as expectedCloseDate, visitor count as amount (approximated or stored as custom field), and event status (scheduled / completed / cancelled) mapped via value_mapping to Opportunity Stage. A Task record is also created for the event date with the linked People records as attendees.

Event-level custom questions such as property feedback, buyer timeline, and financing status that are not already mapped to visitor answers become custom fields on the Opportunity record in Twenty. These fields are created in Settings → Data Model before the Opportunity CSV is imported, ensuring that the data is available for reporting and workflow triggers from the moment the records land.

Spacio Agent records map to Twenty WorkspaceMember records. Email is the unique identifier in Twenty (must exist before visitor and opportunity records that reference it are imported). We resolve agent email from the Spacio Agent object to the corresponding Twenty user and flag any agents not yet invited to the workspace before migration runs.

Spacio Teams (used in the Teams plan tier) have no direct Twenty equivalent. We create a custom select field (Team__c) on WorkspaceMember and map each agent's team assignment. The brokerage-level admin and reporting roles that exist in Spacio Teams do not translate — those organizational views must be rebuilt as Twenty workspace views.

Spacio's internal Agent UKEY is stored as a custom field (Spacio_Agent_Ukey__c) on Twenty WorkspaceMember records for traceability. Visitors and Opportunities created by a specific agent carry this ID as a read-only reference field, allowing managers to audit agent activity, track performance, and maintain a clear link back to the original Spacio agent identity across all migrated records.

Spacio visitor records link to a primary Property. We translate this as People.companyId pointing to the migrated Company record. Visitors who checked in but whose property is not yet migrated are flagged and assigned to a placeholder 'Unmapped Property' Company record.

Spacio pushes visitor records to third-party CRMs via built-in integrations. Twenty has no native integration with Spacio's sync mechanism. Teams using Spacio's CRM push must reconfigure those integrations from scratch in Twenty or via a middleware such as Zapier or Make.

Spacio sends an automated email to each visitor after the open house. Twenty has no native email sequencing or auto-follow-up trigger. This workflow must be rebuilt in Twenty's workflow builder or in an external automation tool (n8n, Zapier) using Twenty's GraphQL API as the trigger source.