Migrate from IDX Broker to Microsoft Dynamics 365 Sales

IDX Broker contacts split by listing association and role: leads without a closed listing become Dynamics 365 Leads; agents and brokers with active listings become Contacts. Email and phone map directly; firstname and lastname resolve to the Name fields on each table. Unmatched contacts are staged in a custom IDX_StagedContact__c table for admin review.

IDX Broker listings have no direct equivalent in Dynamics 365 Sales. FlitStack creates a custom RealEstateListing__c table in Dataverse with fields for MLS number, price, status, bedrooms, bathrooms, square footage, lot size, year built, property type, and image URL list. The table links to the listing agent via OwnerId and to the associated office Account via AccountId__c lookup.

IDX Broker agents map to both a Contact record (for visibility on listings) and a SystemUser record (so OwnerId lookups resolve correctly on RealEstateListing__c). Agent ID from IDX Broker is stored as Agent_ID__c on both the Contact and the RealEstateListing__c record to maintain traceability back to the source.

IDX Broker offices map directly to Dynamics 365 Accounts. Office name becomes Account Name; address fields map to the standard address compound on Account. Agents in IDX Broker who belong to an office get their Contact record linked via the ParentAccountId lookup so team hierarchy is visible on the Account page.

IDX Broker stores contact address as a single string. FlitStack parses the string using common real estate address formats and populates AddressLine1, AddressLine2, City, StateOrProvince, PostalCode, and Country on the Contact record. Unparseable addresses are preserved in Address_Line_Raw__c as a custom text field for manual correction in Dynamics.

Listing street address on IDX Broker is parsed into AddressLine1, City, StateOrProvince, and PostalCode on the custom RealEstateListing__c table. The parsed components enable Dynamics 365 address validation, reporting, and proximity searches using standard address fields. Full address text is also preserved in Listing_Full_Address__c to support geocoding or map integrations after migration. If parsing encounters unusual formatting, the raw value remains available in Listing_Full_Address__c for manual correction.

IDX Broker listing statuses (Active, Pending, Sold, Withdrawn, Expired) map to a custom picklist on RealEstateListing__c. Each value is mapped one-to-one by label. Probability fields on Opportunities do not automatically update from listing status — that logic must be added via a Power Automate flow after migration.

Agent email is the key resolution field for matching IDX Broker agents to existing Dynamics 365 users. If a SystemUser with the matching InternalEmailAddress exists, the Agent record links directly. If not, a new SystemUser is provisioned and a Contact record is created simultaneously to preserve the agent's display name and contact details.

Dynamics 365 sets CreatedOn at record creation time in the destination, which may differ from the original IDX Broker create date. Original listing create and update timestamps are preserved as custom datetime fields (Listing_Created_Date__c and Listing_Updated_Date__c) for reporting continuity and audit purposes.

IDX Broker image URLs are stored as a comma-separated list in ImageURLs__c on the RealEstateListing__c record. Images are not re-uploaded to Dynamics 365 native storage by default — the URLs are preserved as a reference field. If re-hosting in SharePoint or Azure Blob is required, that can be scoped as an add-on step.