Migrate from Lead Docket to Pipedrive

Lead Docket leads carry both contact data and case data on a single record. FlitStack splits this into Pipedrive Person (contact fields) and a Deal (case fields linked by Person ID). The Person carries name, email, phone, and source; the Deal carries case type, status, and custom fields. Attorney assignment resolves to a Pipedrive user lookup if the attorney has a Pipedrive seat, or stores as a custom field if not.

If Lead Docket stores secondary contacts separate from leads (e.g., opposing counsel, referral sources), these map directly to Pipedrive People. Custom fields on the contact attach as Pipedrive custom fields on the Person record. No deal association is required unless the contact is linked to a case.

Lead Docket case types (e.g., Personal Injury, Workers' Comp, Family Law) have no native Pipedrive equivalent. We create a Case_Type__c custom pick-list on the Pipedrive Deal object and map values one-to-one. If the case type names differ from standard pick-list values, value_mapping rows are added per case type.

Lead Docket's 11 default statuses (New Lead, Qualified, Consultation Scheduled, etc.) map to Pipedrive deal stages within a migration pipeline. Each Lead Docket status name becomes a stage label; stage order and probability percentages are preserved. If you use custom statuses in Lead Docket, those are added as additional stage rows.

Lead Docket Source Rules auto-populate the Marketing Source on inbound leads, tracking where the lead originated (Google Ads, referral, partner channel, etc.). Pipedrive has no native marketing source field. We create a Marketing_Source__c text field on Pipedrive People and populate it from Lead Docket's source value for reporting continuity.

Lead Docket's attorney assignment is an object relationship to a user in the platform. In Pipedrive, each user is a Person record under the same workspace. We resolve attorney assignment by matching the Lead Docket user email to a Pipedrive user account and populate Deal.owner_id. If the attorney does not have a Pipedrive seat, we store their name as a fallback custom field and flag it for admin review.

Lead Docket custom fields on leads are defined per-object and support text, number, date, pick-list, and checkbox types. Each custom field is re-created as a Pipedrive custom field on the corresponding object (Person or Deal) with the matching field type. Pick-list custom fields in Lead Docket require a value_mapping step in Pipedrive. The field key in Pipedrive is a generated hash — we capture it during setup and use it in the bulk load.

Lead Docket tracks calls, emails, and notes on leads. Each activity type maps to the corresponding Pipedrive Activity type (call, email, or note). Original timestamps and the owning user are preserved. The activity is linked to the Pipedrive Person and/or Deal derived from the Lead Docket lead.

Lead Docket integrations (form handlers, chat widgets, referral partner pushes) can only create leads — they do not update existing records. These integrations cannot migrate to Pipedrive in place. Each integration must be reconfigured to target Pipedrive's People API endpoint. We document the current integration endpoints and the target Pipedrive configuration so your developer can rebuild them.

Lead Docket automations (a paid add-on) trigger on lead status changes, form submissions, and source rules. They route leads, send templates, and post to Filevine. Pipedrive automations are rebuilt from scratch using Pipedrive's Automation builder. We export the automation definitions as a text summary including trigger conditions, conditions, and actions so your Pipedrive admin can reference them during rebuild.

Lead Docket's Attorney Rotation feature distributes incoming leads across attorneys in a round-robin sequence. Pipedrive has no native round-robin assignment mechanism — this requires a Pipedrive Automation with a round-robin script or a third-party tool like Smartlead Router. We document the current rotation members and logic so it can be rebuilt in Pipedrive.

Lead Docket reports (Average Duration by Case Type, Revenue by Marketing Source, Leads Report, KPI dashboard) have no direct Pipedrive equivalents. The underlying data migrates so reports can be rebuilt in Pipedrive's Insights module or exported to a BI tool. We note the Lead Docket report names and column structure so the rebuild is traceable.