Yardi to Salesforce migration
Moving from Yardi to Salesforce Sales Cloud replaces a property-centric operational system with a person-centric CRM that handles your prospect pipeline, leasing activities, and tenant relationships differently. FlitStack AI maps every property, prospect, lease, tenant, and unit into Salesforce's Account, Lead, custom Lease, and Contact objects — preserving original timestamps and owner assignments while your team keeps working in Yardi through the cutover window.
FlitStack AI migrates accounts, custom object: unit__cs, leads, custom object: lease__cs and contacts from Yardi to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3–6 weeks for under 10,000 records with standard property and lease data.

What moves from Yardi to Salesforce?
Yardi Voyager and Yardi Breeze are property management platforms designed around properties, units, leases, and rent collection — not around CRM-style lead management, sales pipelines, or tenant relationship tracking.
Read the full summary
Salesforce Sales Cloud inverts that model: every person is a Lead or Contact under an Account, activities are logged as Tasks and Events, and commercial leasing deals flow through Opportunities with stage tracking and forecast management. FlitStack AI extracts Yardi data via Yardi Data Connect, nightly SQL exports, or the Yardi Voyager REST API, then transforms and loads it into Salesforce's Account-Contact-Lead-Opportunity object graph. Property records become Accounts; prospects become Leads; leases become custom Lease__c objects tied to the property Account. Yardi automations (rent escalation triggers, renewal alerts, work-order routing) have no native equivalent in Salesforce Flow and must be rebuilt by your admin using Salesforce Flow or Apex triggers. FlitStack AI sequences the migration so foreign keys resolve correctly: Properties first, then Prospects and Tenants, then Leases. A 24–48h delta-pickup window captures any Yardi records modified during cutover. Owner resolution matches Yardi user emails to Salesforce Users before any record lands without an owner assignment.
Property (Yardi Voyager) → Account
Yardi property records map directly to Salesforce Accounts.
How it maps
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.
Unit (Yardi Voyager) → Custom Object: Unit__c
Yardi units have no direct Salesforce equivalent — a property has N units but Salesforce Accounts represent one property per record.
How it maps
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.
Prospect (Yardi Voyager) → Lead
Yardi prospect records map to Salesforce Leads.
How it maps
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.
Lease (Yardi Voyager) → Custom Object: Lease__c
Yardi lease records have no native Salesforce equivalent.
How it maps
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.
Tenant (Yardi Voyager) → Contact
Yardi tenant records map to Salesforce Contacts linked to the property Account via AccountId.
How it maps
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 Roll / Payment History → Custom Object: Rent_Payment__c
Rent payment history and rent roll rows do not map to any standard Salesforce object.
How it maps
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.
- PropertyAccount1:1
- UnitCustom Object: Unit__ctransformed
- ProspectLead1:1
- LeaseCustom Object: Lease__ctransformed
- TenantContact1:1
- Rent RollCustom Object: Rent_Payment__ctransformed
+ 6 more in the mapping below
How Yardi and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Yardi | Salesforce |
|---|---|---|
| Primary object | Yardi organizes everything around Property (building, unit, lease) — the property is the root entity | Salesforce organizes around Account and Contact — persons and companies are the root entities with property as a secondary attribute |
| Prospect/leads | Yardi stores prospects with limited pipeline tracking; no native stage probability or forecast | Salesforce Lead and Opportunity objects offer stage-based pipeline, probability, forecast category, and deal tracking |
| Lease records | Yardi Lease is a first-class object with rent schedules, escalations, and concessions embedded | Salesforce has no native lease object — lease terms must be stored on a custom Lease__c object or Opportunity with custom fields |
| Workflow automations | Yardi handles rent escalations, renewal reminders, and maintenance routing as built-in property rules | Salesforce has no property-automation equivalent; workflows must be rebuilt in Salesforce Flow or Apex by your admin |
| Data extraction | Yardi offers no free export button; data access requires SQL restore, Yardi Data Connect (paid), or Yardi Voyager API (costly per-API) | Salesforce provides Data Loader, REST API, Bulk API, and Data Export — all accessible without per-record fees |
| Multi-unit grouping | Yardi tracks each unit individually within a property; N units = N rows in the unit table | Salesforce Accounts typically represent one property record; units within a property require a custom Unit__c object or a text multi-select field |
| Pricing model | Yardi Voyager and Breeze are priced per unit per month ($1–$3/unit/month minimums); API access adds per-API fees | Salesforce Sales Cloud is priced per user per month ($25–$550/user/month depending on edition) with no per-API access fees |
| Reporting | Yardi Voyager reporting centers on rent rolls, GL exports, and occupancy — financial and operational | Salesforce reporting covers pipeline velocity, win rates, sales cycle length, and tenant engagement — activity and revenue focused |
Yardi to Salesforce field mapping
The 30 most-used fields of 40 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
PropertyNamePropertyNameAccount -
PropertyAddressPropertyBillingStreetAccount -
PropertyCityPropertyBillingCityAccount -
PropertyStatePropertyBillingStateAccount -
PropertyZipPropertyBillingPostalCodeAccount
| Yardi field | Salesforce field | Mapping | Note |
|---|---|---|---|
Property.PropertyName | Account.Name | direct | |
Property.PropertyAddress | Account.BillingStreet | direct | |
Property.PropertyCity | Account.BillingCity | direct | |
Property.PropertyState | Account.BillingState | direct | |
Property.PropertyZip | Account.BillingPostalCode | direct | |
Property.PropertyType | Account.Type | value_mapping | Yardi property types (Multifamily, Commercial, Mixed-Use) map to Salesforce Account Type pick-list values; non-matching values stored as custom Type__c field. |
Property.NumberOfUnits | Account.NumberOfEmployees | transformed | Yardi unit count maps to NumberOfEmployees as a proxy field. Units are also individually represented in the custom Unit__c object. |
Property.YearBuilt | Account.YearFounded | transformed | Property year-built maps to YearFounded (a label override on the Account) for reporting purposes. |
Property.PropertyStatus | Account.AccountStatus__c | value_mapping | Yardi Active/Inactive/Under-Renovation status maps to a custom pick-list field on Account; values mapped one-by-one. |
Unit.UnitID | Unit__c.Name | direct | |
Unit.UnitType | Unit__c.Unit_Type__c | direct | |
Unit.Bedrooms | Unit__c.Bedrooms__c | direct | |
Unit.Bathrooms | Unit__c.Bathrooms__c | direct | |
Unit.SquareFootage | Unit__c.Square_Footage__c | direct | |
Unit.UnitRent | Unit__c.Market_Rent__c | direct | |
Unit.OccupancyStatus | Unit__c.Occupancy_Status__c | value_mapping | Yardi Occupied/Vacant/Notice values map to Salesforce custom pick-list; status dates preserved as additional datetime fields. |
Unit.PropertyID | Unit__c.Property__c | transformed | Unit's parent Yardi property ID resolves to the Salesforce Account external ID lookup; parent Account must be migrated first. |
Prospect.ProspectName | Lead.Name | direct | |
Prospect.Email | Lead.Email | direct | |
Prospect.Phone | Lead.Phone | direct | |
Prospect.Company | Lead.Company | direct | |
Prospect.LeadStage | Lead.Lead_Leasing_Stage__c | custom_field_required | Yardi leasing stages (Inquiry, Tour, Application, etc.) have no Salesforce native equivalent; custom pick-list field created on Lead. |
Prospect.DesiredUnitType | Lead.Desired_Unit_Type__c | custom_field_required | Prospect unit preferences stored as a custom text or pick-list field on Lead since no standard Salesforce field captures this. |
Prospect.MoveInDate | Lead.Desired_Move_In_Date__c | custom_field_required | Desired move-in date stored as a custom date field; Salesforce has no standard field for prospect move-in timing. |
Prospect.OwnerEmail | Lead.OwnerId | transformed | Yardi owner email resolves to Salesforce User by email match; unmatched owners flagged and assigned to fallback User. |
Prospect.CreatedDate | Lead.Original_Create_Date__c | custom_field_required | Salesforce CreatedDate reflects migration time; original Yardi create date preserved as a custom datetime field for reporting continuity. |
Lease.LeaseID | Lease__c.Name | direct | |
Lease.LeaseStatus | Lease__c.Lease_Status__c | value_mapping | Yardi Active/Expired/Terminated/Notice values map to a custom pick-list on Lease__c; status value mapping defined in migration plan. |
Lease.StartDate | Lease__c.Start_Date__c | direct | |
Lease.EndDate | Lease__c.End_Date__c | direct |
What to watch for in a Yardi to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Yardi API access is paywalled and costly — extraction method defines project scope
Yardi does not provide a free public export endpoint.
How we handle it
Data access requires either a Yardi Voyager API license (which carries per-API or annual fees that vary by contract), a nightly SQL database backup restore (which requires Yardi private-cloud or dedicated hosting access and may incur data latency), or Yardi Data Connect (a paid integration layer). The extraction method chosen during scoping directly determines timeline and cost. FlitStack AI maps the available access method to a migration pipeline and discloses any per-API fee exposure in the project plan before work begins. If your Yardi contract does not include API access, a SQL restore or Yardi consultant engagement may be required first.
Yardi property model (N units per property) collides with Salesforce Account hierarchy
Yardi Voyager tracks each unit as a separate row under a property — a 200-unit apartment complex has 200 Yardi unit records.
How we handle it
Salesforce Accounts represent one entity per record, not one unit per record. FlitStack AI creates a custom Unit__c object with a lookup to the parent Account so each Yardi unit maps to its own Salesforce record. Without this custom object, unit-level data (square footage, rent, occupancy) would have to be flattened into a long-text field or lost entirely. The Unit__c object and its lookup relationship to Account must be deployed in Salesforce before data loads run.
Yardi automations (rent escalations, renewal alerts, work-order routing) have no Salesforce equivalent and must be rebuilt
Yardi Voyager handles rent escalation rules, lease-renewal reminders, and maintenance work-order assignment as built-in property management workflows.
How we handle it
These are configuration-level rules in Yardi that are tightly coupled to the property and lease data model. Salesforce has no property-automation layer — there is no native mechanism to trigger a rent increase email or auto-create a renewal task when a lease end date approaches. FlitStack AI migrates the data only; the automation logic must be rebuilt in Salesforce Flow or Apex by your admin. We export a structured description of each Yardi automation rule as a rebuild reference.
Yardi's lease data model does not map to any Salesforce standard object
A Yardi lease record contains start/end dates, rent amount, security deposit, escalation percentage, concession terms, and renewal type — all structured fields that live in Yardi as first-class objects.
How we handle it
Salesforce has no standard lease or tenancy object. FlitStack AI creates a custom Lease__c object with the required fields and a lookup to both the property Account and the tenant Contact. Because Salesforce custom objects require a deployment step before data can be loaded, the migration plan sequences custom object creation and field definition before any lease records are inserted. Without this planning step, lease data would be imported before the object exists.
Dirty Yardi data surfaces post-migration unless pre-scoping audits the source records
Yardi Voyager deployments that have accumulated years of data frequently contain duplicate properties (the same building entered under slightly different names), inactive units still flagged as occupied, and leases with missing end dates.
How we handle it
These data-quality issues are invisible in Yardi because the system does not surface duplicate records or flag stale data. FlitStack AI performs a pre-migration data audit against Yardi's export and generates a cleaning report before transformation begins. Records that fail validation rules in Salesforce (required fields, pick-list values, external ID format) are quarantined and surfaced for your team to resolve before the final migration run.
How the migration runs
Establish Yardi data access and audit source data
FlitStack AI confirms your Yardi access method (API license, SQL restore, or Data Connect) and maps available Yardi objects, custom tables, and unit-level data structures.
What this step covers
We run a pre-migration data audit that identifies duplicate properties, missing foreign keys, stale leases, and inconsistent naming conventions. A data-cleaning report is delivered to your team before any transformation logic is written, so dirty data does not become dirty Salesforce data.
Design Salesforce custom objects and field schema
Based on the Yardi data audit, FlitStack AI designs the Salesforce schema: standard Account and Lead mappings plus custom Lease__c, Unit__c, and Rent_Payment__c objects.
What this step covers
We deliver a schema setup plan that your Salesforce admin (or our team) deploys using Salesforce Setup or the Metadata API before data loads begin. External IDs on Account and Contact are established so Yardi property IDs and tenant IDs can be used for upsert operations rather than insert-only, preventing duplicate records on re-runs.
Export Yardi data and run transformation pipeline
Yardi data is extracted using the agreed access method and loaded into FlitStack's staging environment.
What this step covers
The transformation pipeline maps each Yardi object to its Salesforce equivalent: Properties to Accounts with address normalization, Units to custom Unit__c records with parent Account lookups resolved, Prospects to Leads with leasing-stage mapping, Leases to custom Lease__c records with tenant and property lookups resolved, and Tenants to Contacts linked to the property Account. Owner resolution matches Yardi user emails to Salesforce Users by exact email match; unmatched owners are flagged for fallback assignment.
Run sample migration with field-level diff
A representative slice of Yardi data — typically 100–500 records spanning multiple properties, units, prospects, and leases — migrates to Salesforce first.
What this step covers
FlitStack AI generates a field-level diff report comparing source values against destination field values so you can verify unit-to-Account grouping, lease-to-Contact lookups, leasing-stage mapping, and owner resolution before the full run commits. Sample migration validation typically runs for 1–2 days depending on record volume.
Execute full migration with delta-pickup cutover
The full Yardi dataset migrates to Salesforce using Bulk API for large record sets or REST API for smaller volumes.
What this step covers
A delta-pickup window of 24–48 hours captures any Yardi records created or modified during the cutover window. All operations are logged in an audit trail. If reconciliation reveals missing or incorrectly mapped records, one-click rollback reverts the Salesforce org to its pre-migration state. After validation passes, Yardi remains operational for read-only access throughout the cutover — your leasing and property management team keeps working without interruption.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Yardi migration scope is driven primarily by the data extraction method: SQL restores and Yardi Voyager API access carry technical overhead that increases cost compared to standard CRM-to-CRM migrations. Record volume (total property, prospect, lease, tenant, and unit rows), custom property count in Yardi Voyager, and the number of distinct property types (residential, commercial, mixed-use) set the base tier. Custom Lease__c object creation and multi-unit grouping logic add complexity because each unit row must be either flattened into a custom field or mapped to a child Salesforce object. Yardi's per-API cost model also means data extraction planning adds planning time. Configurations with fewer than 2,000 total rows and no custom Yardi objects fall in the lower range; large multi-property portfolios with 50,000+ rows and complex lease schemas land in the upper range. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Yardi to Salesforce →Why teams move from Yardi to Salesforce
- Yardi's property-centric model has no native lead scoring, pipeline forecasting, or sales-activity tracking — the CRM features real estate operators need to manage broker relationships, investor pipelines, and leasing-team performance are missing without significant customization. Yardi's model lacks native pipeline management tools, making it hard for leasing teams to track deal stages, assign tasks, and forecast occupancy without custom development.
- Data extraction from Yardi requires costly API licensing or SQL database restores with consultant involvement. Teams report spending more time on data pulls than on the actual sales process. Salesforce's free Data Loader and Bulk API eliminate per-query costs and give your team self-service data access.
- Yardi Voyager users describe the interface as outdated, difficult to navigate, and slow during multi-user sessions — G2 reviewers note that simple tasks like updating a lease require many clicks through clunky screens. Salesforce Lightning's modern UI and mobile experience reduce training time for leasing and sales staff.
- As portfolios grow, Yardi's disconnected reporting model requires manual GL exports and spreadsheet consolidation to get portfolio-level performance views. Salesforce's native reporting, Salesforce Analytics, and Tableau integration provide real-time dashboards without manual data assembly. When a portfolio expands, manual GL exports become a bottleneck, forcing analysts to rekey data into spreadsheets and increasing risk of errors. Salesforce's real-time dashboards automate aggregation, giving property managers instant visibility across all assets without repeated manual effort.
- Yardi's AppExchange-equivalent ecosystem is limited — integration with modern tools like Slack, Gong, Outreach, or DocuSign requires custom development or third-party middleware. Salesforce's 5,000+ AppExchange apps and native Slack + Tableau integration reduce the integration burden as teams scale. This breadth of extensions also includes industry-specific solutions for property management, while Yardi's limited marketplace forces teams to build and maintain custom integrations internally, increasing long-term maintenance overhead.
Questions, answered
Yardi to Salesforce migration questions
How long does a Yardi to Salesforce Sales Cloud migration take?
Most Yardi-to-Salesforce migrations complete in 3–6 weeks for portfolios under 10,000 records. The longest planning step is establishing Yardi API access or SQL restore access and designing the custom Lease__c and Unit__c schema. Large portfolios with 50,000+ rows across multi-property entities, complex lease structures, and historical rent roll data extend to 8–16 weeks. The Yardi data access method (API vs. SQL restore) is the primary timeline variable before transformation begins.
Will my Yardi automations (rent escalations, renewal alerts, work-order routing) migrate to Salesforce Flow?
No. FlitStack AI migrates data only — Yardi's built-in property management automations do not transfer to Salesforce because Salesforce has no native rent-escalation or lease-renewal workflow engine. These rules must be rebuilt in Salesforce Flow or Apex by your admin. We export a structured description of every active Yardi automation as a rebuild reference, listing the trigger condition, action, and affected Yardi objects so your admin can reconstruct equivalent logic in Salesforce.
What does a Yardi lease become in Salesforce Sales Cloud?
Yardi lease records have no standard Salesforce equivalent, so FlitStack AI creates a custom Lease__c object. Fields include Lease_Status__c, Start_Date__c, End_Date__c, Monthly_Rent__c, Security_Deposit__c, and Rent_Escalation__c. The Lease__c record links to the property Account (via Property__c lookup) and to the tenant Contact (via Tenant_Contact__c lookup). If your Yardi lease data includes concession terms or addendum text, those are stored as structured custom fields or a long-text area field on the Lease__c record.
Can I migrate Yardi custom objects to Salesforce custom objects?
Yes. Yardi Voyager custom tables created in Custom Tables (the admin panel) map 1:1 to Salesforce custom objects. Custom object associations that use Yardi's N:N relationship model need Salesforce junction objects — FlitStack surfaces these in the migration plan and creates the junction object with lookup relationships to both parent custom objects. Standard Yardi objects (Property, Unit, Prospect, Lease, Tenant, Maintenance, Vendor) also map, each with its own field-level translation documented in the field mapping plan.
How does Yardi's per-unit data (N units per property) translate to Salesforce?
Yardi tracks each unit as a separate row — a property with 300 units generates 300 Yardi unit records. Salesforce Accounts represent one property entity per record. FlitStack AI creates a custom Unit__c object with a lookup field (Property__c) linking each unit to its parent Salesforce Account. Each Yardi unit row becomes one Unit__c record so square footage, market rent, occupancy status, and unit type are preserved as queryable fields rather than collapsed into a text block. This structure also enables reporting on occupancy rates and unit turnover per property in Salesforce reports.
Does the migration affect my Yardi account during the cutover?
No. FlitStack AI uses read-only access to Yardi during migration — your leasing agents, property managers, and finance team continue working in Yardi without interruption. A delta-pickup window of 24–48 hours at the end of the migration captures any records modified in Yardi during the cutover window so Salesforce reflects the final state at go-live. No write-back to Yardi occurs unless your project scope explicitly includes bi-directional sync, which requires a separate integration engagement with Yardi API access.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Marketing Star to SalesforceMapping · history · rollbackKartra to SalesforceMapping · history · rollbackCivicrm to SalesforceMapping · history · rollbackHighLevel to SalesforceMapping · history · rollbackSpotler CRM to SalesforceMapping · history · rollbackAutoText to SalesforceMapping · history · rollback Yardi to Dynamics 365Mapping · history · rollbackYardi to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Yardi to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote