Migrate from Rent Manager to Twenty CRM

Rent Manager tenants migrate as Twenty People records. The tenant's full name splits into FirstName and LastName; primary email and phone map directly. Lease start and end dates store as custom date fields on the Person record since Twenty has no native lease-term concept.

Property owners become Twenty People records. The owner name maps to the Person name field directly, while owner email and phone transfer as standard contact fields. Owner type (individual versus entity) requires a custom select field in Twenty since the standard Person object lacks this distinction. Entity-owned properties link the Owner Person record to the title-holding company via the companyId relation.

Maintenance vendors, utility providers, and service contractors become Twenty Company records. Company name, contact name, email, and phone migrate directly. Vendor specialty (HVAC, plumbing, electrical, landscaping) maps to a custom select field for filtering in Twenty's kanban and list Views, enabling quick categorization of service providers.

Each Rent Manager property becomes a Company record in Twenty representing the physical asset. Address, property type (residential/commercial/mixed), and number of units migrate as fields. The property's parent company (if part of a portfolio company) maps via the Parent Company relation.

Units require a custom object in Twenty since there is no standard real-estate-unit entity. The Unit object links to its parent Property via a Company relation field, stores unit number, bedroom/bath counts, square footage, and current occupancy status as custom fields.

Leases are too domain-specific for standard CRM objects. We create a Lease custom object linked to the Tenant (Person) and Unit (custom object) with fields for lease start, end, monthly rent, security deposit, and renewal status. This preserves the full lease lifecycle for reporting.

Rent Manager maintenance requests transform into Twenty Tasks. Work order category (routine, emergency, preventive), priority level, assigned vendor, and total cost migrate as custom fields on the Task. Original work order create date and completion date preserve as custom datetime fields, maintaining complete maintenance history continuity across the migration.

Individual rent payment transactions have no clean equivalent in Twenty's standard CRM model. We preserve payment history as a JSON-serialized custom long-text field on the Lease record, preserving the full transaction detail. Alternatively, we export a separate payment ledger CSV for detailed financial reconciliation handled outside the CRM system.

Rent Manager's owner payout calculations and distribution schedules represent accounting logic that cannot be represented in Twenty's CRM layer. These calculations export as a reference CSV with all relevant owner distribution data, handled separately during bookkeeping migration to maintain accuracy.

Staff members including property managers, accountants, and maintenance coordinators map to Twenty Workspace Members by email matching. Role-based permissions (Property Manager, Resident/Tenant, Owner, Vendor) transfer as a custom role field on the Workspace Member record for proper access control.

Rental prospects and lease inquiries that never converted to tenants migrate as cold People records. Inquiry date, source (website, referral, walk-in), and unit of interest store as custom fields, preserving the complete leasing funnel analysis data for future marketing and follow-up activities.

Move-in, move-out, and routine inspection records create a custom Inspection object linked to the Unit. Inspection type, inspection date, condition ratings, and associated photos migrate as custom fields. Photo attachments are re-uploaded to Twenty's file storage and linked to the Inspection record by ID for complete documentation.