Migrate from eBrief Ready to Pipedrive

eBrief Ready Matter maps to Pipedrive Deal. The Matter name becomes the Deal title; Matter status (Active, Closed, Pending) maps to the appropriate Pipedrive stage. Case number, jurisdiction, and court level migrate as custom fields on the Deal. Matter-linked Documents attach as Pipedrive Files on the corresponding Deal record.

Party records with type Solicitor, Barrister, or Client map directly to Pipedrive Person. Party role (solicitor, barrister, client, expert witness) migrates as a custom field (Party_Role__c) on the Person record. Primary contact flag from eBrief determines which Person record is linked as the primary contact on the corresponding Matter-Deal.

Parties of type Firm or Company map to Pipedrive Organization representing the legal practice or corporate client. Individual practitioner Parties remain as People linked to that Organization. The organization's address and contact details from eBrief populate the Organization record fields.

eBrief Ready Documents attach to their corresponding Matter-Deal as Pipedrive Files. The original document filename, upload timestamp, and uploader metadata are preserved as file metadata. Documents marked with annotations are flagged in a custom field (Has_Annotations__c) and the annotation text is extracted and stored in a linked Note on the deal.

eBrief Ready folder structure has no direct Pipedrive equivalent — Pipedrive organizes files by Deal, not by folder hierarchy. We preserve the original folder path in a custom field (Source_Folder_Path__c) on each attached file so the original document organization can be referenced post-migration.

eBrief annotations are flattened into a Note record on the corresponding Deal. Each annotation's page number, highlighted text, and author are preserved in the note body. Structured annotation metadata (tag, date, category) appears in a custom field (Annotation_Metadata__c) for reporting filtering.

eBrief Ready matter and document tags map to a custom multi-select field (Matter_Tags__c) on the Deal object. Tags applied at document level attach to the corresponding File record in Pipedrive. Teams using heavy tag taxonomies should plan for a Pipedrive admin to consolidate tags into a manageable pick-list before migration.

eBrief Ready staff user accounts (solicitors, barristers, admin staff) who are not Matter Parties map as internal Person records in Pipedrive. The eBrief role (Senior Associate, Partner, Paralegal) migrates as a custom field (Staff_Role__c) on the Person record. External clients who are Parties do not get duplicate Person records if they already exist as Party contacts.

eBrief Ready log entries recording matter milestones or communications map to Pipedrive Activities — typically Tasks with a type classification. The original activity timestamp, author, and description are preserved in the Task subject, due date, and body. Activity types are mapped via a value-mapping table so logged events map to consistent Pipedrive Activity types.

eBrief Ready court book and electronic brief assembly configurations have no equivalent in Pipedrive's CRM model. These must be manually rebuilt in eBrief Ready (if the firm continues using it for document production) or in a dedicated document assembly tool. FlitStack exports the configuration metadata as a JSON reference file for rebuild planning.