Migrate from ResMan to Nutshell

Pre-migration discovery and ResMan API authentication

FlitStack schedules a discovery session to audit the ResMan environment: property count, resident volume, lead pipeline size, work order backlog, and custom field inventory. We authenticate to the ResMan Partner API using team credentials and confirm whether impersonation scope is available — critical for session continuity during large batch exports. If the Partner API is unavailable or MFA blocks unattended access, we pivot to a file-based export using ResMan's bulk report tool and normalize the CSV before mapping. A schema inventory document is produced covering every ResMan field and its Nutshell destination.

Data extraction, deduplication, and field transformation

FlitStack extracts all CRM-layer records from ResMan: properties, residents, leads, leases, work orders, and vendor contacts. Email-based deduplication runs across resident records — duplicates are flagged with the household relationship plan before any record is written to Nutshell. Custom fields (Section 8 flag, LIHTC code, fraud tag, deposit amount) are normalized to Nutshell's custom field naming conventions. Lease status values are mapped to Nutshell deal stages via the pre-agreed value table. All ResMan internal IDs are stored in custom traceability fields on the destination records for delta-run matching.

Sample migration with field-level diff

A representative slice of 50–100 records migrates first — typically one property's residents, one lead pipeline, and a handful of work orders. FlitStack generates a field-level diff report comparing source values against the Nutshell destination for every mapped field. You review the diff to verify deal amounts, resident emails, work order priority mapping, and custom field values. Any field-level errors are corrected in the transformation logic before the full run is scheduled. This step is the reconciliation checkpoint — it prevents bulk errors from reaching production.

Full migration with delta-pickup window

The full migration commits all validated records to Nutshell using the Nutshell API (app.nutshell.com/api/v1/json — JSON-RPC). A delta-pickup window of 24–48 hours runs concurrently, capturing any new residents, updated leases, new work orders, or lead stage changes that occur in ResMan during the cutover. After the window closes, the delta records are migrated and appended to the Nutshell dataset. FlitStack produces a final reconciliation report showing record counts by object, zero duplicate contacts, and a full audit log of every API operation. One-click rollback is available if reconciliation reveals gaps exceeding the agreed tolerance threshold.

Post-migration handoff and rebuild reference

FlitStack delivers a rebuild reference document listing every ResMan automation, workflow, report, and integration that does not migrate — organized by priority (critical, important, nice-to-have). ResMan workflow definitions are exported as JSON and handed off to your Nutshell admin for recreation using Nutshell's automation rules and sequences. Integration credentials for any third-party tools connected to ResMan are inventoried so they can be reconnected to Nutshell post-migration. Post-migration support is available for 30 days to address data discrepancies discovered after go-live.