Bring the file in without rebuilding your workflow.
Connect the systems your team already uses. Imported documents become the file ChronoLaw compares—contradictions, corroboration, policy and legal connections, and findings you can inspect against the stored source—without a parallel filing habit.
How files enter ChronoLaw
Four ways to bring the complete file into one case. Named connectors below are currently generally available in production.
Cloud storage
Pull documents from the repositories your team already uses—Google Drive, Dropbox, and OneDrive—into a single ChronoLaw case.
- Google Drive
- Dropbox
- OneDrive
Legal case management
Connect practice-management systems so matter files move into ChronoLaw without a parallel filing habit. Clio is generally available today.
Document review
Bring reviewed productions and work product into the same record ChronoLaw analyzes. Upload exports directly, or contact us if you need a specific review-platform connection.
Inbound email
Use a case ingest address to forward emails and attachments into the file as they arrive, so correspondence joins the evidence foundation instead of living only in inboxes.
- Inbound email
Generally available integrations
Only connectors that are enabled, supported, and appropriate for customer onboarding appear here.
01
Google Drive
Import files from Google Drive into a ChronoLaw case workspace.
Dropbox
Connect Dropbox folders and bring matter or claim files into ChronoLaw.
OneDrive
Import from Microsoft OneDrive for teams on Microsoft 365.
Inbound email
Forward mail and attachments to a case-specific ingest address so correspondence joins the matter or claim record.
Integration is only the first step.
Imported documents do not stop at storage. They join the same file ChronoLaw compares so your team can ask questions across the matter, follow findings back to stored sources, and continue into Case Intelligence or Claims Intelligence.
Do not see the system your team uses?
Tell us what you need. Custom integrations are available on Enterprise when a connector your team relies on is not listed above.