Migrate from CaseManager to Pipedrive

CaseManager cases map 1:1 to Pipedrive deals. Case title becomes Deal title, case status maps to Pipedrive deal status (open/won/lost), and close date maps to close date. Priority and category from CaseManager migrate as custom fields since Pipedrive has no native priority/type attribute on deals.

CaseManager contacts linked to a case map to Pipedrive People. Name, email, phone, job title, and address fields migrate directly. If a CaseManager contact has no email, we flag the record before migration so your team can fill it in Pipedrive before the deal association runs.

CaseManager organizations map to Pipedrive Organizations. Organization name, domain/website, industry, and address fields migrate directly. Parent-child hierarchy is not native in Pipedrive — we surface hierarchy as a custom org field and your admin can choose to flatten or keep it as a reference attribute.

CaseManager activity history (call logs, email records, meeting notes) migrates as Pipedrive Activities attached to the corresponding deal. We preserve original activity dates and owner attribution by creating activities with the original timestamp and assigning to the resolved Pipedrive user.

CaseManager custom fields on cases require pre-creation in Pipedrive via the /dealFields API endpoint. We capture the hash key returned by Pipedrive during field creation and use it in the mapping workbook so values load correctly. Pipedrive supports 16 custom field types — we match CaseManager field types to the closest Pipedrive equivalent.

CaseManager owner IDs are resolved by email match against Pipedrive users. Unmatched owners are flagged before migration so your team either creates the Pipedrive user first or assigns those cases to a fallback owner. No deal lands without a valid Pipedrive owner_id.

CaseManager file attachments on cases re-upload to Pipedrive attached to the corresponding deal. File size limits apply — Pipedrive's default is 25MB per file. Inline images in notes are extracted, downloaded, and re-hosted as Pipedrive file attachments.

CaseManager's native priority field (critical/high/medium/low) has no Pipedrive equivalent on deals. We create a Pipedrive custom pick-list field and map values one-to-one. Probability in Pipedrive is separate from priority and can be set per stage — we configure this during Pipedrive setup.

If CaseManager tracks case type or category (e.g., bug, feature request, billing), we create a Pipedrive custom pick-list to preserve the taxonomy. Stage-based pipelines in Pipedrive can serve a similar routing purpose — your admin decides whether to use the custom field or map types to pipeline stages.

CaseManager status-change timestamps and audit trails have no direct Pipedrive equivalent — Pipedrive tracks current stage and last activity, not full status history. We preserve the most recent status-change date as a custom datetime field and note the full history in the deal description or a linked note for audit reference.

CaseManager workflows and case-assignment rules cannot migrate to Pipedrive — the logic is platform-specific and the trigger models differ entirely. We export your workflow definitions as a rebuild reference document so your Pipedrive admin can reconstruct them in Pipedrive Automations or using a tool like Zapier or Make.