Migrate from Homesnap Pro to Salesforce Sales Cloud

Homesnap Pro agents resolve to Salesforce Users by email match. Agents without a matching Salesforce user are flagged before migration so the brokerage can invite them or assign their records to a fallback user owner. The flagged list includes each agent’s email and mismatch reason. The brokerage may choose to create Salesforce users or assign the records to an admin owner to maintain data integrity throughout the cutover.

Homesnap Pro clients who are active buyers or sellers become Salesforce Contacts. Prospects without a transaction history route to Leads. The split is based on the presence of a linked transaction in the source data — clients with at least one showing or offer become Contacts.

Homesnap Pro's buyer/seller classification migrates as a custom pick-list field (Client_Type__c) on Contact. Values (Buyer, Seller, Both, Landlord, Tenant) are preserved exactly and mapped to the custom field's pick-list options in Salesforce. This custom field enables segmentation for targeted marketing and reporting, and can be marked as required on the Contact layout to enforce data consistency. Additional sub‑types can be added as separate pick‑list values during the schema build.

Homesnap Pro listings have no Salesforce standard equivalent. We create a Property__c custom object with fields for address, MLS number, list price, status, property type, bedrooms, bathrooms, square footage, and listing agent. The object links to the listing Contact (seller) via a lookup.

Homesnap Pro listing status values (Active, Pending, Sold, Withdrawn, Expired) map to Salesforce custom pick-list values on Property__c.Status__c. Status transitions and their timestamps are preserved as an audit text field, allowing you to reconstruct the history of each listing post‑migration. This audit field records the previous status, the new status, and the date/time of the change, providing a timeline for reporting and compliance without relying on Salesforce’s native audit capabilities.

Homesnap Pro showings map to a custom Showing__c object linked to Property__c and Contact. We also create Salesforce Events for calendar visibility. Each showing stores agent, client, property, scheduled time, status, feedback, and notes. The Showing__c record includes lookups to the showing agent User and the client Contact, ensuring referential integrity. Status values (Confirmed, Completed, Cancelled, No‑show) are mapped to a pick‑list, and feedback is stored in a text field.

Homesnap Pro client messages map to Salesforce Tasks with Type='Email' or 'Call' depending on content. Original timestamps, sender, and recipient are preserved. Rich-text formatting in messages is converted to plain text for Salesforce compatibility. If a message includes an attachment, the file is saved to Salesforce Files and linked to the related Contact or Property record, maintaining a complete communication history within the CRM.

Homesnap Pro transactions map directly to Salesforce Opportunities. Deal name, amount, stage, close date, and agent owner are preserved, and transaction stages are mapped to Salesforce Opportunity Stage values per the brokerage's sales process. Custom fields for commission amount, agent split, and transaction type are added to capture financial context. Property is stored as a lookup to Property__c, and client is linked via AccountId, with contacts added through OpportunityContactRole.

Homesnap Pro commission data (agreed commission, split percentage, transaction fee) migrates to custom Number and Currency fields on Opportunity (Commission_Amount__c, Agent_Split__c). These are non‑standard fields that require a Salesforce admin to expose them on the page layouts and to include them in reports and dashboards. By adding these fields to the Opportunity layout, agents can view commission details inline, and managers can build commission‑related reports without relying on external spreadsheets.

Every Homesnap Pro custom property is analyzed for type and object scope. Numeric properties map to Number fields, text to Text, dates to Date, and pick‑lists to pick‑lists. We create each as a custom field on the appropriate Salesforce object using the __c suffix naming convention.

Files attached to Homesnap Pro listings or transactions are downloaded and uploaded to Salesforce Files, linked to the Property__c, Opportunity, or Contact record. File size limits (25MB per file) are respected; files over limit are compressed. We preserve the file name and date, and create a Salesforce File version entry referencing the source system. If a file cannot be transferred due to size or format, we log it for handling.

Homesnap Pro teams and office groupings map to Salesforce Territories or Account Teams depending on the brokerage's Salesforce model. We surface this as a planning decision before migration runs, since the choice affects sharing rules, record access, and reporting hierarchies. During planning, we help you define whether teams should be modeled as Territories, Account Teams, or a combination, and we document the implications for agent onboarding and performance tracking.