Migrate from ResMan to Freshsales

Audit ResMan data structure and plan Freshsales schema

We connect to the ResMan Partner API to enumerate all properties, units, tenants, leases, payments, maintenance tickets, and documents in scope. We audit custom field usage per entity, identify any non-standard data (Section 8 subsidy fields, utility account numbers), and document the relationship graph between entities. Simultaneously, we assess the target Freshsales plan for custom field capacity and create the custom Lease object, custom fields on Account and Contact, and any Unit custom module before data mapping begins. We deliver a schema setup checklist so your Freshsales admin can pre-create the required objects.

Connect to ResMan Partner API and export all entities

We authenticate to the ResMan Partner API using OAuth credentials provided by your ResMan account. We export properties, units, tenants, leases, payment history, maintenance tickets, and document metadata in structured JSON. For each entity we capture the original created date, last modified date, and owner assignment. We flag any ResMan records with missing required fields (e.g., tenant email addresses) before the migration run so your team can supply or approximate values rather than discovering gaps mid-migration.

Build field-level mapping and create custom objects in Freshsales

We apply the field mapping defined in the migration plan: properties to Accounts, tenants to Contacts (linked to Accounts), leases to the custom Lease object, payments to Activities, and maintenance tickets to Cases. We create the custom fields required for Section 8 data, utility references, and lease rider details. For each lookup relationship (Contact → Account, Lease → Contact, Lease → Account, Case → Account) we validate referential integrity — the parent record must exist in Freshsales before the child record is written. We sequence entity creation so Accounts are created first, followed by Contacts, then Lease and Case records.

Run test migration with field-level diff

A representative slice migrates first — typically 20–50 properties with their associated tenants, leases, and a sample of payment and maintenance records. We generate a field-level diff report comparing source values in ResMan against the destination values in Freshsales. You verify that lease start dates, Section 8 voucher amounts, maintenance priority assignments, and contact-to-account links are correct. We refine the mapping based on the diff before committing the full migration. Any Freshsales plan upgrades required by custom field count are identified at this stage.

Execute full migration with delta-pickup window

The full dataset migrates to Freshsales under rate-limit-aware batching. All entities are written with their original timestamps preserved as custom fields (since Freshsales sets Created Date at migration time). A 24–48 hour delta-pickup window captures any ResMan records modified or created during the cutover — typically new maintenance tickets or updated lease statuses. We validate record counts by entity type and run a reconciliation report comparing ResMan totals against Freshsales totals. An audit log records every operation, and one-click rollback is available if the reconciliation identifies unexpected discrepancies.

Deliver rebuild reference for automations and integrations

We document every ResMan workflow, screening integration, payment processor connection, and utility management setup that could not migrate. For each item we provide a rebuild reference: the trigger conditions, actions, and field logic from the ResMan configuration, formatted as a setup guide for Freshsales Workflows or a Freshworks Marketplace app recommendation. We also provide the ResMan integration audit checklist so your team can reconnect third-party tools with the correct Freshsales API credentials. Post-migration, your team configures Freshsales Workflows, invite property managers as Freshsales users, and reconnect third-party integrations independently or with support from the Freshworks Marketplace.