Migrate from ResMan to Microsoft Dynamics 365 Sales

ResMan tenant records map directly to D365 Contacts. Each tenant's name, email, phone, and address fields align field-for-field. Primary property association migrates as Contact.AccountId lookup — requires the Account (Property) to exist first. Secondary property associations (tenants with multiple units) surface as Account Contact Relationships in D365.

ResMan properties map to D365 Accounts using property name as Account Name, address fields as Account Address, and property type (multifamily, affordable, mixed-use) as Industry or a custom pick-list. ResMan parent-property hierarchies (portfolio → property) map to Account.ParentId for portfolio-level roll-up reporting in D365.

ResMan leases have no direct D365 equivalent — leases are mapped to Opportunities with a custom Lease_Details__c table linked via Opportunity.LeaseDetailsId__c lookup. The Opportunity represents the lease lifecycle (lease_start to lease_end), with Amount = monthly_rent and CloseDate = lease_end_date. D365 Sales Processes and Opportunity Stages are used to model lease states (Active, Renewal Pending, Expired, Terminated).

Because D365 has no native lease entity, FlitStack creates a Lease__c custom table in Dataverse to store ResMan lease fields that don't fit Opportunity — lease_type (Market Rate, Section 8, LIHTC, Project-Based Voucher), deposit_amount, proration_amount, lease_status, and renewal_option_count. The Lease__c table links to the Contact (tenant) and Account (property) via lookups.

ResMan units have no D365 equivalent — each unit (apartment, townhome, etc.) is created as a Unit__c custom table record linked to the Account (property) via Property__c lookup. Unit fields mapped: unit_number (Name), beds, baths, sqft, market_rent, unit_status (Occupied, Vacant, Under Maintenance). Opportunity (Lease) links to Unit__c via Lease__c.UnitId__c to preserve the unit-to-lease relationship.

ResMan payment records are too granular for D365 native objects — FlitStack creates D365 Task records per payment with Subject = 'Lease Payment: [lease_id]', description = payment details, and scheduledate = payment_date. Actual payment amount is stored in a custom decimal field on the Task or in a custom Payment_Ledger__c table. Multiple payments per lease are tracked as a Task series linked to the Lease__c record.

ResMan maintenance tickets map to D365 Cases (Incident entity) using ticket title as Case Title, description as Case Description, priority as Case Priority, and status as Case Status. The Case's CustomerId (Account) lookup is set to the Property (Account) where the maintenance occurred. Unit association is preserved via custom Unit__c lookup on the Case.

ResMan user records are matched to D365 users by email address. Unmatched users are flagged before migration — teams either create D365 user accounts first or assign records to a fallback owner (e.g., the property management company admin). OwnerId on Account (Property), Contact (Tenant), Opportunity (Lease), and Case (Maintenance) is resolved at migration time.

ResMan lease documents and attachments are downloaded and re-uploaded to D365's SharePoint integration (enabled per Account or Opportunity). The document name and original upload date are preserved in SharePoint metadata. PDF leases attached to the Lease__c record are linked via the SharePoint document location on the custom table.

ResMan inspection records have no D365 equivalent — FlitStack creates an Inspection__c custom table with fields for inspection_type (move-in, move-out, annual, maintenance-related), inspection_date, unit (Unit__c lookup), and inspector (User lookup). Inspection findings are stored as long-text notes linked to the Inspection__c record.

ResMan Utilities tracks utility billing per unit — each ResMan utility account is migrated as a Utility_Account__c record linked to the Unit__c record. Fields mapped: utility_type (electric, gas, water, sewer), account_number, service_address, billing_cycle. ResMan's real-time vacated-resident billing feature is preserved as a custom flag on the utility account record.

ResMan resident screening results (credit, criminal, rental history) are stored as D365 Notes attached to the Contact record. The screening report PDF is uploaded to SharePoint and linked via the note's filename field. Screening score fields are migrated as custom number fields on the Contact.