Migrate from Dibcase Legal Case Management to Pipedrive

Dibcase 'Active', 'Deferred', 'Inactive', and 'Other' clients migrate to Pipedrive Person records. The person's name, email, phone, and address fields map directly. Dibcase Client_ID stores as Source_System_ID__c for traceability. Inactive and Deferred clients preserve their status history and linked case associations in Pipedrive, maintaining the full client record even after active representation ends. Historical client data remains queryable in Pipedrive's CRM format.

Dibcase clients with status 'Lead', 'Rejected Lead', 'Closed', or 'Archived' route to Pipedrive Leads instead of People. The Dibcase lead_stage field maps to a custom Lead field in Pipedrive so the intake routing logic is preserved for reference. This ensures that rejected prospects and closed cases retain their original intake classification, allowing your team to analyze historical lead sources and closed-case outcomes in Pipedrive's reporting tools.

Dibcase allows N:N contact-per-client relationships. Pipedrive supports one primary Person per Organization. Additional contacts from Dibcase migrate as comma-separated custom text fields on the Organization record (e.g., Secondary_Contacts__c). Your team decides which contact becomes primary based on communication frequency, relationship type, and case involvement to ensure the most relevant person appears on the Deal.

Each Dibcase case becomes a Pipedrive Deal. The Dibcase case name maps to Deal title. All legal metadata — SSA/VA form type, hearing date, stage-entry timestamps, SSI/SSDI status — migrates as custom fields on the Deal so the legal context is visible without navigating away from the deal record.

Dibcase case statuses (Initial Claim, Hearing, Appeal, etc.) map to Pipedrive Deal stage names matching the pipeline structure. Dibcase's internal status values (Active, Deferred, etc.) map to a custom pick-list field Case_Status__c on the Deal so both the Pipedrive workflow stage and Dibcase operational status are visible.

Dibcase pipelines map 1:1 to Pipedrive Deal Pipelines. Each pipeline's stages become Pipedrive stage names within that pipeline. If your firm runs separate pipelines for SSD and PI cases, those become separate Pipedrive pipelines for clean reporting. Stage order, probability weights, and stage names replicate Dibcase's workflow logic exactly so your team's existing kanban mental model transfers to Pipedrive without retraining.

Dibcase lead stages are a core object with configurable stages and kanban cards. Pipedrive Leads use a status field but no native lead-stage equivalent. We migrate the Dibcase lead_stage value to a custom Lead field (Lead_Stage__c) and preserve the kanban order as a numeric sort_index field for rebuild reference.

Dibcase tasks migrate as Pipedrive Activities with type='task'. Original due dates, task titles, assigned users (resolved by email match to Pipedrive users), and completion status carry over. Task templates do not migrate — those export as a reference document for Pipedrive automation rebuilding.

Dibcase notes on cases and clients migrate as Pipedrive Notes linked to the corresponding Person or Deal. Original timestamps and note authors are preserved as custom datetime and text fields if Pipedrive does not surface them natively. This ensures the full audit trail of case communications, attorney annotations, and client interactions is available in Pipedrive for ongoing case reference and compliance documentation.

Dibcase documents and file attachments migrate as Pipedrive File attachments on the corresponding Person or Deal record. Files download from Dibcase storage and re-upload to Pipedrive. Large document volumes may require API batching; Dibcase's ERE file retrieval options (normal pickup, full-folder, exhibit pull) become file-folder naming conventions in Pipedrive.

All Dibcase custom fields — SSA form field sets, VA intake fields, ERE batch metadata, custom practice-area properties — migrate as Pipedrive custom fields on the corresponding entity (Person, Organization, Deal, or Lead). Field types map: text→string, picklist→picklist, date→date, number→number. The Pipedrive field key (a hash) is generated per account, so custom fields are created in the destination account during schema setup.

Dibcase tiers clients by billable count (51–100: $99/mo; 101–300: $199/mo; 301–500: $299/mo). The tier label migrates as a custom pick-list field (Client_Tier__c) on the Organization or Deal for reporting continuity, since Pipedrive has no native per-client billing model. This preserves your firm's client-tier segmentation for internal reporting and helps finance teams reconcile Pipedrive activity data with Dibcase's billing records during the transition period.

Dibcase task templates, SMS workflows, and intake automations have no Pipedrive equivalent. FlitStack exports workflow definitions as a structured reference document (JSON/CSV) so your Pipedrive admin can rebuild automations using Pipedrive's Automation builder or Advanced Automation (Advanced+ plan). This is a manual rebuild step, not a data migration.

Dibcase's SSA ERE connectivity, batch queue processing, and staged upload management are Dibcase-specific features with no Pipedrive equivalent. ERE-related case metadata (SSN, ERE status flags, exhibit data) migrates as read-only custom fields on the Deal. The ERE connectivity itself must be worked around using Dibcase's continued standalone access or a third-party integration.

The data underlying Dibcase reports (case counts, hearing status, revenue by practice area) migrates as structured Deals and Activities in Pipedrive. Pipedrive's native Insights reporting then replaces the Dibcase report builder for pipeline analytics. Historical report data that is not stored as structured records does not migrate.