Migrate from Lawcus to Pipedrive

Lawcus contacts map directly to Pipedrive People using the contact's name, email, phone, address, and all standard properties. The contact's primary matter associations are preserved by linking each person to the migrated matter-deal record. Lawcus role labels on matter contacts (e.g., opposing counsel, billing contact) do not map to any Pipedrive field — we preserve these as a custom text field on the person record.

Lawcus matters become Pipedrive Deals. The matter name maps to deal title, matter status (open/closed/pending) maps to a Pipedrive stage value, and the matter description becomes the deal visible in the deal detail. Matter monetary values (estimated value, billed amount) map to deal value fields in Pipedrive. One Lawcus matter produces one Pipedrive deal — if a client has multiple matters, each becomes a separate deal linked to the same Person and Organization.

Lawcus workflow stages are custom-defined per practice area. We map each stage name to a Pipedrive stage value within the target pipeline. You select which Pipedrive pipeline corresponds to each Lawcus workflow. Stage-entry timestamps from Lawcus are preserved as custom datetime fields on the Pipedrive deal. Probability mapping follows your specification — Lawcus stages do not carry probability data, so we apply destination-side defaults per stage or your custom probability table.

Lawcus leads map to Pipedrive Leads — a dedicated object separate from People in Pipedrive. Source lead fields (name, contact info, source, status) map to the corresponding Pipedrive Lead fields. Lawcus lead notes and custom properties migrate to the Pipedrive Lead custom fields. After migration, your team routes leads through Pipedrive's lead routing and conversion workflow to convert qualified leads to People and Deals.

Lawcus activities map to Pipedrive Activities by type. Call activities become Pipedrive Calls, emails become Emails, tasks become Tasks, and meetings become Meetings. Original timestamps, owners, and subject lines are preserved. The activity's linked record (contact, matter) is re-linked to the corresponding migrated Person or Deal in Pipedrive. Note that Lawcus email body content migrates as activity notes; Pipedrive does not create a full email thread view from migrated emails.

Each Lawcus custom field requires a corresponding Pipedrive custom field to be created before migration. We create the Pipedrive custom field with the matching data type (text, number, date, dropdown, etc.) and map values. Dropdown (picklist) custom fields require value-by-value mapping when the options differ between platforms. Pipedrive custom field keys are hash-based and system-generated, so we create the fields in Pipedrive and map them during the migration run.

Lawcus workflows, stage-gate automation rules, and legal process templates do not migrate. Pipedrive's automation builder uses a different trigger-action model with deal-stage triggers, field-change triggers, and activity triggers. We export your Lawcus workflow definitions as a structured reference document your Pipedrive admin can use to rebuild equivalent automations in Pipedrive's automation editor.

Lawcus billable time entries attached to matters have no native Pipedrive equivalent — Pipedrive does not have a time-tracking or billing module. We preserve time entry data as custom fields on the migrated Deal record (total hours, last entry date, last billing status) and as a reference list attached to the deal for manual review. Rebuilding time tracking in Pipedrive requires a third-party integration or a separate time-tracking tool.

Lawcus document attachments on matters and contacts are downloaded and re-uploaded to the corresponding Pipedrive Deal or Person record as file attachments. We handle the download-reupload cycle for files up to the destination-side size limits. Files exceeding Pipedrive's attachment size limits are flagged for manual handling or alternative storage.

Lawcus users are matched to Pipedrive users by email address. Lawcus role assignments (Admin, Member) map to Pipedrive permission sets — Admin in Lawcus maps to a Pipedrive admin user. Unmatched owners (Lawcus users without a corresponding Pipedrive account) are flagged before migration so you can invite them to Pipedrive or assign their records to a fallback owner.

Lawcus practice areas (e.g., Family Law, Corporate, Litigation) are a taxonomy that does not exist in Pipedrive. We migrate practice area as a custom dropdown field on the Pipedrive Deal so you can segment reporting by legal practice area. You specify the target Pipedrive pipeline and stage mapping per practice area if your team uses different pipelines for different matter types.

Lawcus invoice and billing records do not map to any native Pipedrive object. We preserve invoice status (paid/unpaid/overdue) and outstanding balance as custom fields on the migrated Deal record. Billing history detail is preserved as an attached reference file. Pipedrive does not support invoice generation — your firm will need a separate legal billing system post-migration.