Migrate from CRM for real estate to Microsoft Dynamics 365 Sales

Direct 1:1 mapping. CRM for Real Estate contacts migrate to Dynamics 365 Contact records preserving email, phone, address, and role. Primary company resolves via the AccountId lookup — contacts without a primary company attach to a default 'Unassigned' Account record.

CRM for Real Estate companies map to Dynamics 365 Accounts. Company name, website, industry, employee count, and annual revenue map directly. Parent-company hierarchies migrate to the Account.ParentId field; circular references are flagged before the run. Any secondary company relationships beyond the primary assignment surface as Account Contact Relationship records in Dynamics 365. Multi-branch brokerages should confirm during schema design whether branch offices represent separate Account records or divisions within a single Account.

CRM for Real Estate property records have no native Dynamics 365 Sales equivalent. FlitStack creates a custom crXXX_Property__c Dataverse table with fields for address, property type (OptionSet), listing status, price, square footage, beds/baths as whole numbers, and an Account lookup to the associated seller account.

Active listings from CRM for Real Estate map to a crXXX_Listing__c custom entity linked to the Property record. Closed transactions become Opportunities with amount from the sale price and close date from closing date. Listing status values (Active, Pending, Sold) map via OptionSet value-mapping.

CRM for Real Estate transactions migrate as Dynamics 365 Opportunities. Sale price maps to Amount, closing date to CloseDate, and the associated property lookup to crXXX_Property__c. Commission splits and referral fees become custom decimal fields (crXXX_AgentCommission__c, crXXX_ReferralFee__c) on the Opportunity.

CRM for Real Estate agent and owner IDs resolve by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration; you either invite them to Dynamics 365 first or assign their records to a fallback owner. Source agent ID preserved in crXXX_SourceAgentId__c for audit continuity.

CRM for Real Estate showing records track prospect, property, date, and outcome. FlitStack creates a crXXX_Showing__c custom activity entity with ActivityParty lookups for prospect and agent, scheduled datetime, and outcome pick-list. If your team prefers generic activity tracking, showing data lands as Task records with Type='Showing' and property linkage in a custom field. This choice affects how agents filter their daily activity views.

CRM for Real Estate open house records migrate as a crXXX_OpenHouse__c custom entity or Task records. Property lookup, event date, prospect count, and lead follow-up status map to custom fields on the entity. Each open house links to the associated property via the crXXX_Property__c lookup and to the hosting agent as the owner. If your brokerage tracks attendee lists, those migrate as notes or related Contact associations on the open house record. The decision between a custom entity and Task routing should align with how your team reports open house performance in Dynamics 365 Sales dashboards.

CRM for Real Estate calls map to Dynamics 365 PhoneCall activities with Direction, Subject, and regarding ObjectId to the parent Contact or Property. Emails migrate as Email activities with Regarding set to the linked record. Notes migrate as Annotation records preserving body text and attachment links.

CRM for Real Estate file attachments on properties, contacts, and transactions download and re-upload to Dynamics 365 Notes attachments. If your tenant uses SharePoint integration, FlitStack routes document-type attachments to the SharePoint document location linked to the parent Account or crXXX_Property__c record.

CRM for Real Estate leads migrate directly to Dynamics 365 Leads with source, status, rating, and estimated value preserved. Owner resolution applies same email-match logic used for agents. Lead scoring from CRM for Real Estate migrates to crXXX_LeadScore__c custom field.

All CRM for Real Estate custom fields (agent_id, syndication_flags, referral_source, etc.) migrate to custom fields on their target Dynamics 365 entity, prefixed with your publisher solution prefix. Pick-list custom fields require OptionSet value-mapping; text fields are created as SingleLine.Text with matching length constraints.