Migrate from Yardi to Nutshell

Yardi Property maps to Nutshell Account. Property name becomes Account name. Address fields map directly. Property type (residential/commercial/industrial) maps to Industry pick-list on Account, with unmapped types stored as a custom field. Primary owner from Yardi is stored on the Account as the primary contact Person.

Yardi Units (apartments, suites, retail bays) have no Nutshell equivalent. Each Unit becomes a custom field entry on the Account — either as a multi-value custom field listing unit identifiers and statuses, or as a naming convention appended to the Account name (e.g., 'Main St Tower – Suite 101'). Unit-specific rent and status fields are preserved as additional custom fields on the Account.

Yardi Tenants become Nutshell People records. Name, email, phone, and address fields map directly. A custom field identifies the Person as a Tenant and links to the Account (property) via a custom relationship field. Tenant lease history (multiple leases at different properties) is preserved as a custom text field or linked via a custom Lease object.

Yardi Leases require a custom Lease object in Nutshell. The custom object stores lease identifier, start and end dates, base rent, escalation schedule, concessions, security deposit, and associated Account and Person lookups. Multiple leases per property are supported as multiple Lease object records linked to the same Account. Lease status (active, expired, terminated) is a custom pick-list field.

Property Owners become Nutshell People records with a custom field flagging the record as an Owner type. Owner contact details (address, email, phone) map directly. A custom field on the Account (Owners__c) stores a comma-separated list or links to the owning Person records. Owner payment history and statements cannot migrate but can be noted in a custom text field.

Yardi Vendors (maintenance contractors, utility providers) map to Nutshell Accounts with a custom field marking the Account type as Vendor. Vendor contact name, company name, phone, and email map to standard Account and Person fields. Vendor-specific fields like W-9 status are stored as custom fields.

Yardi Work Orders map to Nutshell Tasks. The task Subject carries the work-order description, Status maps to Nutshell task status (open/complete), and due date maps to the task due date. The Account (property) is linked via the standard Account association. Unit number is stored as a custom field on the Task. A custom pick-list field records work-order priority (emergency/high/low).

Yardi rent payments and financial transactions have no equivalent in Nutshell's CRM model. Payment history is summarized as a Note on the Account with key figures (last payment date, current balance, lease total paid) preserved as custom fields. Full transaction detail remains in Yardi accounting; users reference it there.

Yardi portfolios group multiple Properties — this hierarchy does not exist natively in Nutshell. We encode the portfolio relationship using a custom text field (Portfolio_Name__c) on each Account. Teams can use Nutshell's tag or custom field filtering to view all Properties within a portfolio.

Yardi owner statements and financial reports are accounting documents that do not map to any Nutshell CRM object. These must be rebuilt in Nutshell's reporting module or exported from Yardi as PDFs for archive. We flag these as non-migratable and provide a rebuild checklist as part of the post-migration deliverable.