Migrate from CRM for real estate to Salesforce Sales Cloud

Source contact records map to Salesforce Contact linked to an Account. The contact's primary associated organization becomes the Account Name. If the source contact is a standalone buyer without a company record, Salesforce creates a minimal Account record to satisfy the AccountId lookup requirement.

Source contacts marked as 'Uncontacted' or 'New Lead' with no associated deal activity route to Salesforce Lead. Once a lead has a qualifying deal or meeting logged, it transitions to Contact and Opportunity. The split is configurable based on the source's status pick-list values.

Property records require a Salesforce custom object (Property__c) with fields for address components, MLS number, listing price, property type, status, and days-on-market. The object has a lookup to the primary Account (seller) and a lookup to the listing Agent (Contact). We create the object definition and all fields during the pre-migration schema phase.

Source deals map directly to Salesforce Opportunities. The deal name becomes Opportunity Name, amount maps to Amount, close date maps to CloseDate, and stage maps to StageName. The source pipeline determines the Salesforce Sales Process and Record Type so stage pick-list values are scoped correctly per transaction type.

Each source pipeline becomes a Salesforce Sales Process keyed by a Record Type. Pipeline stages map to Opportunity Stage values, with probabilities and forecast categories re-applied. Stage-entered timestamps are preserved in a custom datetime field (Stage_Entered_Date__c) for reporting continuity. The key planning step is determining how many record types your Salesforce org needs — each distinct transaction workflow in the source requires its own Record Type with isolated stage values.

Agent commission percentages and split logic from the source deal record migrate to a custom Commission__c object with lookup to Opportunity and the agent Contact, or to custom fields on Opportunity (Agent_Split__c, Buyer's_Agent_Split__c). Rebate and referral fee tracking follows the same pattern.

Showings and appointments map to Salesforce Events with original start/end times and the related Property__c and Contact lookups preserved. Phone calls and emails map to Tasks with Type='Call' or Type='Email'. Written notes migrate to Salesforce Notes (not the legacy Note object) with the parent record reference intact.

Files attached to listings or deals in the source platform are downloaded and re-uploaded as Salesforce Files linked to the corresponding Property__c or Opportunity record. File size limits apply — Salesforce default is 25MB per file; larger files are chunked or linked via URL reference.

Source custom fields beyond the standard property attributes migrate as Salesforce custom fields on Property__c or Opportunity, following the __c naming convention. Pick-list fields with value restrictions are re-created as pick-lists in Salesforce; free-text fields become Text(255) or Long Text Area as appropriate.

Source agents with login access map to Salesforce Users resolved by email match. Agents in the source who are not Salesforce users at the time of migration are flagged and assigned to a fallback user or imported as Contacts if they represent external parties such as cooperating brokers.

Automated follow-up sequences, listing-status-change alerts, and agent drip campaigns do not transfer to Salesforce. FlitStack AI exports the source workflow definitions, trigger conditions, and action sequences as a structured reference document your Salesforce admin uses to rebuild equivalent logic in Flow or Apex.