Migrate from Property Minder to Microsoft Dynamics 365 Sales

Direct map. Dynamics 365 Sales Contact stores first name, last name, email, phone, and address. Owner and tenant contacts land as Contact records. Foreign keys to Account require Account to be created first in the migration sequence. All Contact fields are mapped directly; ensure that email addresses are unique to avoid duplicate detection issues.

Direct map to Account. Property attributes that have no native D365 equivalent — PropertyType__c, ListingStatus__c, PropertySize__c — are stored as custom fields on the Account record. PropertyMinder property IDs are preserved as SourcePropertyId__c for reconciliation. Custom fields are created during the pre-migration schema setup; verify that option set values match the source pick-list values to maintain data consistency.

Active listings become Opportunities linked to the Property Account. Opportunity.Amount holds the listing price. Opportunity.Stage maps to D365 Sales stage values; ListingStatus pick-list maps via value_mapping to stage names. Closed listings become Closed Won or Closed Lost Opportunities. During migration, ensure that the stage mapping aligns with your sales process; any unmatched statuses are logged for manual review and adjustment.

Owner name and contact details merge into two records: an Account for the owner's business entity and a Contact for the individual. Primary Owner links to Property Account via AccountId; secondary owners are stored as Account Contact Relationships. When an owner is both an individual and a business, we create both Account and Contact entries and link them via a parent Account relationship if needed.

Tenant records map directly to Contact. Tenant-specific fields — lease start, lease end, rent amount — migrate as custom fields on the Contact record. Each tenant Contact links to the Property Account via AccountId lookup. Custom fields are created as choice or date fields as appropriate; ensure that the lease start and end dates are stored in UTC to avoid timezone mismatches.

Units are not native to Dynamics 365 Sales CRM. We create a custom Unit__c table with fields for UnitId__c (text), UnitStatus__c (choice), Property__c (lookup to Account), RentAmount__c (currency), and SecurityDeposit__c (currency). Unit-to-Property link is a lookup relationship. The custom table also includes fields for SquareFootage__c (number) and PropertyType__c (choice) to capture detailed unit characteristics for reporting and analysis.

Leases require a custom Lease__c table in D365 Sales because neither Opportunity nor custom entities natively model lease agreement metadata. Fields include LeaseId__c (text), LeaseStatus__c (choice), Tenant__c (lookup to Contact), Property__c (lookup to Account), StartDate__c, EndDate__c, RentAmount__c, and SecurityDeposit__c. Additional fields such as MonthlyRent__c, LeaseTerm__c (choice), and DepositReturnDate__c may be added based on the source data richness to support comprehensive lease lifecycle reporting.

Listing activities, property updates, and tenant communications migrate as Tasks with Type='Property Activity'. Original timestamps, owners, and parent-record links (Property or Contact) are preserved. Rich-text notes become Note records attached to the parent Account or Contact. All Task records retain the original create date and assigned user, ensuring audit continuity and accurate activity history in the new CRM.

File attachments on Property, Listing, or Contact records are re-uploaded to Dynamics 365 Sales SharePoint integration or stored as Note attachments. File size limits apply — D365 default is 10 MB per file for SharePoint-backed storage. We perform a pre-migration file inventory to identify oversized files, compress where possible, and configure SharePoint library settings to accommodate the expected volume.

Property Minder custom objects migrate as D365 Sales custom tables. Dynamics 365 Sales Professional caps custom tables at 15; Enterprise allows unlimited. We surface the full list of custom objects before migration so your team can decide on licensing tier or consolidate objects.