Migrate from IDX Broker to Twenty CRM

IDX Broker stores leads as contacts with first name, last name, email, phone, and address. FlitStack maps these directly to Twenty's People object. Owner assignment in IDX Broker (the agent assigned to the lead) maps to Twenty's assignee relation — your workspace members must be invited to Twenty before migration so the assignee relation resolves correctly.

IDX Broker contacts are often associated with a brokerage or company name. FlitStack creates a Companies record and links the People record via the companyId relation in Twenty. If a contact has no company, the company field is left blank — no placeholder company is created.

IDX Broker does not have a native Opportunity or pipeline object — leads are tracked as flat contact records. If your team has been using a workaround in IDX Broker to flag deal stage (e.g., a custom text field for 'stage'), FlitStack migrates that value as a custom field on the People record. A dedicated Opportunities object should be created in Twenty for any pipeline tracking you intend to rebuild.

IDX Broker's lead notes are free-text records attached to contacts. FlitStack migrates these as Note records in Twenty, linked to the corresponding People record by email or contact ID. Note body, create date, and the note author (from IDX Broker user data) are preserved. Twenty's Note object supports attaching notes to People, Companies, and Opportunities.

IDX Broker captures buyer saved searches as a native lead feature — this is a key source of prospect intent data that IDX Broker does not expose as a standard CRM field. FlitStack migrates saved search criteria as a custom text field (Saved_Search_Criteria__c) on the People object so agents can see what properties a lead was interested in without re-creating that context manually.

IDX Broker assigns leads to agents by email. FlitStack matches the owner email against Twenty workspace members. If a member does not yet exist in Twenty, FlitStack flags the record for manual assignment — your admin must invite that agent to Twenty before the migration runs so no assignee relation is left unresolved.

IDX Broker records the timestamp when a lead first submitted an inquiry. This is not a standard Twenty field. FlitStack creates a custom datetime field (First_Inquiry_Date__c) on the People object and populates it from IDX Broker's createdate field, preserving the original lead capture date for age-of-lead reporting in Twenty.

IDX Broker tracks lead source (e.g., organic search, paid ad, referral) but this is a custom or meta field in the IDX system. FlitStack migrates the lead source value to a custom select field (Lead_Source__c) on the People object, with pick-list options matching the source values found in your IDX Broker export.

IDX Broker captures which MLS listings a lead viewed or saved. Because Twenty has no native IDX integration, FlitStack stores listing references as a custom text field (Last_Viewed_Listings__c) on the People record. Agents can use this field to re-trigger listing alerts or cross-reference property interest with an external MLS tool after migration.

If your IDX Broker setup uses any custom text fields, pick-list fields, or checkboxes on contact records, FlitStack creates matching custom fields in Twenty's Settings → Data Model before import. Select-type fields require value-by-value mapping if the pick-list options differ between platforms. All custom fields must exist in Twenty before the CSV import step runs — FlitStack handles field creation as part of the pre-migration schema setup.