Migrate from Realpage to Microsoft Dynamics 365 Sales

RealPage Residents map to Dynamics 365 Contacts. We preserve the original ResidentID as Source_System_ID__c for traceability and delta-run de-duplication. Active residents (lease status = current) land as Contacts; former residents with ended leases map to Contact records with Lease_Status__c = Former.

RealPage residents without a signed lease — inquiry-stage prospects or waitlisted applicants — route to Dynamics 365 Leads. The split happens during migration based on lease status field value. Lead source defaults to 'RealPage Migration' for filtering in Dynamics reports.

RealPage Properties map to Dynamics 365 Accounts. Property address fields map to the Account address compound field. Property type (multifamily, commercial, student) maps to Account Type pick-list. We preserve the PropertyID as Source_System_ID__c for Dataverse relationship integrity. The mapping also includes a cross-reference field for portfolio-level reporting.

RealPage Units have no direct Dynamics 365 equivalent — Accounts represent buildings, not individual units. We create a custom Unit__c table in Dataverse with a lookup to the parent Account (Property). Unit_Number__c, Bedrooms__c, Bathrooms__c, Square_Footage__c, and Market_Rent__c migrate as custom fields on this entity.

RealPage Leases map to Dynamics 365 Opportunities because both represent a revenue-generating agreement with a lifecycle (inquiry → application → signed → expired/renewed). We attach custom fields: Lease_Term_Start__c, Lease_Term_End__c, Monthly_Rent__c, Security_Deposit__c, and Lease_Status__c. StageName defaults based on lease status: 'Lease Signed' for active, 'Lease Expired' for ended.

RealPage Payment records have no native Dynamics 365 equivalent. We create a Payment__c custom table in Dataverse with a lookup to the Contact (resident) and a lookup to the Opportunity (lease). Fields include Payment_Date__c, Amount__c, Payment_Method__c, and Transaction_Reference__c. Payment history enables revenue reporting in Dynamics Power BI dashboards.

RealPage Work Orders map to Dynamics 365 Cases because both track service requests with status, priority, and assignment. We transform Work_Order_Number__c, Priority__c (mapped to Case Priority pick-list), Description__c, and Unit_Lookup__c. Vendor assignments map to the Case's Account lookup when a vendor is linked.

RealPage Vendors map to Dynamics 365 Accounts with Account Type = 'Vendor'. Trade_Category__c custom field preserves the vendor's trade (HVAC, plumbing, electrical, etc.). Vendor contact information migrates as related Contact records under the vendor Account. Vendor contracts and service-level agreements are preserved as related notes for reference.

RealPage file attachments (lease agreements, vendor contracts, maintenance photos) re-upload to Dynamics 365 Notes attached to the relevant record. We preserve original file names and created timestamps. File size limits apply per Dataverse constraints (10MB per note by default). File metadata such as created by and last modified dates are retained.

RealPage property managers and owners resolve to Dynamics 365 Users by email match. Unmatched owners are flagged before migration for your team to either invite to Dynamics 365 or assign to a fallback user. OwnerId on Accounts and Cases reflects the resolved mapping.

RealPage custom properties on any object migrate as Dataverse custom columns. We create the field in the appropriate table (Contact, Account, Opportunity, Case) using the same data type where possible. Multi-select pick-lists in RealPage map to Choice columns in Dataverse.