CRM migration
Field-level mapping, validation, and rollback between HomeSpotter Spacio and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
HomeSpotter Spacio
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between HomeSpotter Spacio and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
HomeSpotter Spacio stores open house guest leads, property listings, event records, and agent assignments in a flat export model centered on the Event (open house) and Lead (guest) objects. Freshsales CRM uses a separate Lead → Contact → Account → Deal hierarchy with custom objects for non-standard entities. FlitStack AI extracts Spacio lead records via the REST API (12,000 requests/hour ceiling), maps guest properties to Freshsales Account or custom object fields, and converts open house events into Deals with pipeline stages representing buyer interest level. Custom form questions Spacio collects per event — buyer type, financing status, timeline — migrate as Freshsales custom fields. Social profile URLs Spacio enriches (LinkedIn, Facebook) land in Freshsales custom text fields since no native social link field exists. Automated follow-up email templates and CRM integration workflows in Spacio have no Freshsales equivalent and must be rebuilt using Freshsales Sales Sequences and workflow rules post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a HomeSpotter Spacio object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
HomeSpotter Spacio
Spacio Lead (Guest)
Freshsales
Freshsales Lead
1:1Spacio open house guests map directly to Freshsales Leads. Each guest record carries name, email, phone, and property interest. Freshsales Lead Status defaults to 'New' unless the source record shows a signed buyer agreement, in which case it routes to 'Open - Not Contacted'.
HomeSpotter Spacio
Spacio Lead with signed buyer agreement
Freshsales
Freshsales Contact + Account
1:manySpacio guests flagged as 'Signed Buyer' or with financing documents attached in the lead record split into both a Freshsales Contact (person record) and an Account (derived from the property of interest or the guest's listed employer). The Account name defaults to the property address if no company name is present.
HomeSpotter Spacio
Spacio Property
Freshsales
Freshsales Account
1:1Each Spacio property listing (address, price, beds, baths, MLS number, listing agent) maps to a Freshsales Account record representing the property as a business entity. The Account Name field stores the full property address; the website field stores the MLS listing URL for brokerages that maintain public listing links.
HomeSpotter Spacio
Spacio Property
Freshsales
Freshsales Custom Object: Property
1:1Property-specific fields that have no Freshsales Account equivalent — MLS number, listing agent user key, property type (apartment, condo, house), and number of beds/baths — require a Freshsales custom object named 'Property' or custom fields on the Account object. Which approach is used depends on whether the brokerage wants property records reportable alongside contacts and deals.
HomeSpotter Spacio
Spacio Event (Open House)
Freshsales
Freshsales Deal
1:1Each Spacio open house event becomes a Freshsales Deal representing the event as a sales opportunity. The Deal name follows the pattern '[Property Address] — [Event Date] Open House'. Deal Amount is set to the listed property price to give the deal a monetary anchor in Freshsales pipeline views and forecasting reports.
HomeSpotter Spacio
Spacio Event stage (attendee count, buyer interest level)
Freshsales
Freshsales Deal Stage
1:1Spacio open house attendee responses to buyer-interest questions (e.g., 'Ready to buy', 'Exploring', 'Just browsing') map to Freshsales Deal Stage values. 'Ready to buy with financing' maps to 'Qualified'; 'Exploring' maps to 'Proposal Sent'; 'Just browsing' maps to 'Prospecting'. Stage names are configurable in Freshsales pipeline settings and the mapping is validated against the brokerage's existing stage names before migration runs.
HomeSpotter Spacio
Spacio Agent / Team Member
Freshsales
Freshsales User
1:1Spacio agent records resolve to Freshsales Users by email match. Each agent's Spacio user key is stored in a custom field (Agent_Spacio_Key__c) on the corresponding Freshsales User record for traceability. Agents without a resolvable email in Freshsales are flagged pre-migration so the brokerage admin can provision Freshsales accounts before the cutover.
HomeSpotter Spacio
Spacio Team
Freshsales
Freshsales Sales Team
1:1Spacio team groupings (multiple agents under one brokerage account) map to Freshsales Sales Teams. Team lead agents are designated as the Sales Team owner in Freshsales. Membership is resolved by matching each Spacio agent's team assignment to the Freshsales user roster.
HomeSpotter Spacio
Spacio custom form questions per event
Freshsales
Freshsales Custom Field (Lead/Deal)
1:1Spacio allows agents to configure custom check-in questions per event — financing status, timeline, referral source, property feedback. Each unique question becomes a Freshsales custom field (dropdown or text depending on question type) applied to the Lead and Deal objects. Value mappings are created for pick-list questions so 'Cash buyer' in Spacio maps to 'Cash' in Freshsales.
HomeSpotter Spacio
Spacio automated guest email
Freshsales
Freshsales Sales Sequence
1:1Spacio sends a customizable follow-up email to each guest after an open house event. Freshsales has no equivalent event-triggered email that fires based on a property record. The closest analogue is Freshsales Sales Sequences with time-based email steps, but the trigger logic is contact-centric rather than event-centric — your Freshsales admin must configure the sequence enrollment criteria based on Lead creation date or a custom 'Event Attended' field.
HomeSpotter Spacio
Spacio seller report
Freshsales
Freshsales Report / PDF Export
1:1Spacio generates branded seller reports listing attendee names, contact info, and interest level after each open house. Freshsales has no native equivalent. After migration, your team can build a Freshsales custom report that aggregates Deal records for each open house property, then export as PDF — but the layout and branding must be recreated manually in Freshsales Report Builder.
HomeSpotter Spacio
Spacio social profile enrichment (LinkedIn, Facebook URLs)
Freshsales
Freshsales Custom Field (Text)
1:1Spacio enriches guest records with social profile URLs when available. Freshsales has no native social profile fields on Lead or Contact objects. These URLs are stored as custom text fields on the Lead record: Social_LinkedIn__c and Social_Facebook__c. The enrichment data is informational only — Freshsales does not use it for scoring or automation.
| HomeSpotter Spacio | Freshsales | Compatibility | |
|---|---|---|---|
| Spacio Lead (Guest) | Freshsales Lead1:1 | Fully supported | |
| Spacio Lead with signed buyer agreement | Freshsales Contact + Account1:many | Fully supported | |
| Spacio Property | Freshsales Account1:1 | Fully supported | |
| Spacio Property | Freshsales Custom Object: Property1:1 | Fully supported | |
| Spacio Event (Open House) | Freshsales Deal1:1 | Fully supported | |
| Spacio Event stage (attendee count, buyer interest level) | Freshsales Deal Stage1:1 | Fully supported | |
| Spacio Agent / Team Member | Freshsales User1:1 | Fully supported | |
| Spacio Team | Freshsales Sales Team1:1 | Fully supported | |
| Spacio custom form questions per event | Freshsales Custom Field (Lead/Deal)1:1 | Fully supported | |
| Spacio automated guest email | Freshsales Sales Sequence1:1 | Fully supported | |
| Spacio seller report | Freshsales Report / PDF Export1:1 | Fully supported | |
| Spacio social profile enrichment (LinkedIn, Facebook URLs) | Freshsales Custom Field (Text)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
HomeSpotter Spacio gotchas
12,000 hourly rate limit on API key creation calls
No public bulk export endpoint
Social profile enrichment does not persist through CRM push
Custom sign-in form fields vary per account and per event
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Spacio data export and identify custom form schema
FlitStack AI connects to the Spacio API using your API key and performs a discovery export of all leads, properties, events, agents, and team records. During this phase we identify every unique custom form question across all events and build a schema matrix that maps each question to a Freshsales custom field name, type, and pick-list value mapping. Any custom form questions that appear on fewer than 5% of events are flagged for your review — you decide whether to create a Freshsales field for them or accept that data as notes.
Resolve agent and team records to Freshsales users
Spacio agent records are matched to Freshsales users by email address. Agents without a corresponding Freshsales account are listed for your admin team to provision before migration runs. Teams without a Freshsales counterpart are created as 'Unassigned' with a placeholder owner. Spacio team structures map to Freshsales Sales Teams during this step — the team hierarchy is preserved so manager-to-rep reporting lines carry over.
Create Freshsales custom fields and object schema
Based on the schema matrix from Step 1, FlitStack creates all required Freshsales custom fields on the Lead and Deal objects (and the Property custom object if applicable) via the Freshsales API. Pick-list fields are populated with the mapped values from Spacio. Field-level permissions are set to read/write for all roles by default — your Freshsales admin can tighten these after go-live. This step runs before any data insertion to ensure the target schema is ready.
Run a sample migration with field-level diff
A representative slice of 200–500 Spacio records (covering multiple events, at least one custom form variant, and both buyer-interest levels) is migrated to Freshsales in a sandbox environment or a dedicated test run. FlitStack generates a field-level diff comparing source values to destination field values — you review and approve the mapping for each custom question, the deal name format, and owner assignment before the full run commits.
Execute full migration with delta-pickup window
All remaining Spacio records are migrated to Freshsales. A delta-pickup window (typically 24–48 hours after the main run completes) captures any new leads created in Spacio or updated event statuses during the cutover period. FlitStack uses scoped read access on Spacio during this window — your team continues using Spacio at open houses uninterrupted. After delta-pickup completes, an audit log is delivered showing record counts, any errors, and owner resolution statistics.
Platform deep dives
HomeSpotter Spacio
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across HomeSpotter Spacio and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
HomeSpotter Spacio: 12,000 requests per hour per API key (default; increase available by request).
Data volume sensitivity
HomeSpotter Spacio doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during HomeSpotter Spacio to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your HomeSpotter Spacio to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave HomeSpotter Spacio
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.