Migrate from eBrief Ready to Salesforce Sales Cloud

eBrief Ready Matters map to Salesforce Cases with a custom Case Type pick-list value of 'Litigation Matter' to distinguish from support Cases. Your Salesforce admin pre-creates the record type before migration so the Case.Type field can be populated correctly. Matter status (active, closed, on-hold) maps to Case.Status pick-list values.

eBrief Ready parties linked to a Matter — solicitors, barristers, expert witnesses, opposing counsel — are merged into Salesforce Contacts associated with Account records. Each party role type (applicant, respondent, witness, etc.) maps to a Contact Role pick-list value on the Case. Multi-party matters result in multiple Contact records linked to the same Case.

eBrief Ready documents are downloaded from the platform and re-uploaded as Salesforce Files. Each document becomes a ContentVersion attached to a ContentDocument, which is linked to the corresponding Case record via ContentDocumentLink. Document labels (pleading, correspondence, exhibit) are stored in a custom Content_Label__c field. File size limits of 25 MB per file are enforced; oversized files are flagged before migration.

eBrief Ready folder hierarchies within a Matter have no direct Salesforce equivalent. We map folder names to a custom Matter_Folder_Path__c text field on the Case for reference. If your firm uses Salesforce Content Libraries, we can map top-level folders to ContentWorkspace libraries and sub-folders to custom fields on ContentDocument.

Structured annotation data — tags, highlight text, date markers — splits across two destinations: custom fields on the Case or ContentDocument record for structured data, and Salesforce Notes for free-form annotation text. We surface the full annotation export before migration so your admin decides which annotations to preserve structurally versus as reference notes.

eBrief Ready firm users map to Salesforce Users for platform access and Contacts for their party/representative role in matters. User email is the matching key. Users without Salesforce licenses are mapped to Contacts only. Admin versus standard-user role distinctions are preserved as a custom Role_Type__c pick-list field.

Barristers registered in eBrief Ready are mapped to Salesforce Contacts with a Barrister__c custom checkbox set to true. Their eBrief Ready matter assignments are preserved as Case Contact Roles with the role 'Barrister' selected. Barristers who are also Salesforce users are matched by email and receive both a Contact and a User record.

eBrief Ready's AI-powered chronology tool generates structured timeline events within a Matter. These are extracted as records in a custom Matter_Event__c object with fields: Event_Date__c, Event_Type__c, Description__c, and Linked_Contact__c lookup. This is one of the highest-value custom objects to create before migration so litigation timeline continuity is preserved.

eBrief Ready's bank-statement analysis output (structured financial transaction summaries) has no Salesforce standard object equivalent. We extract the summary data and store it as records in a custom Matter_Financial_Summary__c object with date, amount, category, and notes fields. Original documents are stored as Salesforce Files attached to the Case.

eBrief Ready's smart document classification assigns suggested document names, types, dates, and folder destinations at upload time. These classification values are extracted and stored as custom fields on ContentDocument: Doc_Classification__c, Suggested_Folder__c, and Classified_Date__c. This preserves the AI classification history even though the auto-classification logic itself cannot migrate.