Migrate from The Real Estate Platform (REP) to Microsoft Dynamics 365 Sales

REP contacts migrate directly to Dynamics 365 Contact records. Each Contact receives the primary_agent_id from REP resolved to a Dynamics User via email match; secondary_agent_id becomes a custom Agent_Secondary__c lookup. Unmatched agents flag for manual assignment before the full run.

REP contacts flagged as 'Prospect' status with no associated transaction history route to Dynamics 365 Lead records rather than Contact. Routing to Lead keeps unconverted prospects out of the active Contact table while still enabling follow-up through the Dynamics sales cycle via lead scoring, assignment rules, and sales accelerator features.

REP companies map to Dynamics 365 Account records. The primary headquarters address populates Account.Address1 fields; any secondary mailing address populates Address2. Multi-office companies generate one Account per physical location, linked via ParentId to a master brokerage Account, preserving the REP office hierarchy in the Account structure.

REP Listings require a custom table in Dynamics 365 since no native equivalent exists. We create RealEstateListing__c with fields mirroring REP listing fields: address, price, mls_number, status, listing_agent (lookup to User), and listing_office (lookup to Team). A junction table ListingAccount__c links each listing to its owner Account.

REP Deals migrate to Dynamics 365 Opportunity records. The deal_name becomes Opportunity.Name, amount becomes Amount, close_date becomes ClosePotentialDate, and deal_status maps to Opportunity Stage via a value map. Each Opportunity links to its corresponding ListingAccount junction record via a custom Lookup_Listing__c field.

REP custom activity types map to Dynamics 365 standard activity entities: showing events become Appointment records with scheduled start and end times, offer submissions become Task records with a custom Type field set to 'Offer', and negotiations become Task records with Type='Negotiation'. All migrated activities receive a regardingobjectid linking them to the related Opportunity, Contact, or ListingAccount record to surface in the correct timeline.

REP Agent records resolve to Dynamics 365 User records by email. Active agents get User records with appropriate Security Roles assigned based on their REP role (Listing Agent, Buyer Agent, Team Lead). Inactive agents archive to a custom InactiveAgent__c table for historical reference.

REP Office records become Dynamics 365 Teams. Each team receives a Team Type attribute (Regional Office, Franchise Office, or Branch) corresponding to the REP office classification, and members are added by linking existing Dynamics User records whose email domain matches the REP office identifier. Teams in Dynamics enable territory-based security boundaries and aggregated reporting by office or region.

REP supports multiple agents per listing — co-listing agents, buyer agents, and showing agents are distinct roles. We create a ListingAccount__c junction table with Listing (lookup to RealEstateListing__c), Account (lookup), and Role (custom picklist values: ListingAgent, BuyerAgent, ShowingAgent) to preserve the full agent network on each property. This ensures every agent association survives the migration as a queryable record in Dynamics 365.

REP security hierarchies and custom page layouts do not transfer to Dynamics 365. We document the REP permission structure as a role-mapping reference so your Dynamics 365 admin can re-create Business Unit boundaries, Security Roles, and form customizations in the destination environment.

REP drip campaigns, listing-alert automations, and agent task triggers have no Dynamics 365 equivalent. We export the rule definitions as structured JSON including trigger conditions, action sequences, and timing logic. Your admin uses this as a rebuild spec for Power Automate flows.