Migrate from eBrief Ready to Twenty CRM

eBrief Ready Matters are the top-level legal case records — they contain parties, documents, and folder structures. We map each Matter to a Twenty Opportunity, preserving the Matter name as the Opportunity name, original create date as a custom datetime field, and the matter status as a custom pick-list. The Opportunity is linked to the primary Company (if stored in eBrief Ready) and to all associated People records via the Opportunities_People relation table.

eBrief Ready stores party contacts per matter — barristers, solicitors, expert witnesses, clients. Each party is mapped to a Twenty People record using the person's name, email, phone, and job title. Where eBrief Ready stores a firm or organisation for the party, we create a Twenty Company record first and link the People record to it via companyId before importing People.

When party records in eBrief Ready include an associated firm or organisation name, we map that to a Twenty Company record. The Company domain, industry, and address fields are populated where available. If eBrief Ready stores multiple contacts at the same organisation across different matters, Twenty's Company record is deduplicated to a single entry with all People linked.

eBrief Ready organises documents inside Folders per Matter (e.g., Pleadings, Evidence, Correspondence). We translate each Folder into a Twenty Note on the associated Opportunity record, using the folder name as the Note title and including a reference to the folder path in the Note body. Folder hierarchy is preserved as a nested path string in the Note for auditability.

Individual documents — eBrief PDFs, court books, annotated documents — are exported as files and re-uploaded to Twenty. Each document gets a Note record on the parent Opportunity or People, with the document filename as the title and the eBrief Ready document reference ID stored as a custom field for traceability. File size limits follow Twenty's storage constraints; large bundles may be split or archived.

eBrief Ready's annotation layer (highlights, comments, tags on documents) is exported as structured data. We create a Note on the parent record containing the annotation text, tagged with the document name and page reference. If annotations are used for reporting (e.g., key evidence flags), we create a custom select field on the Note object with the annotation type values.

eBrief Ready's AI-powered chronology tool generates a timeline of events from documents. We export the chronology as a series of Note records, each with a custom date field (Chronology_Event_Date__c), a description field, and a link back to the source document. In Twenty, these Notes can be filtered by date to reproduce the chronology view manually.

eBrief Ready tracks matters through stages such as Filed, Discovery, Hearing, Judgment. We map each eBrief Ready matter stage to a Twenty custom Opportunity stage pick-list (Matter_Stage__c). Stage values are mapped value-by-value. If eBrief Ready's stage model has conditional transitions, those must be rebuilt as Twenty workflow rules post-migration.

eBrief Ready assigns matters to barristers or solicitors. Twenty resolves owners by email — all assignees must have a Twenty user account created and the invite accepted before import, per Twenty's import prerequisites. We flag any unresolvable owner references before migration and map them to a fallback Twenty workspace member.

eBrief Ready's smart classification and manual tags (e.g., privileged, exhibit, witness statement) are stored as metadata on documents. We create custom fields on the relevant Twenty object — typically a multi-select text field or pick-list on the Opportunity record — to preserve the tagging taxonomy. Tags that represent categories of documents (e.g., evidence type) can be surfaced as filterable custom fields in Twenty.

eBrief Ready allows firms to add custom fields to matters (e.g., Court, Judge, Matter Type, Case Reference). We create corresponding custom fields in Twenty Settings → Data Model on the Opportunity object before import. Field types are matched: text fields to text, dates to date, pick-lists to select. If eBrief Ready stores these as free-form text with encoded values, we document the encoding and apply value-mapping during migration.