Migrate from Homesnap Pro to Microsoft Dynamics 365 Sales

Property listing data requires a custom Dataverse entity — standard Dynamics 365 Sales has no property or MLS listing object

Homesnap Pro's core data object is the property listing with MLS ID, status, price, and showing history. Dynamics 365 Sales has no native equivalent — there is no 'Property' or 'Listing' standard entity. We create a Property__c custom table in Dataverse to hold address, price, status, MLS_ID, bedrooms, bathrooms, square footage, and property type. This requires Sales Enterprise license (or a custom-field add-on to Sales Professional) because the 15-table custom limit on Sales Professional is consumed quickly once Property__c plus its related columns are created. We deliver the custom entity schema as part of the migration plan so your Dynamics admin can provision it before data lands. If your organization uses more than five custom entities total, the Enterprise tier becomes mandatory.

Likelihood-to-List predictive scores and MLS-triggered automations have no Dynamics 365 equivalent and cannot migrate

Homesnap Pro's discontinued Likelihood-to-List algorithm scored properties based on homeowner behavior patterns — this AI output has no counterpart in Dynamics 365 Sales. We preserve the last-known score as an integer field on the Property__c record for historical reference, but the predictive logic does not transfer. More significantly, Homesnap Pro's MLS-triggered showing notifications, agent-to-agent status alerts, and MLS-bound workflow automations are platform-native constructs with no equivalent in Dynamics. Power Automate can replicate some of this logic using Dataverse triggers and Microsoft 365 connectors, but the automation definitions must be rebuilt from scratch. We export all Homesnap Pro workflow definitions as a structured JSON reference document to accelerate the Power Automate rebuild.

Homesnap Pro agent accounts map to CRM users, not contacts — owner resolution by email match is required before migration

In Homesnap Pro, agents are platform user accounts. In Dynamics 365 Sales, agents must be provisioned as SystemUser records to own records (Contacts, Property__c, Appointments). The migration does not create Dynamics user accounts — it resolves Homesnap Pro owner IDs against existing Dynamics users by email address. If a Homesnap Pro agent has no matching email in Dynamics 365, their records are flagged with an Owner_Unresolved__c flag and must be addressed before the full migration runs (either by inviting the agent to Dynamics or by assigning records to a fallback owner). Owner resolution failures are the most common cause of migration delays for multi-agent offices.

Sales Professional license caps at 15 custom tables — most real estate migrations exceed this with Property, Showing History, and custom field entities

Dynamics 365 Sales Professional carries a 15 custom table limit as of the 2024 licensing update. A typical Homesnap Pro migration requires at minimum: a Property__c custom entity, a Showing_Request__c activity log (if showing history is tracked separately), and custom columns on Contact and Account for client-specific real estate fields (budget range, prequalification status, preferred property type, likelihood score). These quickly consume the 15-table allowance. If your migration requires more than 15 custom tables, you must upgrade to Sales Enterprise ($105/user/month vs. $65/user/month). We flag this during discovery and include a licensing tier recommendation in the migration plan before any schema work begins.

Homesnap Pro platform end date (October 23, 2023) creates a hard migration deadline — data access may become read-only or unavailable

Homesnap Pro was discontinued by CoStar Group on October 23, 2023, with services migrated to Homes Pro. Agents who did not transition to Homes Pro or export their data before the sunset date may face limited or read-only access to their historical records. Any migration initiated after the sunset must work from the most recent available export rather than live API access, which limits the ability to capture delta changes. We strongly recommend initiating migration planning immediately if you have not yet exported your Homesnap Pro data. If your data is no longer accessible via API, we can work from CSV exports or database backups to reconstruct the migration target schema, though delta-pickup capability is lost.