Migrate from ResMan to Pipedrive

Property-to-Unit hierarchy collapses into a flat Organization model

ResMan's data model treats Properties and Units as a parent-child hierarchy — each Property contains N Units with individual availability, type, and lease status. Pipedrive Organizations have no child entity, and Pipedrive's native data model does not include a Units concept. We map Units to a Pipedrive custom object (available on Professional and higher plans) or to Organization custom fields. Starter-plan Pipedrive accounts cannot create custom objects at all; in that case, unit details must be stored as text or pick-list fields on the Organization record, which limits filtering and reporting on per-unit data. This structural mismatch is the highest-impact gotcha for multi-property ResMan accounts — FlitStack surfaces the pre-migration schema plan so your Pipedrive admin knows exactly which fields or custom objects to create before data lands.

No native lease, rent, or deposit tracking exists in Pipedrive

ResMan tracks lease terms, start and end dates, monthly rent amounts, and security deposits as first-class fields on the Lease object. Pipedrive has no Lease object and no financial transaction object. Lease data must translate to a Deal with a custom field set: Lease_Start__c, Lease_End__c, Lease_Term__c, Monthly_Rent__c, and Security_Deposit__c. Payments and Charges have no Pipedrive equivalent — FlitStack creates Notes on the Person or Deal with the transaction amount, date, and type, but these are not financial records in Pipedrive's sense. Rent-roll reporting, balance-due tracking, and security deposit accounting must be rebuilt as custom reports or in a separate accounting tool post-migration.

Maintenance ticket priority taxonomy has no Pipedrive equivalent

ResMan maintenance tickets carry priority levels, work-order numbers, category assignments, and a full status-change audit trail. Pipedrive Activities model tasks and to-dos with a single done/undone flag and no native priority structure. We map ResMan ticket priority to a custom pick-list field on the Activity, and the full ticket description migrates as the Activity note. However, Pipedrive's Activity model does not support a work-order number field natively — that must be added as a custom text field. Multi-step maintenance workflows with approval routing must be rebuilt in Pipedrive Automations; there is no workflow migration path.

Pipedrive API daily write limits constrain migration batch sizing

Pipedrive enforces 10,000 POST/PUT requests per user per 24 hours on all plans. For ResMan accounts with large tenant, lease, and payment volumes, this cap can extend the migration timeline. FlitStack batches write operations to respect the daily quota, monitors X-RateLimit-Reset headers (which return Unix timestamps, not seconds-until-reset), and retries with exponential backoff on HTTP 429 responses. A 50,000-record migration with full activity history may require multiple days of API writes within the quota window — this is factored into the timeline estimate.