Dropbox → Clio

Dropbox to Clio: moving firm files into matter folders

Dropbox is where a lot of small-firm document life happens: client intake files, scanned mail, shared folders with co-counsel, the archive from the firm's pre-Clio era. Clio is the system of record for the matter. The path between them has four practical forms — including Clio's own native Dropbox integration, which is genuinely useful and genuinely full of sharp edges. This guide walks through all four so you can pick the one that fits how your firm actually uses Dropbox.

By Lucas Barnes, Founder · Last updated October 4, 2026

The shape of the problem

Two file systems, one matter file

LIVES IN CLIO

Matter documents — signed engagement letters, produced records, filed pleadings. The system of record, governed by matter-level permissions and findable by anyone on the case.

LIVES IN DROPBOX

Firm-wide templates, operational docs, personal working files, the pre-Clio archive. The dangerous middle ground is a document that exists in both and quietly diverges.

For many small and mid-size firms, Dropbox predates the practice management system. It holds the firm's historical archive, the shared folders that co-counsel and clients were invited into, the scanner's output folder, and a few thousand files of working storage that accumulated over years. None of that disappears the day the firm adopts Clio.

Clio is the system of record for the matter file. When a document is part of a matter — a signed engagement letter, a produced record, a filed pleading — it belongs in the matter's document folder, governed by Clio's matter-level permissions, findable by anyone working the case. The workflow problem is the hand-off: getting a file from "somewhere in the firm's Dropbox" to "the right folder in the right Clio matter."

Dropbox is the one major cloud-storage provider where Clio offers a native two-way sync integration that most firms actually consider using, so the decision has a different shape than for other sources: the first question isn't "how do I move files," it's "should I turn on the sync, and what do I do for everything the sync doesn't fit?" The four workflows below cover both sides of that question. Firms whose cloud storage is Google Drive face a tighter version of the same decision — the Google Drive equivalent of this guide covers an integration that rules out shared drives entirely.

Option 1

Clio's native Dropbox integration

WHAT IT'S GOOD AT

Routine, ongoing flow — "save it to the matter folder in Dropbox" and "file it in Clio" become one action.
Strong for staff who live in Finder or Explorer with Dropbox desktop sync.
Bringing existing files in is a Move inside Dropbox, not a download-and-reupload round trip.

THE SHARP EDGES

The initial sync can take up to 24 hours; the root folder can't be moved or renamed.
Rename a matter folder on the Dropbox side and Clio recreates it with all contents.
Broad Dropbox access can expose matter folders that Clio-side permissions would restrict.

A Clio administrator connects the firm's Dropbox account under Settings > Documents > Document Sources. Clio creates a folder in the root of the Dropbox account containing a subfolder per client and matter (you can scope folder creation to open matters, open and pending, or all matters). Files placed in those subfolders appear in the corresponding Clio matter. Like the Google Drive integration's shared-drive gap, the Dropbox source connects a single standard firm account — it does not support shared drives or business/team accounts. The official integration docs cover setup and the current sync behavior.

What it's good at. Routine, ongoing flow. Once running, "save it to the matter folder in Dropbox" and "file it in Clio" become the same action — strong for staff who live in Finder/Explorer with Dropbox desktop sync and rarely open Clio's Documents tab. Bringing existing files in is a Move/Copy inside Dropbox rather than a download-reupload round trip, which matters at archive scale.

The sharp edges. The initial sync can take up to 24 hours. The Clio-created root folder cannot be moved or renamed. And the rename rule is the one that bites: rename a client or matter folder on the Dropbox side and Clio assumes the folder is missing, then recreates it with all contents — leaving you a duplicated mess to reconcile. The integration also syncs the matter tree into Dropbox's storage and sharing model, so anyone with broad access to the firm's Dropbox can see matter folders that Clio-side permissions would have restricted. That permissions asymmetry deserves a deliberate decision, not a default.

Where it doesn't fit. Firms whose Dropbox is shared loosely with externals, firms that need matter-level confidentiality walls, and firms that only occasionally move files between the systems. For occasional movement, the standing sync is more machinery than the job needs — one of the lighter options below is simpler and leaves no standing infrastructure to maintain.

Option 2

Dropbox desktop sync + manual upload

No integration: find the file in your synced Dropbox folder on your computer, then upload it to the Clio matter through Clio's web UI (or drag-and-drop a whole folder onto the matter's Documents tab). This is the default path for firms that don't want a standing two-way sync touching their Dropbox structure. On the Clio side, Clio Drive is the mirror-image surface — matter documents mounted as folders in Finder or Explorer — so the whole move can happen without leaving the file manager.

What it's good at. Control and predictability. You pick exactly what goes into the matter, you get a natural pause to fix the filename before it becomes a permanent matter record, and nothing about your Dropbox layout has to change. There's no rename landmine because nothing is watching your folder names.

What it costs. Time per file — a couple of minutes each including matter navigation and renaming. Fine for a handful of files a week; slow for an archive migration or a heavy intake day. For bulk moves, Option 1's move-inside-Dropbox or a bulk-upload tool gets the per-file cost down.

Option 3

Browser download

Open dropbox.com, navigate to the file, download it, upload it to Clio. The same shape as Option 2 without the desktop client — useful on machines that don't have the firm's Dropbox synced (a conference-room desktop, a borrowed laptop) and for files shared with you via a Dropbox link that isn't in your own account at all.

What it's good at. Zero setup and latest-version certainty — the browser always shows the file as it currently exists in Dropbox, with no local sync staleness in the loop. It's also the only manual option for link-shared files that live in someone else's Dropbox.

Where it doesn't shine. It's a download-then-upload round trip with a Downloads-folder copy left behind to clean up, and the per-file cost compounds at volume just like Option 2.

Option 4

Browser-based upload tools

Browser extensions that send a file from the browser directly into a Clio matter, skipping the local-disk round trip: right-click the file link in dropbox.com, pick the matter and folder, and the document lands in Clio. Examples in this category include Send to Case and similar extensions; coverage of Dropbox's various surfaces (your own account, shared links, file requests) varies by tool, so verify against the surfaces your firm actually receives files through.

What this category is good at. Mid-volume work that doesn't justify the standing sync — a stack of intake files to triage into different matters, a shared-link folder from co-counsel to file, the weekly accumulation that's too much for two-minutes-per-file and too little for integration setup. Because the tool works at the browser level, the same workflow covers Dropbox alongside Gmail attachments, court portals, and other browser-served documents.

Where it doesn't shine. It's still per-file or per-batch human-driven work — if your need is "every file in this Dropbox folder should always be in this matter," that's Option 1's job. And browser tools don't reach the Dropbox desktop client; heavy Finder/Explorer workflows pass them by.

Pick by trade-off

Which one to use when

Workflow	Strong when	Weak when
Native sync integration	Ongoing flow; staff who file from Finder/Explorer; archive moves inside Dropbox	Loosely shared Dropbox; strict matter confidentiality; folder-rename discipline can't be guaranteed
Desktop sync + upload	Occasional files; rename-before-filing control	High volume — per-file cost compounds
Browser download	Unsynced devices; files shared via Dropbox links	Anything beyond a few files at a time
Browser-based tools	Mid-volume mixed-source days; Dropbox plus portals plus Gmail attachments	Always-on folder-to-matter routing; desktop-client-only workflows

The honest cost note

What this actually costs to set up and run

Time to first file filed. Options 2 and 3 are instant — your existing Dropbox access plus Clio's web UI. Browser tools add a short install-and-authorize step. The native integration needs an administrator, a folder-scope decision, and up to 24 hours of initial sync before you should trust what you see.

Cost per file. Manual paths run roughly two minutes per file. Browser tools cut that to well under a minute. The native sync is effectively zero per file once running — its cost is structural instead: folder-naming discipline, the permissions asymmetry, and the cleanup bill if someone renames a matter folder on the Dropbox side.

What firms actually do. Firms whose document life genuinely runs through Dropbox turn on the native sync and write the two folder rules into onboarding (don't rename, don't restructure). Firms that treat Dropbox as legacy storage or an external-sharing surface skip the sync and pair manual upload for trickle volume with a browser tool or drag-and-drop bulk upload for the occasional heavy day. Mixing both is fine — the sync for the matter tree, lighter tools for everything that arrives outside it.

Dropbox to Clio FAQ

Got more? Email [email protected].

Q.01

Does Clio have a native Dropbox integration?

Yes. Under Settings > Documents > Document Sources, a Clio administrator can connect a Dropbox account. Clio then creates a folder in the root of that Dropbox account with subfolders for clients and matters, and files placed in those subfolders sync into the corresponding Clio matter. It's a real sync — but it comes with structural rules (the root folder can't be moved or renamed, and renaming a matter folder in Dropbox makes Clio treat it as missing and recreate it), so read Clio's documented limitations before turning it on.

Q.02

How long does the initial Dropbox-Clio sync take?

Clio's documentation says the initial sync can take up to 24 hours. Plan the integration setup for a quiet day, not the morning a closing binder is due. After the initial sync, subsequent changes propagate automatically.

Q.03

What happens if I rename a matter folder in Dropbox?

Clio treats the renamed folder as missing and recreates the folder and all of its contents under the original name. You end up with both folders and likely duplicated files. The safe rule: never rename the Clio-created client or matter folders on the Dropbox side. If a matter name needs to change, change it in Clio and let the integration drive the folder naming.

Q.04

Can I just move my existing Dropbox folders into the synced Clio folder?

Mostly, yes — and that's the documented way to bring existing Dropbox documents into the integration. Use Dropbox's Move or Copy on the files, place them inside the correct client and matter subfolder in the Clio-created tree, and they sync into the matter. It's manual per folder, but it's a move inside Dropbox rather than a download-and-reupload, which makes it fast for large sets.

Q.05

Should our firm's documents live in Dropbox or in Clio long-term?

The convention most firms land on: matter documents belong in Clio (it's the system of record, with matter-level permissions), while firm-wide templates, operational documents, and personal working files stay in Dropbox. The dangerous middle ground is documents that exist in both and quietly diverge. If you run the native sync, the Clio-created folder tree is the matter surface; treat everything outside it as non-matter storage.

Q.06

Who can set up the Dropbox integration in Clio?

Only a Clio administrator can connect and authenticate the Dropbox document source. If you're a paralegal or associate planning to use it, the setup step needs an admin — budget for that in the rollout rather than discovering it mid-task.

Q.07

Does uploading a Dropbox file to Clio remove it from Dropbox?

No, in every workflow on this page the Dropbox copy stays where it is. An upload creates an independent copy in Clio's document storage. That's usually what you want — but it also means version drift is your risk to manage: if someone keeps editing the Dropbox copy after the matter copy is filed, the two diverge. Decide which copy is canonical at the moment you file it.

Q.08

Does Clio limit how large a single file can be?

Yes. A single file can be up to 5 GB in Clio, and the cap is the same for the web Documents area and the Clio Drive desktop app. A file larger than 5 GB has to be split first, or stored externally and referenced from the matter; no method raises the limit. Big shared files can hit it, and zipping one rarely helps — the video and PDFs that get that big barely compress.

Related guides