Daybreak ingests original files, email families and structured message exports into a case. Every accepted item keeps its source fingerprint and byte location, duplicates point to the record already held, and anything not accepted stays visible with its reason.
Load large productions and mailboxes with transfers that resume from the server's confirmed offset.
See which attachments belong to which message, and which items are duplicates rather than missing.
Retry unfinished ingestion, cancel a run with confirmation and check inventory counts.
The receipt beside each step is an illustrative example of what a reviewer sees, not data from a real case.
Supported inputs are ordinary documents and Office files, ZIP archives, EML messages, MBOX mailboxes and message exports structured as Daybreak JSON or CSV. Message exports are selected explicitly; other vendor exports, .msg and .pst files are not accepted.
document · zip · eml · mbox · json · csvEach file is hashed in 8 MiB chunks with SHA-256 before upload, up to 5,000,000,000 bytes. The fingerprint identifies the exact original and must be reproduced to resume.
chunk hashes · root fingerprintChunks go directly to case storage. After every chunk or error the server reports how many bytes it holds, and a paused or interrupted transfer continues from that offset with the same file.
server offset · resumable sessionMessages are kept with their bodies and attachments as one family. Date and sender are shown exactly as written in the headers; they are not treated as verified identities or event dates. Thread grouping that cannot be resolved is marked ambiguous.
family · literal headers · threadEach entry is accepted, linked as a duplicate of an existing record, withheld with a reason, or still pending. Unsupported archive members are withheld, and the inventory reads incomplete until every entry is resolved.
accepted · duplicate · withheld · pendingSee how Daybreak fits your case review. Sign in to your firm's workspace or request a walkthrough.