Migrate from Rent Manager to Microsoft Dynamics 365 Sales

Lease Agreement records require custom Dataverse table creation

Rent Manager stores Lease Agreement as a first-class object with start date, end date, rent amount, security deposit, escalation rate, and renewal terms. Dynamics 365 Sales has no native lease entity—Opportunity covers sales pipeline, not rental contracts. Without a custom Lease_Agreement__c table, lease data either fragments across Account custom fields (unmanageable for multiple units) or gets dropped. FlitStack creates the Lease_Agreement__c table in Dataverse before migration, including fields for unit reference, tenant contact lookup, property account lookup, and all financial terms. Your Dynamics admin should review the table schema against your Rent Manager lease data before the full run.

Sales Professional tier caps custom tables at 15 entities

Dynamics 365 Sales Professional limits custom tables to 15. A Rent Manager migration with a custom Lease_Agreement__c table, a Rental_Unit__c table, and multiple additional custom fields for vendor classification, owner type, and property attributes can exceed this limit. When the 15-table ceiling is hit, Dynamics throws an error at the table creation step. FlitStack audits the full Rent Manager custom field inventory against this limit before migration begins. If your setup requires more than 15 custom tables, the migration plan documents the Enterprise licensing upgrade requirement so your team can procure the correct tier before data lands.

Unit hierarchy collapses to property-account flat structure unless custom table is used

Rent Manager models Properties containing Units with a clear parent-child relationship. Each Unit carries its own rent amount, occupancy status, and lease association. Dynamics 365 Sales Account object stores one level of information per record—without a Rental_Unit__c custom table, unit-specific data must embed in the Account record as custom fields (Unit_1_Rent__c, Unit_2_Rent__c, etc.), which breaks at any portfolio scale. FlitStack creates the Rental_Unit__c custom table and links it to the Property Account via a lookup field, preserving the full unit hierarchy. The migration plan shows the lookup field name and validates that the relationship renders correctly in Dynamics Dynamics 365 Sales forms.

Owner Portal roles don't map to Dynamics account contact roles

Rent Manager distinguishes between Owner Portal individuals (who own properties and receive distributions) and general contacts. Dynamics 365 Sales has Account Contact Roles for defining relationship types, but the pre-seeded roles are limited to 'Business', 'Evaluator', 'Owner', and 'Reseller'. Custom roles can be added, but they don't drive any native behavior in Dynamics 365 Sales the way Rent Manager's owner portal drives specific reporting and payment workflows. FlitStack maps Owner Portal records to Account with Owner_Type__c = 'Property Owner' and flags that owner reporting (distributions, statements, 1099 tracking) requires rebuild in Dynamics using custom reports or Business Central integration.

Rent Manager's accounting ledger has no equivalent in Dynamics 365 Sales

Rent Manager includes a full double-entry accounting system with tenant charges, owner distributions, vendor payments, and bank reconciliation. Dynamics 365 Sales is CRM only—no accounting, no general ledger, no chart of accounts. Tenant charges and payment history from Rent Manager migrate as Notes attachments or as custom fields on Contact, but the transactional accounting records (what was debited, what was credited, in which account) do not translate to any Dynamics 365 Sales object. Organizations needing accounting continuity must either export Rent Manager financial reports as PDFs archived in SharePoint, or pair this migration with Dynamics 365 Business Central migration for full accounting parity. FlitStack documents this gap in the migration plan and offers the Business Central pairing as a separate workstream.