Migrate from CASEpeer to Pipedrive

Each CASEpeer Client becomes a Pipedrive Person. The client's name, email, phone, and address fields map directly. The CASEpeer contact ID is preserved as a custom field on the Person record for traceability and delta-run de-duplication. This custom field, named source_contact_id__c, is indexed in Pipedrive so you can quickly locate the original CASEpeer contact during reconciliation or if you need to reference historical data after cutover.

Each CASEpeer Case becomes a Pipedrive Deal. The Case Title maps to Deal Name. The Case Value maps to Amount. CASEpeer Case Status values (Active, Settled, Closed, On Hold, Pending) map to Pipedrive Deal Stages via a value-mapping table you approve before migration runs.

CASEpeer Case Status is a pick-list with values like Active, Settled, Closed, On Hold, and Pending. Pipedrive Deal Stages are defined per Pipeline and are fully customizable. We build a value-map table during discovery and submit it for your approval before the migration run commits.

CASEpeer Case Type stores values like Litigation, Pre-Lit, Motor Vehicle Accident, Slip and Fall, and Medical Malpractice. Pipedrive has no native case_type equivalent on Deals. We create a Pipedrive custom pick-list field (case_type__c) and map each value during import. During import, each case type value is matched to the pick-list entry, so Pipedrive reports and filters reflect the same classification your team used in CASEpeer.

CASEpeer Calendar Rules encode court-specific filing deadlines per jurisdiction. Pipedrive Activities support due dates and reminder flags but lack jurisdiction-aware rule logic. We convert each Calendar Rule to a Pipedrive Activity with the deadline as the due date and a reminder set to your preferred advance notice window.

CASEpeer Notes attached to a Case or Client become Pipedrive Notes. We preserve the original create timestamp, the author name, and the linked record. Rich-text formatting is preserved where CASEpeer supports it. The migrated notes appear in Pipedrive's activity feed linked to the corresponding Deal or Person, allowing your team to view case-related context directly within the CRM interface.

CASEpeer documents stored within a Case are exported and re-hosted in Pipedrive Files, linked to the corresponding Deal and Person. Files over 25MB are flagged for alternative storage — your admin chooses the destination before the migration run. After migration, the URL reference in Pipedrive points to the stored file location, ensuring users can open documents without leaving the CRM, provided they have appropriate access permissions.

CASEpeer custom intake fields (insurance carrier, policy number, incident date, etc.) have no Pipedrive native equivalent. We create corresponding custom fields on the Deal object and map each field type (text, date, number, pick-list) individually during the import sequence. Each custom field is given a descriptive label matching the CASEpeer field name, and a corresponding API key is generated in Pipedrive for future integrations or API queries.

CASEpeer attorneys and staff users are matched to Pipedrive users by email address. Unmatched users are flagged before migration — your team either invites them to Pipedrive first or assigns their records to a fallback Pipedrive user to prevent orphaned Deals.

CASEpeer activities linked to a Case — calls logged, meetings scheduled, tasks created — migrate as Pipedrive Activities. Each Activity is linked to the corresponding Deal and Person. Original timestamps, owners, and subject lines are preserved during import. This linking ensures that the full activity history for each case appears in Pipedrive’s timeline, enabling attorneys to review past interactions without switching between CASEpeer and the CRM.