Migrate your ResMan data

Properties are the top-level organizational unit in ResMan containing multiple Units. We map them directly to the destination's Companies or Properties object with address, type, and metadata fields preserved intact.

Units belong to Properties and contain lease status, rent amounts, and unit details. We map Unit records 1:1 and flag vacant vs. occupied status explicitly in the migration scope.

Residents are the primary contact records tied to a Unit and Lease. We map Residents to Contacts and preserve the Unit assignment, subsidy type, and compliance flags for affordable housing.

Leases link a Resident to a Unit with term dates, rent amounts, and deposit information. We map Leases to Deals or Opportunities and preserve the full lease lifecycle including renewal history.

Payments are tied to Leases and Residents. We map payment records with amount, date, method, and allocation details. Note that partial payments and payment plans require value-level mapping to match destination accounting.

Charges and fees include rent, utility billing, late fees, and miscellaneous charges. ResMan's utility billing integration creates charges tied to vacating workflows. We map these to invoice line items or custom objects depending on destination structure.

Maintenance tickets track work orders tied to Properties or Units with priority, status, and assignment. We map tickets to Cases with full description, photos, and work order history preserved.

Documents include lease agreements, addenda, notices, and resident paperwork stored per entity. We export documents as binary blobs with metadata and re-attach them to the corresponding migrated records in the destination.

ResMan captures leads through websites and contact center modules. We map leads to CRM Leads or Contacts depending on destination's lead model, preserving source attribution and pipeline stage.

Identity validation results are stored per resident with verification status. We map verification status as a custom property on the Contact record since destination CRMs handle this differently.

Section 8 subsidy data, income limits, and compliance dates are stored on Residents and Leases. We map these to custom properties or Compliance objects and flag them for review since regulatory requirements vary by destination.

Staff accounts include role assignments and property access. We map users to destination Users or Contacts depending on whether they are billable staff or administrative contacts.

Custom reports are ResMan-specific report definitions that do not export in standard formats. We do not migrate report definitions; instead we migrate the underlying data so reports can be rebuilt on the destination platform.

Chatbot conversations and contact center interactions are ephemeral communication records that do not have a standard schema equivalent in most destination CRMs. We do not migrate these records.