Migrate from Real Estate CRM Software to Salesforce Sales Cloud

Real estate contacts split based on source status: active buyers/sellers with transactions route to Salesforce Contact; cold leads and inquiries without closed deals route to Salesforce Lead. Source contact records without a transaction history land as Leads to preserve Salesforce's lead-conversion workflow.

The brokerage or company record in the source maps directly to Salesforce Account. Branch offices and affiliated agents stored as child Account records using ParentId. Brokerage-level billing address and commission structure fields migrate as custom fields on Account. Commission tiers, franchise fees, and regional identifiers also move as custom fields, preserving any tiered billing logic the brokerage uses.

Property records have no direct Salesforce equivalent — they migrate as a custom Property__c object. Fields include address, MLS number, property type, status, list price, and agent assignment. We create the custom object definition in Salesforce before migration and map all property fields to the new schema.

The listing lifecycle (Active, Under Contract, Pending, Closed) maps to Salesforce Opportunity stages. Each pipeline stage value maps to a corresponding StageName value. If the source has multiple pipelines (residential vs. commercial), each becomes a Salesforce Record Type with its own Sales Process and stage pick-list.

Closed and in-progress transactions map to Salesforce Opportunity. Sale price migrates to Opportunity.Amount. Commission fields migrate to custom Opportunity fields. The related Property__c links via a lookup field so the transaction always shows its associated listing. Stage history, close dates, and probability percentages are also transferred to maintain reporting continuity and forecast accuracy across the pipeline.

Agent records are resolved by email match to existing Salesforce User records. If an agent does not have a Salesforce User, their records are assigned to a fallback User (brokerage admin) and flagged for the team to create the User account before go-live.

When a transaction involves a co-agent or referral partner, the primary agent is set as Opportunity.OwnerId and the secondary agent is added as an OpportunityTeamMember with Role = 'Co-Agent' or 'Referral'. We parse the source co-agent field and create the team member records during the Opportunity load.

Showing appointments, calls, and emails linked to a property or transaction map to Salesforce Tasks (for calls, emails) and Events (for showings). Notes attached to a property or contact map to Salesforce Notes. Original timestamps, owners, and parent-record links are preserved.

Listing photos, contracts, and disclosure documents are re-uploaded to Salesforce Files linked to the Property__c or Opportunity record. Large files (>25MB) are chunked per Salesforce's file size limits. We preserve folder structure as ContentWorkspace libraries where the source supports it.

Source custom fields specific to listings — HOA fees, lot size, year built, MLS ID, showing instructions — migrate as custom fields on Property__c. Field type mapping handles currency, date, pick-list, and text fields. The Salesforce admin pre-creates these fields per our field map deliverable before migration.

Listing alerts, lead-assignment rules, and showing-notification automations do not migrate. These are destination-side configuration built in Flow. We export the workflow definitions as a JSON reference file for the Salesforce admin to use as a rebuild guide.

MLS feeds and IDX listing imports are source-platform-specific and cannot migrate. Teams must install an AppExchange MLS integration (e.g., ListHub, Bridge Interactive) or build a custom API connector post-migration. Historical listing data migrates as property records; live syndication requires a separate setup.