Migrate from MRI Software to Microsoft Dynamics 365 Sales

MRI owner records contain company name, contact name, address, email, phone, and ownership percentage per property. These map directly to Dynamics 365 Account (Name, Address, Primary Contact fields) and optionally a Contact record for the primary owner contact. Ownership percentage and ownership structure data (individual vs. entity owner) are stored as custom fields on the Account.

MRI stores individual contact information for owners separately from the owner entity. These map to Dynamics 365 Contact records linked to the Account created from the parent Owner record. Email, phone, and address fields map directly; the Contact.AccountId lookup links to the owner Account.

MRI properties are the top-level organizational unit in the real estate model. They map to Dynamics 365 Account with the property name as Account Name and the property address as Account Address fields. Property type (multifamily, commercial, retail), number of units, and property-level financial summaries migrate as custom fields on the Account.

MRI units (apartments, suites, retail bays) have no direct equivalent in Dynamics 365 Sales standard objects. We create a custom Unit__c entity linked to the parent Property Account via a lookup field. Unit fields include unit number, square footage, bedroom/bath count, market rent, and unit status (occupied, vacant, under maintenance).

MRI tenant records contain tenant name, email, phone, and the unit they're leasing. Tenant contacts migrate to Dynamics 365 Contact records linked to the Property Account via AccountId. For commercial tenants that are also companies, the tenant's business name may also generate a separate Account record if the tenant organization differs from the owner entity.

MRI lease records store lease start/end dates, base rent, CAM charges, security deposit amount, escalation clauses, and renewal terms. These do not map to standard Dynamics 365 Opportunity (which assumes a sales-cycle deal). We create a custom Lease__c entity with fields for lease date, expiration date, monthly rent, CAM recovery, deposit held, and renewal type, linked to both the tenant Contact and the property Account.

MRI tracks detailed tenant accounts receivable: open charges, late fees, payment history, and current balance. Dynamics 365 Sales has no accounts receivable module. We store the current balance as a custom currency field on the Contact and preserve a full ledger history as a PDF attachment (exported from MRI) linked to the Contact record. Integration with Business Central is required for live AR synchronization.

MRI vendor records store vendor company name, contact name, insurance status, labor rates, and category (HVAC, plumbing, electrical, etc.). These map to Dynamics 365 Account records with the vendor type stored as a custom pick-list field. Vendor insurance expiry dates and labor rate schedules are preserved as custom fields.

MRI's maintenance module stores work order details: unit, category, priority, vendor assignment, status, and cost. Dynamics 365 Sales has no native work-order entity. We create a Maintenance_Request__c custom entity linked to the Unit__c record (or the property Account) with fields for category, priority, assigned vendor Account, status, and cost.

MRI inspections store inspection type (move-in, move-out, annual), date, inspector, unit, and condition notes. These migrate to a custom Inspection__c entity linked to Unit__c. Inspection type, date, and condition ratings are stored as custom fields; condition notes become a long-text field on the inspection record.

MRI payment records show payment date, amount, payment method, and check/transaction reference. Dynamics 365 Sales does not have a payment history object. We preserve the last 24 months of payment history as a custom field on the Contact record (e.g., Last_Payment_Date__c, Last_Payment_Amount__c) and attach a full payment history CSV export from MRI as a Note linked to the Contact.

MRI's Tenmast module tracks Housing Assistance Payment (HAP) voucher details: voucher number, HAP amount, portability status, and HUD reporting fields. These migrate as custom fields on the Lease__c record (HAP_Voucher_Number__c, HAP_Monthly_Amount__c, HAP_Contract_End_Date__c). Contact-level fields for voucher status are added to the tenant Contact record.