Migrate from Yardi to Twenty CRM

Yardi tenant records map directly to Twenty People. Each tenant record carries first name, last name, email, phone, and address — these become standard Twenty People fields. The original Yardi tenant ID is preserved as a custom field (Source_Tys-Tenant_ID__c) for traceability. If a tenant has multiple lease records, a single People record is created and the most-recently-active lease is linked as the primary opportunity.

Yardi property records (building name, address, property type, number of units, market rent) map to Twenty Companies. The property's primary address populates Company.street, city, and country fields. Property type (residential, commercial, mixed-use) migrates as a pick-list custom field (Property_Type__c) since Twenty Companies have no native property-type field. Parent properties in Yardi hierarchy map to Company.parentId — the top-level portfolio entity has no parent.

Yardi lease records are the most complex translation. Each active lease becomes a Twenty Opportunity — the Opportunity name is constructed as '[Property Name] – [Tenant Name] Lease'. Monthly rent maps to Opportunity.amount. Lease start and end dates map to custom date fields (Lease_Start__c, Lease_End__c) since Twenty Opportunities have a CloseDate for expected close rather than lease duration. StageName defaults to 'Active Lease' as a custom pick-list value; expired leases use a 'Closed Won' stage. Lease status (active, expired, terminated) maps via value mapping.

Yardi vendor records map to Twenty Companies with a custom pick-list field (Account_Type__c) set to 'Vendor'. Vendor name, contact name, phone, and email map to standard Twenty Company and People fields. The vendor's address maps to the Company address fields. Each vendor may have multiple service categories (HVAC, landscaping, plumbing) — these are stored as a multi-select custom field (Service_Categories__c) on the Company record.

Yardi work orders map to Twenty Tasks. The Task title is constructed from the work order type and property address. The related Company is resolved by matching the work order's property to the migrated property record. The Yardi work order status (Open, In Progress, Completed, Cancelled) maps to a custom pick-list field (Work_Order_Status__c) since Twenty Tasks use a binary completed/not-completed model. Original work order create date migrates as Task.createdAt.

Yardi unit records are not independent objects in Twenty — they are aggregated as custom fields on the parent Company record. Unit count, unit number range, and unit type breakdown (studio, 1BR, 2BR) migrate as custom Number and text fields (Total_Units__c, Unit_Mix__c) on the Company. For large portfolios with hundreds of units, unit-level detail is preserved in a CSV companion file attached to the Company record rather than as individual records.

Yardi rent roll records (monthly rent, arrears, concessions, escalations) do not map to a native Twenty object. They are aggregated and stored as custom currency fields on the associated Opportunity: Current_Rent__c, Arrears_Amount__c, Monthly_Escalation__c, and Security_Deposit__c. Historical rent roll rows beyond the current period are archived as a JSON attachment on the Opportunity for compliance reference.

Yardi Voyager user accounts map to Twenty WorkspaceMember records. The mapping relies on email address — FlitStack cross-references Yardi user email against Twenty workspace invitations. Users without a resolvable email are flagged as unmatched before migration. The Yardi user's property-level role (Property Manager, Accountant, Admin) is stored as a custom text field (Source_Yardi_Role__c) on the WorkspaceMember.

Yardi CRM Queue items (phone calls, emails, notices) map to Twenty Tasks attached to the relevant People or Company record. The queue item type (Call, Email, Notice) is stored as a custom pick-list field (Queue_Item_Type__c). The queue item's original timestamp and Yardi user who created the item migrate as Task.createdAt and the assigned WorkspaceMember. Since Yardi CRM Queue lacks activity body content, the Task.note field is populated with a standard descriptor: 'Yardi CRM Queue item — [type] — [date].'

Yardi Custom Tables — created by admins under Tenant buttons in Voyager — map to Twenty custom objects. Each custom table becomes a new Twenty object with fields created via the /metadata API. The relationship between the custom table and its parent entity (Tenant, Property, or Lease) is established as a relation field on the custom object. Custom table data migrates via the Twenty REST import endpoint, with foreign keys resolved to migrated Yardi record IDs.