Migrate from IDX Broker to Zoho CRM

IDX Broker contacts map 1:1 to Zoho CRM Leads. The contact's first name, last name, email, phone, and address fields carry over directly without transformation. The original IDX Broker contact ID is stored in the Source_System_ID__c custom field for delta-run deduplication and traceability back to the source system after migration completes.

If your IDX Broker setup uses the Contact object for clients who have already engaged, those records migrate as Zoho CRM Contacts (separate from Leads) to preserve lifecycle position. Contacts without deal history land directly; those with closed deals become Contacts linked to Accounts for full relationship hierarchy.

IDX Broker agent brokerages and company records map to Zoho CRM Accounts. Account Name, website, industry, phone, and billing address carry over as standard fields. Multi-agent brokerages with parent-child relationships use Zoho's Parent Account lookup field to preserve organizational hierarchy during migration.

IDX Broker stores property preferences—preferred property type, min/max bedrooms, min/max price, desired neighborhoods, MLS listing IDs of saved listings—as flattened lead properties. Zoho CRM has no native real-estate property-interest object, so FlitStack creates a Property_Interests__c multi-line text field (or a custom Property_Interests module if the client chooses) to store these values.

IDX Broker tracks individual saved property listings with address, MLS listing ID, status, and agent notes. Zoho CRM has no native property-listing object. FlitStack maps these to a custom Property_Listings__c module linked to the Contact, or flattens key fields (listing ID, address, status) into a Deals-based record if the client prefers to treat saved listings as potential transactions.

IDX Broker saves client search criteria (location, price range, property type, bedrooms, keywords) as structured lead records. Zoho CRM has no saved-search equivalent. FlitStack preserves the full search criteria as a long-text custom field (Saved_Search_Criteria__c) on the Zoho Lead so no buyer preference data is lost.

IDX Broker lead activities—calls logged, emails sent, property showings scheduled—map to Zoho CRM Tasks. The original activity timestamp, subject, and outcome are preserved. Call duration and meeting type (in-person showing vs. virtual tour) are stored in custom task fields if present in the source.

IDX Broker notes attached to leads migrate as Zoho CRM Notes linked to the corresponding Lead record. Rich-text formatting is preserved where possible during the transformation. Notes are associated to the migrated Lead using the original IDX Broker ID stored in the Source_System_ID__c field for traceability.

File attachments on IDX Broker leads (offer documents, client agreements, property PDFs) are re-uploaded to Zoho CRM's Attachments module linked to the corresponding Lead or Contact. File size limits apply—Zoho caps single attachments at 25 MB per file for most plans.

IDX Broker agent accounts are resolved by email match against Zoho CRM users. Unmatched agents are flagged before migration; your team either creates Zoho users first or assigns records to a fallback Zoho user. Agent display names map to Zoho's First Name + Last Name fields.

IDX Broker lead statuses (New Lead, Contacted, Showing Scheduled, Offer Made, Closed Won, Closed Lost) map value-by-value to Zoho CRM Lead Status picklist values. Custom statuses in IDX Broker require new picklist values to be created in Zoho before migration runs.

IDX Broker displays MLS listing data sourced from third-party MLS feeds—these records are not stored persistently in IDX Broker. FlitStack does not migrate MLS listing data; the listing content remains in the MLS system and IDX Broker re-connects to it post-migration. Only MLS listing IDs stored as saved-listing references on leads are preserved as custom fields.