Migrate from Case.one to Pipedrive

Case.one matters map directly to Pipedrive deals. The matter name becomes the deal name, the responsible attorney maps to the deal owner by email match, and close date is derived from the matter's target resolution date. Practice area and matter type are preserved as custom fields since Pipedrive has no native legal-type classification.

Case.one status values like Open, Pending Review, and Closed map to Pipedrive deal status (open/won/lost). For more granular legal-status tracking, we create a Matter_Status__c custom field and preserve the original Case.one status label as a value-mapped field so the legal team's workflow context isn't lost.

Client contact records in Case.one — the individual at the client organization — map 1:1 to Pipedrive persons. Name, email, phone, job title, and address fields carry over directly. The contact's primary organization link in Case.one maps to the person-organization association in Pipedrive.

The client company or organization in Case.one maps to a Pipedrive organization record. Organization name, address, phone, website, and industry field carry over directly. The organization's billing ID or account number from Case.one is preserved as a custom field if it exists.

Documents attached to a matter in Case.one are downloaded and re-uploaded to the corresponding Pipedrive deal as a File attachment. File names, original upload timestamps, and uploader information are preserved. Very large document sets may require batching based on Pipedrive's file size limits.

Notes attached to a matter or contact in Case.one map to Pipedrive notes. The note body text, creation timestamp, and author are preserved. Notes linked to both a matter and a contact are created on the deal record with a reference to the associated person.

Court hearing dates, filing deadlines, and attorney scheduling events from Case.one map to Pipedrive activities. We use the activity type field (Meeting for hearings, Task for filing deadlines) and preserve the original event date, time, and description in the activity. Calendar events without a specific assignee are assigned to the matter's responsible attorney.

Tasks and to-do items from Case.one map to Pipedrive activity records with type=Task. Task name becomes the activity subject, due date carries over, and completion status is preserved. Open tasks migrate as open Pipedrive activities; completed tasks are logged with their completion timestamp.

Billable time entries in Case.one don't have a native Pipedrive equivalent. We create them as activity records on the deal with a time-entry note capturing hours, description, and billing rate. For firms that need detailed billing data, we also export time entries as a structured CSV alongside the migration.

Legal-specific custom fields in Case.one — Practice Area, Referral Source, Client Matter Code, Responsible Attorney, Court/Jurisdiction — require pre-creation in Pipedrive before migration. We deliver a custom-field setup plan listing each field name, type, and pick-list values so Pipedrive is schema-ready before data lands.

Multiple contacts associated with a single matter in Case.one map to multiple person associations on the Pipedrive deal. All linked contacts are attached to the deal in their original role (e.g., Client, Opposing Counsel, Witness) using the person-deal association with role labels.

Case.one's billing rate tables (attorney hourly rates, matter-specific rates, trust-account rules) have no Pipedrive equivalent. We export these as a structured reference file so the billing administrator can reconfigure in Pipedrive's billing integration or a connected accounting tool.

Case.one automations — case intake triggers, filing deadline reminders, status-change notifications — do not migrate. FlitStack exports the automation definitions as a text reference document so the Pipedrive admin can rebuild equivalent rules in Pipedrive Automations after migration.

IOLTA trust account balances and ledger entries from Case.one have no direct Pipedrive object. These are exported as a financial reference file tied to the matter record so the firm's accounting team can reconcile externally after migration.