Migrate from HomeSpotter Spacio to Microsoft Dynamics 365 Sales

Spacio Guests with a confirmed buying interest or completed contact form route to Dynamics 365 Sales Contact. Guests with no follow-up action and no email address route to Lead. The split decision is based on whether the Guest has an email address and whether the follow-up status in Spacio is marked complete.

Spacio agents who will log in to Dynamics 365 Sales map to SystemUser records, matched by email address. Agents who will not have Dynamics licenses map to Contact records and are assigned as OwnerId on their associated Opportunities and Accounts.

Spacio Listings with a brokerage association map to an Account record representing the brokerage. The property-level details (price, beds, baths, address, MLS number) map to custom fields on an Opportunity record linked to that Account. Each open house event for that listing creates a separate Opportunity.

Spacio Listings without a brokerage association (FSBO or agent-owned listings) map directly to Opportunity records with property details stored in custom fields. The agent's email is used to resolve the OwnerId. If the agent lacks a Dynamics 365 user account, record is assigned to a fallback owner as a team lead or brokerage administrator. Details like lot size, year built, and HOA fees are stored as custom fields for reporting.

Each Spacio open house Event creates or updates an Opportunity representing that listing at a specific date. If the brokerage tracks event-level analytics beyond the Opportunity, a custom Event entity is created with a 1:N relationship to Opportunity. The custom Event entity stores metrics such as attendance count, visitor interest level, and follow‑up tasks, enabling detailed reporting on open house effectiveness across listings and agents.

Spacio gathers social profile URLs on verified contacts. These URLs are stored as custom text fields (e.g., LinkedIn_URL__c, Facebook_URL__c) on the Contact record. No native Dynamics equivalent exists; FlitStack preserves the data as reference fields. These reference fields allow agents to view a guest's LinkedIn or Facebook profile from the Contact form, supporting personalized outreach. The URLs are maintained even if the external platform changes, ensuring continuity of social context.

Spacio allows unlimited custom questions per event sign-in form. Each unique custom field is created as a custom field in Dynamics 365 Sales on the Contact or Lead entity, matching the data type (text, picklist, date). Professional tier has a 15-field limit — Enterprise or custom field budgeting required for more.

Spacio's automated follow-up email records migrate as Email (activity) records in Dynamics 365 Sales tied to the Contact record. The email body and timestamp are preserved; the sending automation logic does not migrate and must be rebuilt in Power Automate.

Spacio office and brokerage entities map to Account records in Dynamics 365 Sales. The Account Name is the brokerage or office name, with Address, Phone, and Website mapped to standard Account fields. Spacio agent counts and team structures are noted for later Dynamics security role assignment.

Spacio seller report exports (attendee lists, lead quality notes) migrate as Note or Attachment records linked to the relevant Opportunity in Dynamics 365 Sales. The report PDF is uploaded as a file attachment to the Opportunity. During migration, PDF is associated with the Opportunity's document library, preserving the file name and timestamp for audit trails. If multiple reports exist for the same listing, they are linked to maintain reference.

Spacio pulls MLS listing data (MLS number, listing status, photo URLs) via Lone Wolf integration. MLS numbers migrate as custom text fields on the Account or Opportunity. Listing status (Active, Pending, Sold) maps to the Opportunity StageName or a custom pick-list field.

Spacio role-based permissions (Agent, Team Admin, Brokerage Admin) have no direct equivalent in Dynamics 365 Sales security model. Permissions are preserved as documentation for your Dynamics admin to map to Security Roles and Field-Level Security profiles post-migration. The documentation includes each user's Spacio role, assigned listings, and team membership, which helps the admin assign appropriate Business Units and privileges in Dynamics 365. This ensures users retain access matching their responsibilities.