Migrate your eBrief Ready data

Matters are the top-level container in eBrief Ready. Each matter has a name, parties list, and associated folder tree. We export matter metadata including all linked parties and preserve the matter name and internal reference during migration.

Documents are the core binary assets — PDFs that are OCR-processed and paginated on upload. We export document binaries, page counts, and the OCR text layer. Pro-tier annotation import from Adobe or PDF Expert is preserved when the destination supports annotation metadata.

Folders nest within matters and organize documents. eBrief Ready sorts and orders folders by date or manually by user. We reconstruct the full folder hierarchy and preserve the user-defined sort order at migration time.

Annotations include highlights, comments, tags, and dates applied to documents. Reports can be compiled into spreadsheets. Where the destination lacks an annotation layer, we map annotations to document metadata fields or tag them as searchable text.

Multi-party matters support multiple parties for mediations and complex litigation. Party names are stored against the matter. We map party records to the destination's contact or party object, noting that party roles and relationship types may need manual review post-migration.

eBrief Ready creates and maintains a court book index that updates automatically. This index is a derived artifact tied to document order. We export the index as a structured document that can be imported alongside the bundle, but the automatic update behavior will not carry over.

Each matter has permission levels: owner or full user. Group Actions require owner or full user permission. We map these to the destination's role or access-control model, noting that permission granularity may differ across platforms.

The Chronology Tool generates event timelines from uploaded documents. We export chronology data as a structured dataset, though the interactive timeline generation feature will need to be rebuilt in the destination if it has no equivalent.

Bank Statement Analysis extracts and summarizes financial transactions from uploaded statements using AI. This is an analysis artifact, not a structured data object. We do not migrate this as it is not a persistent stored record — the source document containing the statements is migrated separately.

Smart Classification suggests document names, dates, and destination folders on upload. These suggestions are not stored as persistent fields if the user does not accept them. We preserve only accepted classifications as document metadata during migration.