Migrate from IDX Broker to Salesforce Sales Cloud

IDX Broker contacts with lifecycle stage Lead or Unknown route to Salesforce Lead. Contacts with lifecycle stage Customer route to Salesforce Contact. The split happens at migration time based on the source lifecycle value, and the original stage progression dates are preserved in custom datetime fields on both Lead and Contact.

IDX Broker company records map directly to Salesforce Account. Company hierarchies (parent / child relationships) are preserved using Salesforce's Parent Account field. A circular reference check runs before migration to flag any loops. IDX Broker companies without contacts attach to a default placeholder Account.

IDX Broker deal records do not map directly to any Salesforce standard object because IDX Broker uses deals to track offer status, not a pipeline stage. We map them to Salesforce Opportunity with a custom pick-list field for deal status (Active, Offer Made, Under Contract, Closed). The Opportunity StageName is set to a default value during migration and adjusted per record type after go-live.

IDX Broker listing records require a Salesforce custom object because Salesforce Sales Cloud has no native property or MLS listing concept. We create Property__c as a custom object with fields for MLS Number (MLS_Number__c), Property Status (Property_Status__c), Days on Market (Days_On_Market__c), List Price (List_Price__c), and Beds/Baths/SqFt (Beds__c, Baths__c, SqFt__c). Each Property__c record links to the listing's primary contact via a lookup field.

IDX Broker agent records do not exist as a standard Salesforce object. Agents are matched to Salesforce users by email address. If a matching Salesforce user does not exist, the agent is flagged before migration and either invited to Salesforce or their IDX Broker records are assigned to a fallback owner. The original agent ID is stored as Agent_ID__c on migrated records.

IDX Broker showing request records map to Salesforce Task. The Task Subject carries the showing request detail, Type is set to 'Showing', and the related Property__c lookup is populated from the IDX Broker listing association. Original timestamps and the requesting contact's ID are preserved.

IDX Broker offer submissions map to Salesforce Task with Type = 'Offer' and Subject carrying the offer detail. The amount offered from IDX Broker is stored as a custom number field on the Task. The task links to both the contact and the Property__c record so the full offer context is traceable in Salesforce.

IDX Broker engagement logs (emails, calls, meetings) map to Salesforce Tasks (for calls and emails) and Events (for meetings). Original timestamps, activity type, and owner assignment are preserved. Meetings preserve start and end times as Salesforce Event fields. Call duration and email subject lines are stored in Salesforce Task fields where applicable.

IDX Broker notes map to Salesforce Notes (not the legacy Note object — we use the modern Notes object). Rich-text formatting is preserved where possible. File attachments are downloaded from IDX Broker and re-uploaded to Salesforce Files, associated with the related contact or property record. File size limits of 25 MB per file in Salesforce apply.

Any IDX Broker custom fields on contacts, companies, listings, or deals that have no Salesforce standard equivalent are created as custom fields on the mapped Salesforce object. Field type is matched (text, number, pick-list, date) during the mapping phase. If the custom field uses a pick-list in IDX Broker, the same values are replicated in Salesforce. Custom fields are always suffixed with __c per Salesforce convention.