Migrate from Yardi to Freshsales

Yardi Prospects map directly to Freshsales Leads. FlitStack preserves the Yardi prospect ID as Source_System_ID__c on the Lead, retains the original create date as a custom datetime field, and maps Yardi lifecycle stage to Freshsales lifecycle_stage. Yardi lead status maps to Freshsales Lead Status pick-list by value.

Yardi contacts that represent property managers, leasing agents, or company contacts map to Freshsales Contacts. Name, email, phone, mobile, job title, and address fields map directly. The Yardi contact ID is stored as Source_System_ID__c for traceability and duplicate detection on re-migration runs.

Yardi companies that own or manage properties map to Freshsales Accounts. Company name maps to Account Name, domain maps to Website, industry maps to Industry pick-list, employee count maps to NumberOfEmployees, and annual revenue maps to AnnualRevenue. Parent-company hierarchies in Yardi map to Freshsales Parent Account lookup.

Yardi properties that represent individual buildings or units map to Freshsales Accounts with a Property_Type__c custom field to distinguish them from company Accounts. The Yardi property name becomes Account Name, address maps to billing address fields, and unit-level detail (unit count, unit types, square footage) is stored as custom fields on the Account record.

Yardi units are merged into the parent Property Account as custom fields. Unit_Number__c, Unit_Type__c, Square_Footage__c, Market_Rent__c, and Unit_Status__c are added as custom fields on the Account. For reporting on individual units, units can also be stored as a Freshsales custom object with a lookup to the Property Account.

Yardi leases map to Freshsales Deals — the lease number becomes the Deal name, monthly rent maps to Deal Amount, lease start and end dates map to Close Date and a custom Lease_End_Date__c field, and Yardi lease status (Active, Expired, Pending) maps to Freshsales Deal Stage by value mapping. Lease_ID__c stores the Yardi lease identifier for reconciliation.

Yardi owners are resolved by email match to Freshsales User records. Owner name, email, phone, and role transfer as User fields. Unmatched owners are flagged before migration; their records are assigned to a fallback Freshsales user and the Yardi owner ID is preserved as a custom field on the associated records for post-migration reconciliation.

Yardi work orders map to Freshsales Tasks with the Yardi work order ID stored as Source_System_ID__c. Task Subject carries the work order name, description maps to Task Body, status maps to Freshsales Task Status, and priority maps to Priority__c. The primary contact on the work order links to the corresponding Freshsales Contact or Lead.

Prospect engagement history from Yardi migrates as Freshsales Tasks for calls and emails, and Events for meetings. Original timestamps, owners, and subject lines are preserved. Each activity record is linked to the corresponding Freshsales Lead or Contact by email resolution. This preserves deal context from Yardi's prospecting phase.

Yardi Custom Tables (tenant_type, lease_status, work_order_category) translate to Freshsales custom fields on the relevant object (Contact for tenant fields, Deal for lease fields, Task for work order fields). Yardi plan tier determines the number of custom fields available in Freshsales — Sprout has no custom fields; Forest allows 300 custom fields per module. FlitStack creates matching custom fields in Freshsales before loading.

Yardi files attached to prospects re-upload to Freshsales as Files on the corresponding Lead or Contact record. File size limits per Freshsales plan apply (Storage limits: Growth 2GB/user, Pro 5GB/user, Enterprise 100GB/user). Inline images in Yardi notes are extracted and rehosted as Freshsales file attachments.

Yardi rent escalation rules, lease approval workflows, and maintenance automation do not have a migration path to Freshsales. Freshsales Workflows must be rebuilt manually. FlitStack exports Yardi workflow definitions as a reference document for your Freshsales admin to use during the rebuild phase.