Migrate from ResMan to HubSpot

ResMan properties map to HubSpot companies. If the property itself carries address, type, and unit count, those land as company fields. FlitStack can alternatively create a Property custom object to preserve the unit-hierarchy relationship that HubSpot companies don't natively store.

HubSpot has no native unit concept. FlitStack creates a Unit custom object linked to the Property company via a lookup field. Fields include bedrooms, bathrooms, sq footage, market rent, and unit status (vacant, leased, notice). This custom object preserves the property-unit hierarchy that HubSpot companies don't natively store.

ResMan tenants map directly to HubSpot contacts. Name, email, phone, move-in date, and current unit assignment migrate. A tenant's lease history (prior units, prior leases) can be stored as contact properties or association notes. This preserves complete residency history for lease renewal outreach and tenant screening purposes.

A ResMan lease (term dates, rent amount, deposit, status) becomes a HubSpot deal. HubSpot's deal stages can be remapped to lease lifecycle stages: Lease Pending, Active, Expiring Soon, Month-to-Month, Ended. Custom fields on the deal carry term dates, monthly rent, and deposit amounts.

HubSpot has no native payment recording object. FlitStack creates a Payment custom object linked to the Contact and the Deal (lease). Fields include payment date, amount, method, and charge type. Payment history supports renewal risk reporting in HubSpot dashboards, allowing you to identify tenants with payment patterns that may indicate renewal risk.

ResMan charge codes (late fees, pet rent, parking, utility charges) map to a Charges custom object or deal line items. Custom pick-list fields preserve the charge category. Past-due charges can trigger HubSpot workflow enrollments once rebuilt, enabling automated late payment follow-ups and escalation procedures.

ResMan work orders map to HubSpot tickets. Category, priority, status, description, and assigned staff transfer. HubSpot's ticket pipelines replace ResMan's work-order status workflow — categories map to pipeline stages, priority maps to the priority pick-list. This enables maintenance team tracking and performance reporting within HubSpot.

ResMan staff users are matched to HubSpot users by email address. Unmatched users are flagged before migration. ResMan's property-level staff assignments become HubSpot team assignments or manual owner overrides on records. This ensures proper access control and accountability for migrated property data.

ResMan lease documents and tenant addenda are downloaded and re-uploaded as HubSpot file attachments linked to the corresponding contact and deal record. Original filenames and upload dates are preserved. This maintains complete document history and legal reference for each lease and tenant relationship.

ResMan screening results (credit score, background check, income verification) migrate as custom properties on the contact. No native HubSpot equivalent; custom number and date fields capture the key screening metrics for reference. This preserves tenant screening history and supports future screening validation workflows.