Migrate from Thomson Reuters Case Center to Pipedrive

Each Case Center case becomes one Pipedrive Deal. Case title maps to Deal title (name). Case status values (Active, Closed, Pending) map to Pipedrive stage names, which are created to mirror the original legal status workflow so reporting continuity is preserved.

Party records with role type 'Plaintiff' or 'Defendant' map directly to Pipedrive Person. Name fields, email addresses, phone numbers, and mailing addresses migrate as Person fields. Each person is linked to the Pipedrive Deal representing the originating case.

When a Case Center party is associated with a company or firm (e.g., corporate defendant), that entity migrates as a Pipedrive Organization record. The Person record from the party then links to the Organization via Pipedrive's person-to-organization relationship, preserving the original hierarchical relationship that existed in Case Center where parties could be tied to organizational entities.

Evidence files linked to a case are re-uploaded as Pipedrive Files attached to the corresponding Deal record. The original file name and Thomson Reuters document ID are preserved in a custom field for traceability. Pipedrive's 25MB per-file default limit applies; files larger than this are linked by URL reference instead, maintaining accessibility without exceeding storage constraints.

Case Center hearing records (hearing date, time, room, presiding officer) have no Pipedrive native equivalent. We create a Pipedrive Activity of type 'Meeting' with the hearing details in the subject and notes, linked to the Deal. Recurrence and room-booking data is captured as Activity notes rather than a dedicated scheduling object.

Text notes attached to a Case Center case migrate as Pipedrive Activity records of type 'Note' linked to the corresponding Deal. Original create date and author are preserved as Activity fields. Rich-text formatting is simplified to plain text.

Case Center's case type taxonomy (e.g., Contract Dispute, Personal Injury, Regulatory, Employment) has no Pipedrive native field. We create a Pipedrive custom picklist field on the Deal object and migrate values value-by-value, mapping each legal matter category to the closest Pipedrive stage or label your admin specifies during the planning phase.

Any custom properties stored on Case Center party records (e.g., Bar Number, Client Reference ID, Billing Rate) are created as Pipedrive Person custom fields. Pipedrive's 40-character hash-based field keys are generated at creation time; the migration plan documents each key for downstream mapping before the migration run executes.

Custom fields on the Case Center case object (e.g., Court Docket Number, Statute of Limitations Date, Jurisdiction) are created as Pipedrive Deal custom fields. Field types are matched: date fields to Pipedrive date fields, numeric fields to Pipedrive number fields, picklist fields to Pipedrive options fields.

Case Center witness records contain name, contact, and testimony notes. The witness's name and contact details migrate as a Pipedrive Person linked to the Deal. The testimony summary is stored as an Activity Note attached to that Person record, keeping the witness's identity in the CRM without creating a separate legal-witness object.

Case Center tracks exhibit version history and revision timestamps. Pipedrive has no version-history tracking for files. We capture the most recent version metadata as a custom text field on the Pipedrive File attachment and write a summary Activity Note documenting the version chain, preserving the audit trail as a reference record rather than a native object.

Case Center workflows for document routing, hearing preparation notifications, and party assignment have no Pipedrive equivalent. These must be rebuilt using Pipedrive Automations (available on Advanced tier and above). We export the Case Center workflow definitions as a structured reference document to guide your Pipedrive admin during the automation rebuild phase.