Migrate from Acquaint CRM to Pipedrive

Property listings have no native Pipedrive equivalent — every property becomes a Deal with custom fields

Acquaint's Property Listing module is a first-class object with photographs, floor plans, virtual tours, EPC uploads, and portal-sync status. Pipedrive has no property entity — the migration treats each Acquaint property as a Deal, and property-specific attributes (EPC rating, bedroom count, tenure, portal status) land as custom fields on the Deal. Teams must decide which property attributes are worth preserving as custom fields versus which can be dropped or attached as files. Pipedrive's dealFields API endpoint (/dealFields) handles custom field creation, but the mapping plan needs to name each property attribute before the migration runs.

Acquaint's Client Accounting module has no Pipedrive equivalent — financial records require a separate workflow

Acquaint's Client Accounting module handles tenant rent ledgers, deposit holds, bank imports, and credit references — this data sits outside Pipedrive's data model entirely. Pipedrive has no ledger, accounting, or payment-tracking module; these capabilities are left to integrated accounting tools like Xero, QuickBooks, or FreeAgent. We migrate accounting-related notes as formatted text on the Organization record for audit reference, but the actual financial records (balances, payment history, deposit status) must be exported from Acquaint and reimported into your accounting platform post-migration. This is a data-decision moment: archive old ledgers or keep them accessible as PDF exports.

Pipedrive's token-based API rate limits (December 2024 policy) affect bulk migration throughput

Pipedrive introduced token-based rate limits in December 2024, placing a ceiling on API requests per token per time window. For large Acquaint datasets (25,000+ records), FlitStack AI manages request pacing to avoid 429 responses — splitting large batches, adding backoff between requests, and resuming from checkpointed offsets when limits reset. The migration plan includes a rate-limit contingency: if Pipedrive's API returns a 429, the migration pauses automatically and resumes within the next allowed window. This adds buffer time to the migration estimate for large datasets but prevents partial or corrupted inserts.

Acquaint owner-to-Pipedrive-user matching requires email address resolution before data lands

Acquaint stores owner_id on contacts, companies, and properties — these reference Acquaint user accounts. Pipedrive's owner_id on People, Organizations, and Deals is a Pipedrive User ID. The migration resolves owner references by matching Acquaint owner email addresses to Pipedrive user email addresses. If an Acquaint owner has no corresponding Pipedrive user, their records land under a designated fallback Pipedrive user and are flagged in the migration report for manual reassignment. Teams must ensure all active Acquaint owners have Pipedrive user accounts created before the migration runs.

Workflows, automations, e-signing configurations, and SMS templates do not migrate

Acquaint workflows (property-viewing reminders, tenant-task triggers, viewing-booking automations) and e-signing configurations are platform-native constructs with no export format compatible with Pipedrive. Similarly, SMS templates with Acquaint merge-field syntax do not port to Pipedrive's email template system. We export Acquaint workflow definitions as JSON — each workflow's trigger conditions, actions, and field references become a requirements document for your Pipedrive admin to rebuild using Pipedrive's Automations feature (available on Advanced plans and above). Planning 2–4 hours per significant workflow for Pipedrive reconstruction is a reasonable estimate.