Migrate from Lawmatics to Pipedrive

Lawmatics Contact maps directly to Pipedrive Person. All standard fields (name, email, phone, address) migrate as direct mappings. Owner resolution happens by email match against Pipedrive users. Unmatched owners are flagged before migration so you can invite them to Pipedrive first.

Lawmatics Company maps to Pipedrive Organization. Company hierarchies (parent/child) are not natively supported in Pipedrive — we preserve the parent link as a custom field on the Organization for reference. Multi-company associations on a Lawmatics contact collapse to the primary Organization plus additional Organization links in Pipedrive.

Lawmatics Matter is the most complex migration object. Matters represent client cases with legal-specific status (New, Contacted, Consultation Scheduled, Retainer Sent, Active, Closed, etc.). Pipedrive Deals have a standard stage model. We map Matter status to Pipedrive Deal stages — your team decides which Lawmatics intake stages become Pipedrive pipeline stages. Practice area, case type, and attorney fields migrate as custom fields on the Deal.

Each unique Lawmatics Matter status value is mapped to a Pipedrive Deal stage name. We preserve the original status label as a custom field on the Deal so you can report on the original legal intake stage. Stage-order sequence is preserved as the stage index in Pipedrive.

Lawmatics Tasks map to Pipedrive Activities of type 'task'. Original due dates, task owners, and completion status are preserved. Open tasks migrate with their current status; completed tasks migrate as completed activities. Task Status values (e.g., In Progress, Completed) map to Pipedrive activity done flag.

Lawmatics Events (appointments) map to Pipedrive Activities of type 'event'. Original start/end times, location, event type, and linked contacts are preserved. Pipedrive does not support all-day events natively — we set a flag for all-day events. Event attendees not already in Pipedrive are linked to the event as note references.

Lawmatics Notes attach to Matters, Contacts, or Companies and migrate to Pipedrive Notes attached to the corresponding Person, Organization, or Deal. Rich-text formatting is preserved where Pipedrive's note format allows. Note timestamps and owner are preserved. Long notes are split if they exceed Pipedrive's character limit.

Lawmatics files (documents, PDFs, images) attached to Matters, Contacts, or Companies re-upload to Pipedrive Files attached to the corresponding Deal, Person, or Organization. Files exceeding Pipedrive's 100MB limit are flagged for chunked upload. Document-merge originals need to be re-linked manually post-migration since Pipedrive lacks a native document-merge engine.

Lawmatics custom fields on Matters (practice_area, case_type, court_info, statute_of_limitations, etc.) require custom fields in Pipedrive. We create these on the Deal object before migration. Field types are mapped: Lawmatics pick-list → Pipedrive enum; Lawmatics date → Pipedrive date; Lawmatics text → Pipedrive text. Custom field keys in Pipedrive are hashed (40-character strings) — we map these during migration by field label.

Lawmatics custom fields on Contacts (bar_number, practice_jurisdiction, referring_source, etc.) become Pipedrive custom fields on Person. Same type-mapping rules apply. Contact-type custom fields are created in Pipedrive before migration using the Pipedrive PersonFields API endpoint. Field labels are matched by name; hashed API keys are generated automatically during field creation. Unmapped field types default to text in Pipedrive unless a type conflict is flagged.

Lawmatics custom fields on Companies (firm_type, bar_association_id, malpractice_insurance, etc.) migrate to Pipedrive Organization custom fields. Created in Pipedrive before the main migration run using the OrganizationFields API. Field type mapping follows the same rules as Contact and Matter custom fields — pick-lists become enums, dates remain dates, and text fields map to text. Any unsupported field types in Lawmatics are flagged for manual review before the migration run starts.

Lawmatics Tags are multi-use labels applied to Contacts, Companies, and Matters. They map directly to Pipedrive Tags on the corresponding object. Multiple tags per record are preserved as Pipedrive's tag list. Tags used across object types (e.g., a tag on both a Contact and a Matter) are preserved on each record independently.

Lawmatics users (attorneys, paralegals, intake staff) are resolved by email match against Pipedrive users. We extract the user list from Lawmatics, match by email address, and flag any Lawmatics owner without a Pipedrive user account. Your team creates Pipedrive accounts for unmatched owners before migration, or we assign their records to a designated fallback owner.

Lawmatics automations (form-to-matter flows, status-change triggers, document-merge sequences) do not migrate. Pipedrive's automation engine uses different trigger semantics (deal stage change vs. matter status change). We export your Lawmatics automation definitions as a structured document so your Pipedrive admin can rebuild the logic in Pipedrive automations or via a third-party tool like Zapier or Make.