Migrate from The Real Estate Platform (REP) to Salesforce Sales Cloud

REP contacts migrate directly to Salesforce Contacts. Most REP contacts have an associated company — the primary company becomes the Contact's AccountId lookup. REP contacts without a company link get attached to a default 'Unassigned Account' placeholder record so Salesforce's AccountId requirement is satisfied.

REP companies map to Salesforce Accounts. REP's parent-child company hierarchy uses a Parent_Company_ID field that translates to Salesforce's ParentId lookup, preserving the organizational structure. Multi-company contacts collapse to one primary AccountId plus Account Contact Relationships for N:N associations, ensuring each contact links to the correct parent organization.

REP leads that haven't been converted to contacts map directly to Salesforce Leads. Lead source, status, and rating fields map directly. Unqualified leads that should have been contacts are flagged before migration so you can re-route them to the Contact path.

REP listings have no Salesforce standard equivalent — we create a custom Property__c object with fields for street address, city, state, zip, listing price, property type, square footage, lot size, year built, listing status, and MLS number. The custom object includes a lookup to the listing agent's User record and to the seller Account.

REP transactions map to Salesforce Opportunities. Deal value maps to Amount, close date maps to CloseDate, and REP transaction stage maps to Salesforce StageName via value mapping (New Lead → Prospecting, Under Contract → Proposal/Price Quote, Closed Won → Closed Won, etc.).

REP's deal stage values are mapped one-by-one to Salesforce Opportunity StageName values. Stage probability is re-applied per Salesforce's standard stage-folder model. For transactions with custom stage labels (e.g., 'Inspection Complete', 'Appraisal Ordered'), we create custom Opportunity Stage values scoped to a Real Estate record type.

REP offices become Salesforce Accounts positioned as hierarchy nodes under a top-level Brokerage Account. This preserves the reporting relationship — regional managers can use Salesforce's Account Hierarchy feature to see all offices and agents under their region without needing Territory Management configuration.

REP agents who need Salesforce platform login become Salesforce Users matched by email. Agents who only need CRM visibility as external contacts (e.g., co-listing agents from other brokerages) become Contacts with a custom Agent_Role__c pick-list and license number stored in a custom field.

REP regions map to Salesforce Territories, which require Territory Management to be enabled in your Salesforce org. Each REP region becomes a Territory with associated zip codes, and agents are assigned to the appropriate Territory so regional managers get filtered pipeline views. If your Salesforce edition doesn't include Territory Management, regions fall back to a custom Region__c pick-list on the User record.

REP file attachments on listings, contacts, and transactions are downloaded and re-uploaded as Salesforce Files attached to the corresponding Property__c, Contact, or Opportunity record. File size limits (25MB default per file in Salesforce) are respected — larger files are flagged for manual handling.

REP calls map to Salesforce Tasks with Type='Call', emails to Tasks with Type='Email', meetings to Events with original start and end times preserved, and notes to Salesforce Notes. Original timestamps and owner assignments are migrated so activity history is complete in Salesforce for reporting continuity.

REP's white-label configuration often includes broker-specific custom objects (e.g., commission splits, referral agreements, showing requests). These map 1:1 to Salesforce custom objects. Custom object relationships that use REP's N:N model need junction objects in Salesforce — we surface these in the migration plan before the full run.