Migrate from MRI Software to Twenty CRM

MRI Tenants (individuals renting units) map to Twenty People. Tenant name, email, phone, and contact details transfer directly. Primary unit assignment becomes a custom field or link to a Property custom object. Tenant lease history migrates as notes or custom fields.

MRI Property Owners (individuals or entities who own properties) map to Twenty People. Owner contact information transfers. If the owner is a company, it may map to Companies instead — we flag ambiguous records for your review before migration commits.

Corporate entities listed as MRI Property Owners map to Twenty Companies. Company name, address, and tax identification number transfer as standard Company fields. MRI stores entity type on the owner record — we apply a type-detection rule during the migration run that examines the ownertype field to determine whether each owner maps to the People or Companies object. Ambiguous cases involving hybrid individual-entity names receive manual review before the migration commits to prevent incorrect classification.

MRI Properties (buildings or real estate assets) have no direct equivalent in Twenty's standard CRM model. We create a Property custom object in Twenty before migration. Property fields (address, type, square footage, year built) map to custom fields on the Property object. Properties link to Tenants via custom relation fields.

MRI Units (individual rental spaces within a Property) map to a Unit custom object linked to the Property custom object. Unit fields include unit number, floor, bedroom count, bathroom count, and square footage. Current tenant assignment links to the Tenant People record.

MRI Leases (rental agreements tied to Units and Tenants) map to a Lease custom object. Key fields: lease start/end dates, monthly rent, security deposit, and renewal terms. Lease links to the Tenant People record and the Unit custom object. Rent schedule line items become child records on the Lease object.

MRI Vendors (service providers, contractors, and maintenance companies) map to Twenty Companies. Vendor name, primary contact name, email address, phone number, and service category transfer as direct field mappings. MRI stores vendor classification by trade or service type — this maps to a custom pick-list field on the Company record in Twenty, preserving your categorization scheme for filtering and reporting purposes. Vendor records without complete contact information are flagged for your team to supplement before or after migration.

MRI Work Orders (maintenance requests) map to Twenty Tasks. Task subject carries the work order description, due date carries the scheduled date, and assignee resolves to a Twenty Workspace Member by email match. Work order status (open, in-progress, completed) maps to Task status values.

MRI communication logs and contact notes map to Twenty Notes attached to People or Companies records. Each note preserves the original timestamp and author attribution to maintain the full activity timeline in Twenty. Communication type classification from MRI — including email correspondence, phone calls, site visits, and general notes — transfers as a custom field on the Note object. This enables your team to filter notes by interaction type and reconstruct complete communication histories during the audit or handoff process.

MRI staff accounts with CRM access resolve to Twenty Workspace Members by matching email addresses between systems. Active or inactive status on the MRI user record carries over to determine initial member status in Twenty. Any MRI users whose email addresses do not match existing Twenty accounts appear in a pre-migration report — your administrator can create matching Twenty accounts or assign those users' migrated records to an existing Workspace Member before the final migration run executes.

MRI Security Console manages access through Security Roles, Entity Classes, and Site ID configurations — a layered permission system tied to MRI's database structure. Twenty uses Workspace Members with Roles and optional Field-level visibility settings, which operates differently. The permission architectures have no direct mapping path. We capture your complete MRI security role structure during the audit and deliver it as a structured reference document for your administrator to use when configuring Twenty Roles manually after migration is complete.

MRI financial entries, journal vouchers, accounts receivable records, and accounting transactions constitute ERP-level data outside CRM scope. Twenty is a customer relationship management platform designed for managing People, Companies, and Opportunities — it does not include an accounting module or financial object model. We exclude General Ledger entries, payment history, outstanding balances, and all accounting data from migration scope. Your financial records remain in MRI or your designated accounting system post-migration.

MRI custom objects created via Application ToolKit map to Twenty Custom Objects using custom field mappings for each attribute. The migration plan documents every custom object's field definitions, data types, and inter-object relationships discovered during the audit phase. MRI custom objects frequently use N:N many-to-many relationship patterns — these require junction objects in Twenty's relational model, which we design and include in the schema plan. We validate relationship cardinalities during the sample migration phase before committing to the full run.