Migrate from Real Estate CRM to Salesforce Sales Cloud

Buyer contacts migrate as Salesforce Contacts. The source role label is preserved in a custom Role__c pick-list field on Contact for segmentation and reporting. Primary associated account is resolved from the source company field or by broker association. OwnerId is set via email match to Salesforce User. Original create dates are preserved in Original_Create_Date__c custom datetime field.

Seller contacts migrate as Salesforce Contacts with the seller role preserved in Role__c. The property being sold links via a custom Property__c lookup on the Contact record for listing association. Listing agent assignment is preserved as OwnerId on the related Property__c record. This maintains the relationship between the seller contact and their listed property.

Tenant and vendor contacts migrate as Contacts with a custom Role__c pick-list value. Vendors representing companies rather than individuals may alternatively map to Account records for proper company association. The mapping decision depends on whether the vendor functions as an individual contact or as a company representative in the source system.

Source company records map to Salesforce Accounts. Parent brokerage and branch office hierarchies map to ParentId in Salesforce to preserve organizational structure. Account Type field set to match source entity type such as Brokerage, Franchise, or Independent. Billing and shipping addresses migrate to Account address fields. Industry pick-list mapped per source value.

Each transaction becomes a Salesforce Opportunity. The source deal stage maps to Opportunity StageName via value mapping per record type. Amount, close date, and property reference migrate as-is. OwnerId resolved by email match to the agent assigned in the source. Source_System_ID__c stores the original ID for traceability.

Source deal pipelines map to Salesforce Sales Processes keyed by Record Type. Each distinct pipeline in the source requires a Salesforce record type so stage pick-list values are scoped correctly. Stage names map value-by-value with probabilities re-applied from Salesforce defaults. This ensures stage filtering works correctly per deal type.

Property records do not have a direct Salesforce standard object. We create a Property__c custom object with address compound, price, status, property type, and beds/baths fields. Listings active in a transaction link to the Opportunity via a lookup field. Historical listings kept as read-only for deal reference. MLS numbers preserved in MLS_Number__c custom field.

Source call logs, emails, and meeting records migrate as Salesforce Tasks (for calls and emails) and Events (for meetings). WhoId links to the Contact or Lead; WhatId links to the related Opportunity or Property__c. Original timestamps preserved; owners resolved by email match. Activity types map to Salesforce Task Type pick-list.

Text notes migrate as Salesforce Notes (not legacy Note object). File attachments are downloaded and re-uploaded as Salesforce Files linked to the parent record. File size limits of 25MB per file in Salesforce apply; larger files flagged for manual handling. ContentDocument links tracked via ContentDocumentLink junction records.

Any source custom objects—ShowingRequest, Offer, Lease—map 1:1 to Salesforce custom objects with the __c suffix. Relationships between custom objects and standard objects require junction objects in Salesforce if the source used many-to-many associations. We identify junction requirements in the migration plan before data moves to ensure relationship integrity.