Migrate from AgentLocator to Microsoft Dynamics 365 Sales

AgentLocator contacts that have not yet converted to a client relationship map directly to Dynamics 365 Sales Lead. The Lead entity captures initial inquiry data, source attribution, and agent assignment. We preserve the original AgentLocator lead-create timestamp as a custom datetime field since Dynamics 365 Sales CreatedOn reflects the migration date.

AgentLocator contacts marked as clients or with closed transactions map to Dynamics 365 Sales Contact. The Contact entity links to the primary Account (brokerage or individual account). AgentLocator contact phone numbers migrate as Phone and MobilePhone on the Contact record.

AgentLocator brokerage or company records map to Dynamics 365 Sales Account. For solo agents, the account may be the agent's own name; for team brokerages, the brokerage firm is the Account with individual agents as Contacts linked via AccountId. Website, industry (Real Estate), and address fields map directly.

AgentLocator saved searches (city, price range, property type filters) have no direct Dynamics 365 Sales equivalent. We create a custom SavedSearch__c table linked to the Lead or Contact, storing filter criteria as text fields and last-modified date. This preserves the lead's expressed property interest for agents to reference after migration.

AgentLocator listing views and viewing requests represent which properties a lead has expressed interest in. We create a ListingInterest__c custom entity linked to Contact and to an Opportunity or Note containing property details (address, MLS ID, price). MLS IDs and property statuses migrate as custom text fields since Dynamics 365 has no native listing entity.

AgentLocator pipeline stages (New Inquiry, Contacted, Showing Scheduled, Offer Made, Under Contract, Closed) map to Dynamics 365 Sales Opportunity StageName values. We create stage values matching the source names and set probability percentages per stage. Each stage value is created under the default Business Process Flow unless custom business process flows are required.

AgentLocator call logs, SMS history, and email activities migrate as Dynamics 365 Sales Task records. Each Task links to the parent Contact or Lead via RegardingObjectId. Activity type is stored in the Type or Category field. Original timestamps are preserved as ActualEnd for completed activities.

AgentLocator notes on contacts and listings migrate as Dynamics 365 Sales Note (annotation) records. Notes attach to the parent Contact, Lead, or Opportunity. File attachments are downloaded from AgentLocator and re-uploaded as Dynamics 365 Notes or SharePoint-connected document libraries if the organization uses Teams/SharePoint integration.

AgentLocator tags used to segment contacts (buyer, seller, investor, past-client) migrate as a semicolon-delimited text field on the Contact or as Dynamics 365 Topics if the Sales Insights module is active. Tags used for agent assignment are handled separately via OwnerId resolution by email match.

AgentLocator agent users are matched to Dynamics 365 Sales users by email address. Unmatched agents are flagged before migration; records for unmatched agents are assigned to a designated fallback owner (broker or admin). This ensures no record lands without a valid OwnerId in Dynamics 365.

AgentLocator custom fields specific to real estate (MLS ID, property type, listing status, preferred neighborhoods) migrate as new_ prefixed custom fields on the Contact or Lead table in Dynamics 365 Sales. Field data types are matched: pick-lists become OptionSets, numeric fields become Decimal or Whole Number, text fields become Single-Line Text.

AgentLocator email and SMS templates do not migrate. They are exported as reference files so the Dynamics 365 admin can recreate them as Email Templates or Power Automate-approved templates. Template logic and personalization tokens require manual mapping to Dynamics 365 token syntax.

AgentLocator automated drip campaigns and lead nurture sequences have no direct equivalent in Dynamics 365 Sales. We export the campaign definition (trigger, steps, delays, content references) as a rebuild reference document. Rebuilt sequences are implemented in Power Automate or Sales Insights sequences after go-live.

AgentLocator IDX and MLS feed data is external to the CRM and not migrated as CRM records. Listing inventory typically lives in a separate MLS system. We document the MLS ID linked to each contact's saved search so the broker can reconnect listing search tools post-migration with a compatible IDX provider.