Migrate from AgileCase to Pipedrive

AgileCase Contact maps 1:1 to Pipedrive Person. Name, email, phone, job title, and company association transfer directly. The company's primary key resolves to a Pipedrive Organization ID before Persons insert, so Organizations must migrate first. During migration, we also preserve the original created timestamp as add_time, and any existing owner_id is translated via email lookup to the corresponding Pipedrive user ID to maintain audit continuity.

AgileCase Company maps to Pipedrive Organization. Domain, industry pick-list, and employee count map directly. Industry pick-list values require value-by-value mapping because AgileCase and Pipedrive use different enumerated sets. Parent-company hierarchies map to the 'parent_org_id' field in Pipedrive. Additionally, we preserve the company's original createdate as add_time, and map any annual revenue to a custom numeric field on the Organization, ensuring historical financial context carries over.

AgileCase Case is the primary work unit and maps directly to Pipedrive Deal. The case name becomes the deal title, case value maps to deal_value, and the AgileCase status value maps to a Pipedrive Pipeline stage name. One AgileCase pipeline = one Pipedrive Pipeline object. Custom properties on the Case map as Pipedrive deal_fields using the hash-key lookup.

AgileCase status pick-list values (e.g., New, In Progress, Under Review, Resolved) map value-by-value to Pipedrive stage names within the target Pipeline. If AgileCase uses statuses that have no Pipedrive equivalent, they migrate as a custom pick-list field and Pipedrive admins select the nearest stage during setup.

AgileCase priority (Low, Medium, High, Critical) has no native Pipedrive equivalent on the Deal object. We create a Pipedrive custom field (priority_cf) as a pick-list and map values directly. Pipedrive's built-in deal_priority field does not exist; this custom field is the equivalent tracking mechanism.

AgileCase call records (subject, duration, outcome, owner, timestamp) map to Pipedrive Activity records where type = 'call'. The subject becomes the activity subject, and the AgileCase outcome maps to the notes field. The activity owner resolves by email match to a Pipedrive user. Uncompleted calls omit the 'done' flag in Pipedrive's API payload.

AgileCase email records (subject, body, direction, timestamp, owner) map to Pipedrive Activity records where type = 'email'. Pipedrive's email activities do not store the full email body in the same structured way — the subject becomes the activity subject and the body content is stored in the 'note' sub-object. Inbound/outbound direction maps to Pipedrive's 'flag' field.

AgileCase meeting records (subject, start time, end time, location, owner) map to Pipedrive Activity records where type = 'meeting'. Pipedrive requires both busy_flag and done_flag to be set correctly in the API payload. Meetings without a fixed time in AgileCase get a default start time during migration to avoid Pipedrive validation errors.

AgileCase custom properties on Cases migrate as Pipedrive deal_fields. Pipedrive requires pre-creating each custom field via POST /dealFields and capturing the returned 40-character hash key before records insert. AgileCase field type (string, number, date) maps to Pipedrive field_type (varchar, int, date). Pick-list custom fields require value-by-value mapping in Pipedrive's field editor.

AgileCase file attachments download to local storage, then re-upload via Pipedrive's Files API (POST /files) with the base64-encoded content. Each file is linked to its parent record (Person, Organization, or Deal) using the item_id and item_type parameters in the API payload. Files larger than Pipedrive's 100 MB limit per file are flagged for manual handling.

AgileCase workflows, automations, and workflow scripts do not have a direct Pipedrive equivalent and are not migrated. They must be rebuilt manually in Pipedrive's Automation builder (trigger + action logic) or via an external automation platform. We provide a workflow definition export from AgileCase as a rebuild reference for your Pipedrive admin.

AgileCase users and case owners resolve to Pipedrive users by email address match. Unmatched owners are flagged before migration and assigned to a fallback Pipedrive user or held for invitation before the deal migration step. This prevents orphaned deals with null owner_id in Pipedrive, which the API rejects.