Migrate from Property Raptor to Microsoft Dynamics 365 Sales

Property Raptor Contact maps directly to Dynamics 365 Sales Contact. A primary Company association is required in Dynamics 365 — contacts without a linked company land on a placeholder Account and must be re-associated manually or via a post-migration cleanup script.

Property Raptor Company maps to Dynamics 365 Account. Company hierarchies (parent and subsidiary relationships) map to the Parent AccountId field. Multi-company contact associations in Property Raptor collapse to one primary AccountId per contact in Dynamics 365, with secondary associations stored in Account Contact Relationships.

Property Raptor listings — representing a property under offer or sale — map to Dynamics 365 Opportunity. Listing-specific attributes (property address, price, bedrooms, square footage, portal source) become custom columns on Opportunity (new_PropertyAddress, new_ListingPrice, etc.) since Dynamics 365 has no native property object. Each listing portal status flag maps to a value-mapped pick-list.

Property Raptor Lead maps directly to Dynamics 365 Lead. Lead status pick-list values require value-mapping against the destination status optionset. Any Property Raptor lead score property migrates as a custom Number field (new_LeadScore__c) since Dynamics 365 has no native lead scoring engine.

Property Raptor stores which portal a listing originated from (PropertyFinder, Bayut, Rightmove, Zoopla). Since Dynamics 365 has no portal-native field, we create a new_PortalSource option-set field on Opportunity and map each source string to an integer value in the set. Portal listing IDs map to a new_PortalListingId text field for reference.

Property Raptor engagement activities map to Dynamics 365 activity entities: calls and emails to Task with Type='Phone Call' or 'Email', meetings to Appointment, and notes to Note. Original timestamps, owners, and parent-record links (contact or opportunity) are preserved. Activity-party relationships resolve to Dynamics 365 Contact or Lead records by email match.

Property Raptor files attached to contacts, companies, or listings are downloaded and re-uploaded to the Dynamics 365-connected SharePoint document library (enabled via the native SharePoint integration). If SharePoint is not configured, files attach to Note records. Maximum file size limits of the destination SharePoint library apply.

Property Raptor custom fields that capture real-estate-specific data (property type, furnishing status, availability date, strata lot number) map to new_ custom columns on the relevant entity in Dynamics 365. Field type parity is maintained — text to text, number to whole number or decimal, date to datetime. Any Property Raptor custom fields that have no Dynamics 365 equivalent are flagged as new_SourceCustomFieldName and preserved for admin review.

Property Raptor owner IDs are resolved against Dynamics 365 users by email address match. Unmatched owners are flagged before migration with a resolution report — your team either creates a corresponding Dynamics 365 user or assigns records to a designated fallback user. No record migrates without a resolved OwnerId.

Property Raptor tracks listing status per portal (Active, Under Offer, Sold, Withdrawn). Each status value maps to a corresponding integer in a new_ListingStatus option-set created on Opportunity. If your team uses additional statuses beyond the standard set, those are added to the option-set before migration runs.