Migrate from ResMan to Odoo CRM

ResMan stores tenant contact records (name, email, phone, address) under the Tenant object. These map directly to Odoo res.partner records. The contact's primary property association in ResMan becomes a custom field (Primary_Property_ID__c) and a note on the partner record. Multiple property associations are linked as partner categories or tags in Odoo.

ResMan Property records (name, address, unit count, property type) map to res.partner records with partner_type='company'. The property's primary manager or owner contact becomes the commercial partner linked via parent_id. Unit-level data does not translate to Odoo CRM natively — unit inventory is preserved as a custom JSON field for reference only.

ResMan Lease records (start date, end date, rent amount, deposit, lease status) have no Odoo CRM equivalent. We map them as structured custom fields on the associated res.partner: Lease_Start_Date__c, Lease_End_Date__c, Monthly_Rent__c, Security_Deposit__c, and Lease_Status__c. Historical lease events are logged as notes with timestamps.

ResMan Work Order records (category, priority, status, assigned technician, unit, description, create date) map to Odoo project.task records. A dedicated Odoo project ('Property Maintenance') is created per property, with tasks representing individual work orders. Priority and category map to project.task priority and tag. The original ResMan work-order ID is stored as a custom field for audit traceability.

ResMan payment and charge history is accounting data with no CRM equivalent in Odoo. We preserve the data as structured custom fields on res.partner (Last_Payment_Date__c, Balance_Due__c, Payment_Status__c) and export the full payment ledger as a CSV attachment linked to the partner record. Full accounting migration requires Odoo Accounting app — handled separately.

ResMan stores tenant screening results (credit, criminal, eviction history) as documents linked to the tenant. These are binary files with no Odoo CRM field equivalent. We re-upload them as ir.attachment records on the res.partner, tagged with category 'Screening Report' and original ResMan create date preserved in the attachment's description field.

ResMan documents stored under tenants, leases, or properties are exported and re-uploaded to Odoo as ir.attachment records. Documents linked to a contact attach to res.partner; documents linked to a lead attach to crm.lead. File size limits (Odoo default 25MB per file) are respected; oversized files are split or flagged for manual handling.

ResMan staff users (property managers, leasing agents, maintenance staff) are resolved by email match against existing Odoo res.users records. If a user does not exist in Odoo, they are flagged as unassigned before migration. Their ResMan role (e.g., 'Property Manager') is mapped to Odoo groups or kept as a custom field on the user record.

ResMan's CRM module stores early-stage leads or prospects separate from tenant contacts. These map 1:1 to Odoo crm.lead records. Lead source, status, and assigned agent map to crm.lead source_id, stage_id, and user_id respectively. HubSpot-style lifecycle stages used in ResMan's CRM export as a custom pick-list field on crm.lead.

ResMan allows custom fields on properties, units, and tenants. Any custom fields identified during the data audit are created as Odoo custom fields via Studio (or Python module for Community) before migration. The field type is preserved where possible: text→char, number→float, date→date. Multi-select custom attributes map to Odoo tags or selection fields.

ResMan Utilities tracks billing and sub-metering for properties. This is accounting and utility-management data with no Odoo CRM equivalent. We do not migrate utility records. Property utility configuration (meter IDs, billing rules) is exported as a JSON reference file for re-entry in Odoo Billing if needed.

ResMan stores pet records, vehicle info, and additional occupants as sub-records under a tenant. These map to Odoo custom fields on res.partner (Pet_Info__c, Vehicle_Plate__c, Additional_Occupants__c) or as tagged notes. The relationship type (pet vs. vehicle) is preserved in the field name or as a category tag on the note.