Migrate from Real Properties to Microsoft Dynamics 365 Sales

Direct 1:1 map. Dynamics 365 Contact records receive all Real Properties contact fields including name, email, phone, and address. Owner resolution matches Real Properties owner email to Dynamics 365 user email for OwnerId assignment. Contacts without a primary company link to a default 'Unassigned Account' record.

Direct 1:1 map. Real Properties company records become Dynamics 365 Accounts with all standard fields (name, address, industry, website). Parent-company hierarchies in Real Properties map to Account.ParentAccountId. Multi-contact companies collapse to one primary AccountId with additional contacts linked via Account Contact Relationships.

Real Properties listing data has no direct Dynamics 365 equivalent — property address, listing price, square footage, and listing status map to Opportunity with custom fields (Listing_Status__c, Square_Footage__c, Property_Type__c). Listing history timestamps become custom datetime fields for reporting continuity. Each property attribute requires a corresponding custom field on the Opportunity table, and the custom field manifest delivered during discovery specifies which fields your admin must pre-create.

Real Properties listing status values (Active, Pending, Sold, Withdrawn) map to a custom OptionSet field on Opportunity. Each status value requires explicit mapping to the corresponding Dynamics 365 picklist value. Probability and forecast category re-applied per status value to ensure pipeline reporting reflects the original Real Properties sales stage definitions accurately.

Real Properties transaction records map directly to Dynamics 365 Opportunities. Transaction amount becomes Opportunity.Amount, expected close date becomes CloseDate, and transaction owner maps to OwnerId via email resolution. Sales process stages map to Opportunity StageName values with value-by-value translation for accurate pipeline representation in the destination system.

Real Properties engagement records — calls, emails, meetings — map to Dynamics 365 Activities. Original timestamps, owners, and parent-record links (ContactId, regarding ObjectId) are preserved throughout the migration. Meeting duration and location fields map to corresponding Activity fields ensuring complete engagement history transfer.

Real Properties notes and listing attachments migrate as Dataverse Annotations. File attachments are downloaded and re-uploaded to Dynamics 365 / Dataverse; inline images in notes are extracted and rehosted as annotation file attachments. The 25MB per-file limit applies to each annotation record created in the destination environment.

Real Properties custom fields on listings — such as HOA fees, lot size, year built, MLS number — require new custom fields on the Opportunity table in Dynamics 365. We deliver a custom field creation manifest before migration so your admin can pre-create fields in the target environment.

Real Properties owner records resolve to Dynamics 365 SystemUser by email match. Unmatched owners are flagged before migration — your team either provisions Dynamics 365 users or assigns their records to a fallback owner. No record lands in Dynamics 365 without a resolved OwnerId.

Real Properties workflows, sequences, and automation rules do not migrate automatically — they require complete manual rebuild in Dynamics 365 using Power Automate or the classic workflow designer. Since workflow logic lives in proprietary Real Properties rule definitions, FlitStack exports workflow definitions as a structured reference document for your Dynamics 365 admin to use as a specification guide when rebuilding automations in the destination environment.