Migrate from BackDocket to Pipedrive

BackDocket contact records map 1:1 to Pipedrive People. The primary contact email, phone, address, and name fields transfer directly. BackDocket clients without an email address are flagged during validation because Pipedrive requires an email for lead routing in some automation triggers.

BackDocket organization-level records (if separate from contacts) map to Pipedrive Organizations. Industry, website, address, and employee-count fields map to their Pipedrive counterparts. Multi-contact clients each link to the same Organization record, replicating BackDocket's client-company structure. We also preserve the organization’s primary contact email on the Person record for smooth follow-up and duplicate detection in Pipedrive.

Each BackDocket matter becomes a single Pipedrive Deal. The matter name maps to Deal title, case amount or billing estimate maps to Deal value, and matter status maps to a Pipedrive pipeline stage. Multiple BackDocket matter types require multiple Pipedrive pipelines so stage pick-lists stay relevant per practice area.

BackDocket matter statuses (Open, Pending, Closed Won, Closed Lost, etc.) map to Pipedrive Deal stages by value. Each matter type may use a different status set, so we apply value-by-value mapping per Pipedrive pipeline to ensure stage labels match the source semantics.

BackDocket practice-area categorization (personal injury, family law, corporate, etc.) has no direct Pipedrive equivalent. We create a Matter_Type__c custom pick-list field on the Deal object and populate it from the source matter type field so reporting by practice area is preserved.

BackDocket document references are exported from the onsite data warehouse and re-uploaded to Pipedrive Files, then linked to the corresponding Deal (for matter documents) or Person (for client correspondence). Files over 25MB require chunked upload or alternative storage with a link field in Pipedrive.

BackDocket intake form submissions represent pre-client leads. We map them to Pipedrive Leads (which share the same field schema as Deals) and populate the form field values as custom fields on the Lead record. Once the intake converts to a client, the Lead converts to a Person and Organization in Pipedrive's standard workflow.

BackDocket calendar entries (court dates, client meetings, filing deadlines) map to Pipedrive Activities of type Event with the original start/end timestamps preserved. Court-appearance events link to the Deal; client-meeting events link to the Person. We retain the original event description in a custom field to preserve context after migration, and we set activity reminders based on the original due dates to maintain schedule continuity.

BackDocket tasks map to Pipedrive Activities of type Task. The task subject, due date, assignee (owner), and completion status transfer directly. BackDocket task sequences (ordered multi-step workflows) do not map — they must be rebuilt as Pipedrive Automation sequences, which we document in the rebuild reference.

BackDocket staff records are resolved to Pipedrive Users by email match. Unmatched BackDocket users (such as archived or inactive staff) are assigned to a fallback Pipedrive user or marked with a custom field so owner attribution on migrated matters is preserved as a reference.

BackDocket's claim management and billing-entry records have no native Pipedrive equivalent — Pipedrive has no accounting module. We preserve claim amounts, billing status, and invoice references as custom fields on the Deal for reporting continuity. For full billing history, a link to the original BackDocket export is stored in a custom field.