Migrate from Yardi to Salesforce Sales Cloud

Yardi property records map directly to Salesforce Accounts. Property name becomes Account Name; property address maps to BillingAddress fields. For commercial portfolios, industry can be set to 'Real Estate' or a sub-sector pick-list value. Multi-building complexes can be grouped using Parent Account hierarchy in Salesforce.

Yardi units have no direct Salesforce equivalent — a property has N units but Salesforce Accounts represent one property per record. FlitStack creates a custom Unit__c object with a lookup to the parent Account (Property). Each unit row becomes one Unit__c record so square footage, unit type, rent amount, and occupancy status are preserved and queryable by property.

Yardi prospect records map to Salesforce Leads. Prospect name becomes Lead Name; prospect email and phone map to Email and Phone. Leasing stage in Yardi (Inquiry, Tour, Application, etc.) maps to a custom pick-list field Lead_Leasing_Stage__c on the Lead record. Owner resolved by email match to Salesforce Users.

Yardi lease records have no native Salesforce equivalent. FlitStack creates a custom Lease__c object with a lookup to the property Account and to the tenant Contact. Fields include Lease_Status__c, Start_Date__c, End_Date__c, Monthly_Rent__c, Security_Deposit__c, Rent_Escalation__c, and Renewal_Type__c. Lease terms and concessions are preserved as text fields or structured custom fields based on available source data.

Yardi tenant records map to Salesforce Contacts linked to the property Account via AccountId. Multiple tenants per lease become separate Contact records with the lease relationship stored on the Lease__c object. Tenant contact fields (name, email, phone) map directly; emergency contact and alternate contact fields migrate as custom fields if present in Yardi.

Rent payment history and rent roll rows do not map to any standard Salesforce object. FlitStack creates a Rent_Payment__c object with a lookup to the Lease__c record. Fields include Payment_Date__c, Amount_Paid__c, Rent_Due__c, Payment_Method__c, and Late_Fee__c. Historical rent data is migrated for financial reconciliation purposes and Salesforce reporting on payment trends.

Yardi prospect activities — calls logged, notes attached, meetings scheduled — migrate to Salesforce Tasks (Type='Call' or 'Email') and Events linked to the Lead record. Original timestamps and owning user preserved. Yardi's activity timestamps become Salesforce Task.ActivityDate or Event.StartDateTime. Yardi activity notes can be attached as Salesforce Files to preserve context for future follow-ups.

Yardi users assigned as property managers or owners resolve to Salesforce Users by email address match. Unmatched Yardi users are flagged before migration; records are assigned to a designated fallback Salesforce User so no record lands without an owner. Role-based access in Salesforce is set up separately and is not migrated.

Yardi property photos, floor plans, and document attachments re-upload to Salesforce as Salesforce Files attached to the Account record. File size limits (Salesforce default 25MB per file) apply. Inline images in Yardi notes are downloaded, rehosted, and linked to the corresponding Salesforce record.

Any custom Yardi Voyager tables created via Custom Tables in the Yardi admin panel migrate to Salesforce custom objects. Custom object associations in Yardi (N:N relationships between custom entities) require Salesforce junction objects — FlitStack surfaces these in the migration plan before data lands.

Yardi maintenance and work-order records map to Salesforce Cases on the property Account. Case Subject, Description, Status, Priority, and CreatedDate migrate. The Yardi maintenance assignee resolves to a Salesforce User or Contact. Original work-order numbers are preserved in a custom field Source_Work_Order__c for traceability.

Yardi vendor records that manage property services (HVAC, landscaping, etc.) map to Salesforce Accounts with a Type='Vendor' designation. Vendor contact persons map to Contacts on the vendor Account. Vendor contract details migrate as custom fields on the Account if available in Yardi.