Migrate from PropertySimple to Microsoft Dynamics 365 Sales

PropertySimple contact records map 1:1 to Dynamics 365 Sales Contact. Email, phone, name, address, and owner resolve by email match to a Dynamics 365 user. PropertySimple contacts without a company association land as Contacts on a default 'Unassigned' Account record, which your admin defines in Dynamics 365 before migration runs.

PropertySimple stores a company name on the contact record. We split this into a Dynamics 365 Account record (created first, by Company Name) and a Contact record with AccountId lookup pointing to it. If the same company appears on multiple contacts, only one Account record is created and all contacts reference its AccountId.

PropertySimple brokerage and company records map directly to Dynamics 365 Sales Account. Company name becomes Account.Name, website becomes Account.Website, and industry defaults to 'Real Estate' unless a specific value is set. Billing address and shipping address fields on the company map to Account.Address fields.

PropertySimple leads that have not yet been converted to a client record route to Dynamics 365 Sales Lead. LeadSource maps from PropertySimple's source-channel field (e.g., 'ZIP Ad Click', 'Portal Inquiry'). Status pick-list values are mapped value-by-value; custom lead statuses in PropertySimple require value-mapping setup in Dynamics 365 before migration.

PropertySimple has no Dynamics 365 equivalent for real estate listings. We create a custom RealEstateListing__c table in Dynamics 365 with fields for Address, City, State, ZipCode, ListingStatus, ListPrice, ListingAgent (lookup to Contact), and ListingDate. This table is loaded after Account and Contact so foreign keys resolve correctly.

PropertySimple links a listing to a primary agent contact. We map this as a lookup on RealEstateListing__c to the Contact record created from PropertySimple. The OwnerId field is set from the matched Dynamics 365 user by email. Secondary agents are stored as a custom multi-select or separate junction object depending on your listing workflow.

PropertySimple's ZIP-code exclusivity zones have no direct Dynamics 365 equivalent. We create a custom ZIPCodExclusivity__c field on Account (for broker-level zones) or on a Territory__c custom table (for agent-level zones). Each PropertySimple ZIP record becomes one row in this table, with a link to the owning Contact or Account.

PropertySimple ad campaigns with click-through and cost data migrate to Dynamics 365 Campaign records with total actualcost and numberofleads captured in custom fields. Individual listing ad performance (impressions, clicks, cost per click) is stored as a related custom table (ListingAdPerformance__c) linked to the Campaign.

PropertySimple client notes and email interactions map to Dynamics 365 Email (activity) records with regardingobjectid pointing to the Contact or Account. Original timestamps and subject lines are preserved. Rich-text formatting in PropertySimple notes converts to Dynamics 365 Note (annotation) body text.

PropertySimple AI follow-up sequences and automated client messaging have no Dynamics 365 Sales native equivalent. We export the sequence definition (trigger conditions, message order, timing) as a JSON reference document. Your Dynamics 365 admin rebuilds these in Power Automate or Dynamics automated processes using that export as the functional spec.

PropertySimple's automated social media posting and listing promotion scheduling do not transfer to any Dynamics 365 entity. These automations must be rebuilt using Power Automate templates that trigger SharePoint or third-party social connectors. We document the current posting cadence and triggers before migration so the rebuild is scoped accurately.

PropertySimple users and agent accounts resolve to Dynamics 365 Sales SystemUser records by email address match. Unmatched PropertySimple users are flagged before migration so your team can create corresponding Dynamics 365 accounts or assign their records to a fallback owner. OwnerId on every migrated record references the resolved SystemUser.