Migrate from Entrata to Twenty CRM

Each Entrata Property becomes a Twenty Company. Property name maps to Company.name. Address, unit count, and property type migrate as custom fields on the Company record. Active Work Orders and open Leases attach to this Company as Tasks and Opportunities respectively.

Entrata Tenants and Residents become Twenty People. The primary Property-Company record links via companyId on the Person. Tenant contact fields (email, phone, move-in date) map to Person fields or custom fields. Former tenants with churned leases retain their Person record with lease-end captured.

Prospective tenants in Entrata's pipeline migrate as Twenty People with a lead status custom field. The source property they inquired about attaches as the primary companyId. Inquiry date and source channel migrate as custom fields for segmentation and lead-age analysis. This preserves the prospect pipeline for follow-up in Twenty after migration.

Active leases map to Twenty Opportunities keyed to the Property-Company. Lease value (monthly rent × lease term) becomes the Opportunity.amount. Lease status (Active, Expired, Month-to-Month) maps to Opportunity.stage via a value-mapping table. Lease start and end dates become custom date fields; the Opportunity close date reflects lease end.

Individual Unit records (unit number, bedrooms, bathrooms, sq footage, market rent) are aggregated and stored as a custom Units__c field (JSON array or linked custom object) on the Property-Company record. Unit availability status is preserved for reporting. If the portfolio exceeds 500 units, Units may warrant a separate custom object linked to Company.

Entrata Work Orders migrate as Twenty Tasks attached to the Property-Company record. Subject carries the work-order title, body carries description and resolution notes. Priority, category, and vendor assignment migrate as custom fields. Original creation timestamp and assigned technician preserved. Closed tasks retain full history.

Entrata Vendors become Twenty Companies with a vendor-type custom field to distinguish them from Property records. Vendor contact name, email, and phone map to the standard Company contact fields. Service category (HVAC, plumbing, electrical) migrates as an industry__c custom field for filtering.

Entrata user accounts are matched to Twenty WorkspaceMembers by email address. User roles (Property Manager, Leasing Agent, Maintenance Tech) map to Twenty permission groups. If a user email has no match in Twenty, the records assign to a default owner flagged for manual reassignment.

Rent payment history and ledger entries do not map to a native Twenty object. We store the most recent payment date, outstanding balance, and payment status as custom fields on the Lease-Opportunity record. Full payment history is exported as a CSV attachment for reference but does not create individual records.

Lease agreements, tenant documents, and work-order attachments are re-uploaded to Twenty's file storage and linked to the corresponding Company (Property), Person (Tenant), or Opportunity (Lease) record. File size limits and format compatibility are checked before upload to prevent migration failures.

Property inspection records migrate as Twenty Notes attached to the Property-Company. Inspection date, inspector name, and overall condition score migrate as custom fields on the Note. Detailed line-item inspection results are stored in the Note body for reference and future audit purposes.

Entrata listing sources and marketing campaign attribution do not have a direct Twenty equivalent. We preserve the listing source (website, referral, walk-in) as a custom source__c picklist field on the Person record. Campaign-specific UTM data is stored as text fields for post-migration analytics.