Migrate from MRI Software to Odoo CRM

MRI Tenants map to Odoo res.partner records with partner_category set to 'Tenant'. All core contact fields — name, email, phone, street address, city, state, zip, and country — transfer directly via direct field mapping. Lease-specific attributes including unit assignment, lease start date, lease end date, monthly rent amount, and security deposit migrate as custom fields on the res.partner record, since Odoo CRM lacks a native lease object. The tenant's original create date from MRI is preserved as a custom datetime field.

MRI Owners (property owners and landlords) map to Odoo res.partner records with partner_category set to 'Owner'. Standard contact details including owner name, email, phone, and mailing address migrate via direct field mapping. Ownership-specific fields such as ownership percentage and commission rate structures are stored as custom float and monetary fields on the res.partner record. Owner records are preserved with full contact fidelity and role attribution.

MRI Vendors map to Odoo res.partner records with partner_category set to 'Vendor'. Core vendor information including name, email, and phone transfer directly. Vendor-specific attributes such as vendor type classification, tax identification number, payment terms, and banking details migrate as custom fields where Odoo lacks native equivalents. This ensures vendor payment and compliance data is fully preserved in the Odoo partner record.

MRI Properties have no direct Odoo CRM equivalent — Odoo has no Property object in the CRM module. We map Property records to product.product (marked as storable or consumable depending on use) with property name, type, address, and unit count as product fields and custom fields.

MRI Units nest within Properties as child entities. Each Unit migrates as a separate product.product record linked to its parent Property via a custom many2one field (parent_property_id__c). Unit-level attributes including unit number, floor number, bedroom count, bathroom count, square footage, and market rent become standard product fields and custom fields. This hierarchical structure preserves the property-unit relationship within Odoo's product model.

MRI Leases link Tenants to Units. Since Odoo has no native Lease object in CRM, we attach lease fields to the res.partner (Tenant) record: lease_start, lease_end, unit_id (many2one to product.product), monthly_rent, security_deposit, and escalations as custom fields. Multi-tenant leases with multiple signatories require junction records.

MRI tenant ledger entries (rent charges, payments, arrears) have no CRM equivalent in Odoo. We preserve the final balance and last-12-months ledger summary as custom fields on the res.partner record. Full ledger history requires Odoo Accounting module configuration and data import separately.

MRI maintenance tickets and work orders migrate to Odoo's mrp.repair model when the Repair module is installed, or project.task for general maintenance tracking. Priority level, maintenance category, assigned vendor (linked via many2one to res.partner), and scheduled completion date become custom fields on the target record. Open versus closed status migrates as a stage field, preserving the ticket's current state in the migration.

MRI allows contact persons attached to Properties or Tenants. These merge into res.partner records — if the person is already represented as a Tenant or Owner, the contact role is added to the existing partner record via partner.category and custom contact_role field.

MRI file attachments including lease PDFs, unit photographs, owner correspondence, and vendor contracts are downloaded from the source system and re-uploaded to Odoo's ir.attachment model. Each attachment is linked to its corresponding res.partner or product.product record using Odoo's relational reference fields. File size limits and supported formats (PDF, images, Office documents) follow Odoo's standard attachment constraints.

MRI users are matched to Odoo res.users by email address. MRI role names (Property Manager, Accountant, Admin) map to Odoo security groups. Unmatched users are flagged before migration — teams either create the Odoo user first or assign records to a fallback user.

MRI note entries and activity logs migrate as Odoo mail.message records linked to the corresponding res.partner. Original timestamps, author (matched by email to res.users), and body text are preserved. Private notes migrate as internal notes visible to the record owner.