Migrate from Yardi to Odoo CRM

Yardi tenant records map directly to Odoo res.partner. Each tenant's name, email, phone, and address fields translate to partner fields in the same structure. Unmatched tenants without an email are flagged for manual review before insertion. FlitStack also tags each partner as 'Tenant', stores the original Yardi contact ID in a custom Char field, and checks for duplicate emails before insertion.

Yardi owner records map to res.partner with a custom tag or partner_category set to 'Owner' so Odoo users can filter the partner list by role. Owner email is used for user resolution if the owner is also an Odoo system user.

Yardi properties have no direct Odoo CRM equivalent — the property name and Yardi Property ID are stored as custom Char fields on each associated res.partner record. This preserves the relationship without requiring Odoo Real Estate modules. FlitStack also creates a custom Char field for the property manager name when present in Yardi, allowing additional context to be retained on the partner record.

Yardi unit references (unit number, building) are stored as custom Char fields (Yardi_Unit_ID__c, Yardi_Building__c) on res.partner. Units without a linked tenant become placeholder partner records with role 'Unassigned Unit' for reconciliation. These custom fields enable quick filtering of partners by unit or building, and they are indexed for reporting in Odoo's kanban and list views.

Each active or historical Yardi lease becomes a crm.lead record in Odoo CRM. The lease status (New, Under-Review, Renewed, Terminated) is mapped value-by-value to a corresponding crm.lead.stage_id. Lease metadata — rent amount, start/end dates, escalation clause — is stored in custom fields on the lead.

Yardi lease status pick-list values are mapped to Odoo crm.lead.stage_id records: 'New Lease' → 'New', 'Under-Review' → 'Qualified', 'Renewed' → 'Won', 'Terminated' → 'Lost'. The mapping is configured before migration so stage_id is set correctly on lead insertion. If a lease status does not have a matching stage, FlitStack creates a new stage record in Odoo before loading leads, ensuring no foreign‑key errors.

Yardi vendors map to res.partner with vendor_category_id set from Odoo's default vendor category. Vendor type (plumber, electrician, etc.) is preserved as a custom Selection field since Odoo stores vendor role as a category rather than a typed attribute. FlitStack also adds a tag 'Vendor' to each partner record to differentiate them from tenants and owners in list views and reporting.

Yardi work orders and service requests are property-maintenance records with no direct Odoo CRM equivalent. They are exported as a reference CSV for manual re-entry in Odoo Maintenance or a custom module if your plan includes that application. They do not migrate as CRM data.

Financial ledger entries and rent payment history from Yardi do not map to Odoo CRM. They belong in Odoo Accounting if you are also deploying that module. FlitStack exports the payment history as a reference archive; the accounting module requires a separate migration run.

Yardi Voyager custom tables are exported via ySQL and mapped to Odoo custom fields on the relevant model (res.partner or crm.lead). For each custom table row, FlitStack creates the ir.model.fields entry in the target Odoo database before loading data. The field definitions are applied through Odoo's XML‑RPC API, and any pick‑list values are also created as selection options to maintain data integrity.

Yardi staff users are matched against Odoo res.users by email address. Unmatched Yardi staff are flagged as inactive Odoo users pending account creation. Owner assignment on migrated records uses this resolved user map. FlitStack records the mapping in a JSON file for audit purposes, and retries email matching after any bulk user import to capture newly created accounts.

Yardi's N-ary association chain (Tenant linked to Lease, Lease linked to Unit, Unit linked to Property, Property linked to Owner) is collapsed into a single res.partner record per tenant with Yardi_Property_ID__c and Yardi_Owner_ID__c stored as reference fields. No junction object is required in Odoo CRM.