Migrate from BrightDoor to Microsoft Dynamics 365 Sales

BrightDoor homebuyers map directly to Dynamics 365 Contacts. The primary company link in BrightDoor is the community; in Dynamics 365 this becomes a lookup to the community Account record. BrightDoor agent associations on the contact become a custom Agent_Role__c field or Contact Relationships in Dataverse.

BrightDoer's community object maps to Dynamics 365 Account because both represent organizational entities. Parent-community and sub‑community hierarchies in BrightDoor map to Account.ParentAccountId, with the parent migrated first to ensure referential integrity. Community phase (Phase 1, Phase 2, etc.) migrates as a custom picklist field on the Account record, and the community’s address and manager role are stored in the same Account fields or via custom fields for reporting and routing.

Dynamics 365 Sales has no native lot object. We create a custom Lot Dataverse table with fields for Lot_Number__c, Community__c (lookup to Account), Lot_Status__c (picklist: Available, Under Contract, Sold, Reserved), Square_Footage__c, Base_Price__c, and Elevation__c. Each Lot record links to the BrightDoor lot by Source_System_ID__c.

BrightDoor buyer registrations (the record of a prospect selecting a community or lot) map to Dynamics 365 Opportunity. The Opportunity's Account lookup points to the community; the Lot lookup points to the custom Lot entity. Opportunity StageName is remapped from BrightDoer's prospect lifecycle to the Dynamics 365 stage picklist: Prospecting, Qualification, Proposal, Negotiation, Closed Won.

BrightDoor tracks lot status transitions (Available → Under Contract → Sold) with timestamps. Dynamics 365 Opportunity has a stage-entered timestamp but no per-status history. We preserve the full lot-change log as Lot_Status_History__c (text area) and map each status change to a corresponding Opportunity Stage entry in Dynamics 365.

BrightDoor agents are resolved by email match against Dynamics 365 licensed users. Unmatched agents are flagged before migration and assigned to a fallback owner. Agent role in BrightDoor (Listing Agent, Buyer's Agent, Community Manager) migrates as a custom Agent_Role__c field on the Contact record or on the Opportunity via Opportunity_Agent_Role__c.

BrightDoor prospects who have not yet registered or selected a lot map to Dynamics 365 Lead. Lead Source, estimated close date, and budget fields map to the corresponding Dynamics 365 Lead attributes. Conversion to Contact and Opportunity happens in Dynamics 365 post-migration using standard Lead conversion.

BrightDoor call logs, meeting notes, and general activity records map to Dynamics 365 Tasks. The regarding_objectid links each task to the corresponding Contact or Opportunity. Original timestamps, owners, and note body text are preserved. BrightDoor touchscreen interaction logs are not migrated — those are session-specific and non-transferable.

BrightDoor file attachments on community, lot, or contact records are re-uploaded to Dynamics 365 SharePoint integration or as Note attachments. File size limits per the destination environment apply. Floor plan PDFs and lot maps are stored in SharePoint document libraries linked to the Lot custom entity.

BrightDoor allows custom properties per object (e.g., HOA_Fee__c on Lot, Community_Amenities__c on Account). Each custom property is created as a custom field on the mapped Dynamics 365 entity. Field type mapping: text → String, number → Number, date → DateTime, picklist → Picklist. Custom properties are inventoried during discovery before migration runs.

BrightDoer's interactive touchscreen experience and HomeRover live-tour app configuration have no Dynamics 365 equivalent. These are application-level settings, not data records. We do not migrate them. FlitStack exports a configuration export reference for your IT team to use when rebuilding interactive kiosk and virtual-tour flows in a separate application.