Migrate from Acumen to Pipedrive

Pipedrive API rate limits require queue-based throttling

Pipedrive enforces token-based rate limits of 100 requests per minute across all API endpoints. Acumen datasets with 10,000+ records can trigger 429 Too Many Requests responses during bulk import. FlitStack implements queue-based throttling with exponential backoff and respects the Retry-After header in every 429 response — no records are silently dropped. If your Acumen export includes dense activity history (logged hours, task completions, notes), plan for a longer migration window to accommodate throttling.

Pipedrive custom fields use hash keys — not human-readable names

When you create a custom field in Pipedrive, the system generates a 40-character hash key (e.g., a1b2c3d4e5f6...) as the field identifier for API calls. This key differs from account to account even for identically named fields. FlitStack captures each Acumen custom field's source key and maps it to the newly created Pipedrive hash key at migration time. Without this mapping, data populates the wrong fields or fails validation silently. We store the Acumen field key as a reference attribute on the Pipedrive field for audit continuity.

Acumen workflows and approval chains do not migrate

Acumen's workflow engine — including approval chains, conditional triggers, and automated assignment rules — has no structural equivalent in Pipedrive. Pipedrive offers Sequences (email drip campaigns) and Automations (trigger-based actions), but these are fundamentally different constructs. FlitStack exports your Acumen workflow definitions as a structured JSON reference file that your Pipedrive admin can use to rebuild logic in Pipedrive's automation builder. Expect to spend 1–3 days rebuilding critical workflows depending on complexity.

Acumen project task hierarchy collapses to flat activities in Pipedrive

Acumen projects use WBS (Work Breakdown Structure) to nest tasks with parent-child relationships, dependencies, and cost-code assignments. Pipedrive activities have no hierarchical model — every task or event is a flat record linked to a deal or person. FlitStack migrates each Acumen WBS task as an individual Pipedrive activity and links it to the deal representing the parent project. The WBS hierarchy is lost unless you request a custom junction object approach where we attach a level indicator and parent-task reference as custom fields.

Acumen cost-code data requires custom field creation before import

Acumen cost codes, budget amounts, planned costs, and actual costs are core to its data model but have no native equivalent in Pipedrive. FlitStack creates custom numeric fields on Pipedrive deals (representing Acumen projects) to capture this data. If your Acumen setup uses cost-code pick-lists, we map those values to Pipedrive pick-list fields created as part of the migration. The Acumen field ID is preserved as a reference attribute so your team can trace any budget figure back to its source.