Migrate from Clio to Pipedrive

Clio contacts map directly to Pipedrive People. The contact's display name becomes the Person's name field. Email, phone, and address fields map 1:1. For clients with multiple matters, all associated matters attach to the same Person record via deal links.

Each Clio matter becomes a Pipedrive Deal. The matter number maps to deal title, and the primary client contact links to the deal's Person. Matter status (Active, Pending, Closed) maps to Pipedrive pipeline stage values. We configure the pipeline stages to mirror your Clio matter lifecycle before migration.

Clio billing fields — flat rate, hourly rate, billing arrangement type — have no Pipedrive native equivalent. We migrate these as custom fields on the Deal object (e.g., Billing_Type__c, Rate__c). Your team rebuilds invoice generation in your accounting tool post-migration.

Clio time entries become Pipedrive Activities with Type='Note'. The note body contains hours worked, date, and description. We preserve the original entry timestamp and link the activity to the Person (client) and corresponding Deal (matter). Billable flag migrates as a custom checkbox field on the activity.

Documents attached to Clio matters are downloaded and re‑uploaded to the corresponding Pipedrive Deal as file attachments. We preserve the original file name, creation timestamp, and any existing version metadata during the upload. Pipedrive's 500 MB per‑file limit applies, and files larger than this are flagged for manual handling. Inline text from PDFs is not extracted; the original file is stored as‑is so your team can open it directly in Pipedrive.

Clio matter tasks become Pipedrive Activities with Type='Task'. The due date, priority, and assignee are carried forward, and we map Clio priority levels (low, medium, high) to Pipedrive's priority enum (0, 1, 2). Open tasks are created as Pipedrive tasks; completed tasks are saved as done activities with a timestamp. Each task is linked to corresponding Deal and, if relevant, to the Person record, giving your team context in Pipedrive.

Clio custom fields on matters (practice area, court venue, opposing counsel, statute of limitations) are created as Pipedrive deal custom fields. Field types are matched: Clio dropdown becomes Pipedrive enum, Clio date becomes Pipedrive date. We flag any field types Pipedrive doesn't support (e.g., Clio's trust balance field).

Clio users are resolved to Pipedrive users by matching email addresses. Unmatched users are flagged before migration, allowing your team to create the Pipedrive account, invite the user, or reassign records to a fallback owner. The Clio user ID is saved in a custom field on each Pipedrive user. Billing‑responsible attorney fields map to the deal owner, so the attorney assigned in Clio becomes the owner of the Pipedrive deal.

Clio invoices, trust accounting records, and expense entries have no Pipedrive counterpart. We export these as a CSV file for import into QuickBooks, LawPay, or another accounting tool. The invoice number and amount are preserved as a reference note on the Deal.

Clio invoices, trust accounting records, and expense entries have no Pipedrive counterpart. We export these records as a CSV that includes the invoice number, date, client name, matter reference, amount, status, and data. The CSV can be imported into QuickBooks, LawPay, or an accounting tool. Additionally, the invoice number and amount are stored as a reference note on the Pipedrive Deal, letting your team view billing details without leaving Pipedrive.