Migrate from MRI Software to HighLevel

MRI stores contacts as part of Tenant, Landlord, and Vendor records. FlitStack extracts each contact type with its role designation and maps them to HighLevel Contacts with the role preserved as a tag and a custom field (Contact_Role__c) for filtering and segmentation. Additional contact metadata including communication preferences and source attribution is retained in custom fields during the migration process to maintain full contact history integrity.

HighLevel has no native Property object. We create a Property Custom Object in HighLevel with fields for property name, address, type (residential/commercial/mixed-use), unit count, and MRI property ID. Each Property record links to its Unit child records via HighLevel's custom object relationship.

Units belong to a Property and hold fields for unit number, floor plan, square footage, bedrooms, bathrooms, and current occupancy status. We create a Unit Custom Object and establish a parent-child link to the Property Custom Object using HighLevel's relationship field.

Leases contain start and end dates, monthly rent, security deposit, lease status (active/expired/terminated), and the related Tenant and Property. We create a Lease Custom Object with all standard lease fields and link it to the corresponding Contact (tenant) and Property Custom Object records in HighLevel.

MRI owners and landlords map to HighLevel Companies. We extract the owner name, company name (if a business entity), address, and email from MRI and map to the Company object. MRI allows multiple properties per owner — we preserve this by tagging the Company with property count and linking all associated Property Custom Object records.

Vendors from MRI map to HighLevel Contacts with the Vendor tag applied automatically. The vendor company name maps to the Contact's company field, and the vendor specialty (HVAC, plumbing, electrical) maps to a custom pick-list field (Vendor_Specialty__c) for filtering in HighLevel workflows.

MRI work orders map to HighLevel Tasks with additional fields (property, unit, category, priority, assigned vendor) stored as a WorkOrder Custom Object linked to the Task. We preserve the work order description, creation date, status, and cost estimate from MRI.

Financial ledger entries — rent payments, security deposit transactions, and GL entries — store as a LedgerEntry Custom Object in HighLevel. We preserve date, amount, transaction type, and reference to the Lease and Contact. This data does not drive HighLevel's native billing tools (those must be configured separately).

MRI user accounts are resolved by email match against HighLevel users. Unmatched users are flagged before migration so the team can create HighLevel accounts first or assign a fallback owner. Owner display name and email are preserved as metadata on migrated records.

MRI file attachments associated with properties, leases, or units are downloaded and re-uploaded to a Document Custom Object in HighLevel, linked to the corresponding Property or Lease record. File size limits from HighLevel apply (standard upload size cap).

MRI supports N:N associations between tenants, landlords, and properties. We map the primary association as a direct link on the Contact record and surface secondary associations using tags (e.g., property_manager, former_tenant) since HighLevel's native linking supports 1:N from Contact to Custom Objects.

MRI's Rent Reasonableness module stores comparable rent data used in Housing Choice Voucher programs. We preserve this as a RentBenchmark Custom Object with fields for comparable property, unit type, market rent, and voucher amount. This is a reference data migration — it does not drive HighLevel's native workflows.