Migrate from MRI Software to Pipedrive

MRI lease data has no native Pipedrive equivalent — custom fields are required

Pipedrive Deals are pipeline-tracked deals, not lease records. Fields like security deposit amount, rent payment frequency, lease start date, and CAM reconciliation summary have no Pipedrive native equivalent. We create custom fields on the Deal object for each of these, but Pipedrive's custom field references use account-specific hash keys (e.g., a47b...) that cannot be pre-provisioned by name across accounts. FlitStack creates these fields during the migration run — plan for a custom field schema review before the test migration commits so you can rename or re-type fields before the full run.

MRI's multi-site entity model flattens in Pipedrive's flat Organization hierarchy

MRI allows an entity to operate across multiple sites with one designated as active for daily processing. Pipedrive Organizations are entirely flat — there is no native multi-site or parent-subsidiary Organization hierarchy. If your MRI portfolio uses multi-site entity mapping (common for property managers running MRI across regional offices), we collapse this into Tags on the Organization record in Pipedrive. Each site gets a Tag (e.g., 'Site: Northeast', 'Site: Southwest') that your team can filter on. The alternative is creating separate Pipedrive Organizations per site, which inflates record count significantly.

MRI API partner-key rate limits constrain export throughput

MRI's partner API keys allow 1,000 requests per five-minute rolling window with 24-hour manifest caching. For portfolios with 50,000+ records across tenants, owners, leases, units, and work orders, this rate limit means a single full export can take multiple hours. FlitStack manages the pagination and backoff automatically, but we surface this constraint in the migration plan so you can allocate a weekend window for the export phase. If your MRI instance is on-premise rather than SaaS, the export path requires database-level access which adds a coordination step with your MRI administrator.

Pipedrive's token-based rate limits apply to write operations during migration

Pipedrive introduced token-based rate limits in December 2024 that vary by subscription tier. FlitStack uses Pipedrive's Bulk API where possible to batch writes, but custom field creation, Activity writes, and Organization/Person creates each count against per-token limits. Pipedrive's documentation notes that Enterprise accounts receive higher rate limits. We query your Pipedrive plan tier before migration planning and calibrate the write throughput accordingly — migrations against an Essential-tier Pipedrive account run slower than against an Enterprise account.

MRI rent payment history does not migrate as financial records

MRI stores tenant ledger entries — rent payments, late fees, security deposit transactions — as detailed financial records. Pipedrive is not a financial system of record and cannot hold ledger entries. We migrate the most recent 12 months of payment status (paid, outstanding, partial) as Notes on the Person record, but the full ledger history including individual transaction amounts, GL codes, and bank reconciliation data stays in MRI's financial module. You must retain MRI read access or export the full ledger to CSV before decommissioning if you need payment history for audits.