Migrate from IDX Broker to HubSpot

IDX Broker contacts map 1:1 to HubSpot contacts. Name, email, phone, and address fields translate directly. IDX Broker's contact create/update timestamps are preserved as HubSpot custom properties since HubSpot's native CreatedAt is set at migration time. Owner resolution happens via email match against HubSpot users.

IDX Broker leads merge into HubSpot contacts. HubSpot has one contact object rather than separate contact and lead objects. The source lead status is preserved as a custom pick-list property in HubSpot, and lifecycle stage is set to 'lead' unless a more advanced stage was tracked in IDX Broker's extended fields.

IDX Broker brokerages and real estate companies map to HubSpot companies. Company name, domain, industry, phone, and address fields translate directly. If IDX Broker stores agent teams as companies, those map to HubSpot teams or companies depending on your target schema.

IDX Broker property records (MLS listings with addresses, prices, MLS numbers, statuses, bedroom/bath counts) require a HubSpot custom object. FlitStack creates the Property object in HubSpot with custom fields for MLS number, listing price, status (Active/Pending/Sold), property type, square footage, and year built. Each property is associated to the relevant contact via a many-to-many relationship.

IDX Broker saved searches are MLS-criteria-based alerts tied to the IDX website engine. HubSpot lists use contact-based criteria and cannot store MLS field logic. We preserve saved search criteria as a custom text property on the contact so your team can manually recreate matching lists in HubSpot.

IDX Broker agents resolve to HubSpot owners by email match. If an IDX Broker agent record has no matching HubSpot user, the record is flagged for your team to either invite the agent to HubSpot or reassign to a fallback owner before migration commits.

IDX Broker showing requests map to HubSpot tasks assigned to the relevant agent/owner. Task subject, property reference, requested date, and contact association are preserved. Original request timestamps and owner assignments carry over. If a showing references a property, the task links to the HubSpot Property__c custom object and task status reflects IDX Broker status (Scheduled, Completed, Cancelled), allowing your team to track showings in HubSpot.

IDX Broker notes on contacts, leads, and properties migrate to HubSpot engagement notes. Original timestamps, owners, and the parent record association (contact or property) are preserved. Notes attached to specific properties link to the corresponding custom Property object in HubSpot.

IDX Broker file attachments (property images, documents, PDFs) are downloaded and re-uploaded to HubSpot Files. Files are linked to the parent contact or Property record in HubSpot. HubSpot's 25MB per-file limit applies; large media files over this threshold are flagged for selective upload.

Any IDX Broker custom fields on contacts, leads, or properties translate to HubSpot custom properties. Field types map: text to single-line text, number to number, date to date/datetime, pick-list to pick-list. Enterprise-only IDX Broker custom objects translate to HubSpot custom objects following the same association rules as standard property objects.

IDX Broker lead source tracking (website form, MLS search, referral, etc.) maps to HubSpot's hs_analytics_source field on contacts. If your IDX Broker uses a custom lead source taxonomy, it migrates as a custom pick-list property and is mapped alongside the standard source.

IDX Broker tags on contacts and leads map to HubSpot tags. Tags are preserved as‑is; HubSpot’s tag model supports the same flat‑label structure that IDX Broker uses for contact classification. During migration, FlitStack AI imports tags exactly as they appear, preserving any hierarchical naming conventions you use. After migration, tags can be used in HubSpot workflows, lists, and reporting for segmentation and automation without any re‑tagging effort.