Migrating to Clio: A practical guide for law firms
Clio's migration service — complimentary for many common systems — will move your contacts, matters, calendars, tasks, and unbilled time. Documents are a separate workstream, and most firms don't find out how to handle them until the kickoff call.
What Clio's free migration covers (and what it doesn't)
Clio's complimentary migration team is genuinely good — but their scope is structured data, not documents.
Per Clio's data migration overview, a standard migration moves:
- ✓ Contacts — clients, opposing counsel, vendors
- ✓ Matters — case shells with metadata
- ✓ Notes, related contacts, calendars, and tasks
- ✓ Emails and phone logs — (source-system dependent — MyCase, for one, can't export emails)
- ✓ Unbilled time activities — (for many systems, unbilled expenses too)
- ✓ Outstanding and trust balances — (single summative line items per matter or contact — not transaction history)
Documents are scoped and quoted by size. Clio's own help center is direct about it:
"Documents (subject to scoping and additional fees based on volume)"
— Clio Help Center, Clio Manage Data Migration Overview (June 2026)
That's how Clio's own can-migrate list qualifies documents — the one data type that's scoped and priced by volume rather than bundled with the standard migration. You have three paths to close the gap; we cover them below, and the full what-moves-what-doesn't breakdown lives in our Clio data migration and documents reference.
Why documents are a separate workstream
It's not a Clio gotcha. It's how every legal-SaaS migration works.
Structured data — contacts, matters, billing entries — is bounded. A 5-attorney firm has a few thousand contacts and a few hundred matters; the export is a manageable CSV. Documents are different. The same 5-attorney firm can have 200 GB of files, or 2 TB. Some files are small Word memos, some are 1.5 GB depositions. Folder structures are wildly inconsistent. Some files have version histories that matter; some don't.
That's why every migration partner — Clio, Universal Migrator, the in-house migration team at every legal SaaS — scopes documents by volume. The complimentary tier handles the deterministic part. The document piece gets a separate quote, a separate timeline, and often a separate vendor.
The honest read for most firms: Clio's free migration team will move every byte of structured data they can pull out of your old system. Documents are a real, separately-priced project — and there are three reasonable ways to handle them, depending on your firm's size and storage situation.
Three paths to move your documents
Pick the one that matches your firm's size, document volume, and budget.
Clio's paid scoped migration
Clio's migration team handles documents as a separately-quoted project. Pricing depends on volume, source system complexity, and version-history requirements.
BEST FOR
- • Mid-size firms (10+ attorneys)
- • Complex source DMS
- • Version history matters
- • You already trust Clio's team
Ask your Clio onboarding rep for a quote.
Third-party migrator
Universal Migrator and similar specialists move documents and metadata in bulk, with version-history preservation — four-figure engagements, with license and consultant fees scaled by volume.
BEST FOR
- • 100+ GB document libraries
- • Multi-source migrations
- • Consultant-led switches
- • Practice areas where versioning is critical
DIY with Send to Case
Free Chrome extension. Drag-and-drop folders, batch-scan webpages, and upload directly from your browser to a Clio matter. No per-GB fees, no scoping calls.
BEST FOR
- • Solos and small firms (under 10 attorneys)
- • Documents in cloud storage or browser portals
- • Matter-by-matter migration
- • Ongoing capture after cutover
Already on local or synced storage? If your files already sit on a shared drive or a synced folder, Clio Drive's desktop app adds a native, no-extra-cost option: its bulk file upload feature moves large quantities of documents — or large individual files — in the background, tracked in a "Pending Upload Queue" on both Windows and Mac. Clio does caution that moving large amounts of files in bulk may cause the system to freeze, and suggests moving files in smaller chunks — so confirm current details in Clio's help center.
A realistic migration timeline
Clio says processing time varies with your data's size and complexity. Plan for 6–12 weeks total when you factor cleanup before and document upload after.
Weeks 1–2 — Scope and clean
Inventory data across every system. Deduplicate contacts, reconcile open matters, decide what's "must move" vs. "archive only." Don't skip this — it's the difference between a clean migration and weeks of post-cutover cleanup.
Weeks 3–4 — Clio runs the structured-data migration
Hand contacts, matters, calendars, tasks, and unbilled time to Clio's onboarding team. They import it. You review for accuracy.
Weeks 5–6 — Validate, old system read-only
Per Clio's guidance, stop entering data in the old system once you export — keep it read-only for reference while you validate the import. After an assisted structured-data import, Clio gives you a three-business-day window to review the data, and cautions that if you modify the imported data during that window it may be lost should the import need to be reverted — so confirm it's accurate before you start editing. Critical rule: pick one system as the source of truth for billing during this window. Recording time in both is the #1 way migrations go sideways.
Week 7 — Cutover
Freeze new matter creation in the old system seven days before cutover Friday. Export a final billing snapshot for parallel-period reconciliation. Trust accounting cutover is its own workstream — trust balances arrive in Clio as summative line items, not transaction history, so reconcile the ledger to the bank first; most firms freeze new trust transactions for the cutover weekend. Talk to your Clio specialist for IOLTA-specific timing.
Weeks 8–12 — Historical document upload
The part Clio's free migration skips. Whichever path you chose in the previous section — Clio paid, Universal Migrator, or Send to Case — this is where it executes. Most firms underestimate this phase. Budget the time. If uploads fail, see our troubleshooting guide.
Pre-migration cleanup checklist
Run through these before you send anything to Clio's migration team.
- ☐ Deduplicate contacts. Same client entered three times = three contacts in Clio. Merge before export.
- ☐ Reconcile open matters. Close anything that's actually closed. Don't move dead matters into your new system.
- ☐ Inventory document locations. Where do your files actually live? Shared drives, Dropbox/Drive/OneDrive, opposing-counsel portals, PACER, the old practice-management system, email attachments. Make a list.
- ☐ Tag "must move" vs. "archive only." Closed matters past your retention policy can be archived to cold storage rather than uploaded into Clio.
- ☐ Reconcile your trust ledger. Make sure trust balances in your old system match bank statements before cutover. This is the single most painful post-cutover cleanup if skipped.
- ☐ Identify what won't migrate. Custom workflows, intake forms, document templates, and saved reports often have to be rebuilt in Clio. Make a list so nothing surprises you.
- ☐ Backup everything. Belt and suspenders. Always.
Switching from your current system
Vendor-specific guides for the most common migration paths.
LEAP to Clio
The document exit window, LEAP's matter-level export tooling, and the documents-first playbook.
Read guide →MyCase to Clio
What MyCase's Full Data Backup actually contains, how to pull documents, and the LawPay reconnection step.
Read guide →PracticePanther to Clio
Native vs. cloud-synced storage paths, custom-workflow rebuild expectations, and four document situations switchers hit.
Read guide →Smokeball to Clio
Auto-form workflow continuity, Word integration changes, and how Smokeball-generated documents land in Clio matters.
Read guide →PCLaw to Clio
CTree storage realities, the trust transaction-history question, and a bookkeeper-aware playbook for the LexisNexis-era move.
Read guide →Tabs3 to Clio
There is no export button — data exits through PracticeMaster, and the version compatibility catch matters.
Read guide →Time Matters to Clio
Clio's own backup instructions skip the Documents directories — here's the documents-first counter-play.
Read guide →Needles to Clio
Five migratable data types — among the narrowest standard scopes in Clio's guides — and what that means for a PI firm's files.
Read guide →Amicus Attorney to Clio
Three Amicus editions, three different export stories — including the one where exports are not guaranteed.
Read guide →AbacusLaw to Clio
Abacus and Abacus Sky export paths, and where the documents actually live on your server.
Read guide →Docketwise to Clio
Running both tools or switching outright — the sync covers contacts and matters; filing the form packets is its own step.
Read guide →Coming from Filevine, CosmoLex, Rocket Matter, or NetDocuments? We have guides for those too. And for what Clio's migration moves across every system, see the data migration and documents reference.
When to schedule the migration
Summer is the window firms most often pick — slower caseloads, vacation-friendly training schedules, and time to settle in before fall picks back up. The reasoning is sound.
But the realistic version: any 2–3 weeks of partner availability with light filing deadlines works. Summer is when most firms have that combination by default. If your firm has a different quiet stretch — between trial seasons, after a closing-heavy quarter, around a major billing cycle close — that's the right window for you.
What firms get wrong
Four pitfalls we hear from firms who've already done it.
1. Discovering documents are out of scope mid-migration
Many firms first learn on the kickoff call that documents are scoped and priced separately — and then scramble. Build the document plan before the call, not after.
2. Under-budgeting parallel-running
Two systems running for 4 weeks means either double-billed time or untracked hours. Pick one source of truth for billing and stick to it.
3. Skipping data cleanup
Garbage in, garbage out. Duplicated contacts, stale matters, and bad billing entries all migrate cleanly. Then you have to clean them up in Clio.
4. Cancelling the old system too soon
If you cancel before pulling all your historical documents, you're locked out. Keep the old system live until the document phase is fully complete.
Does Clio's free migration include documents?
+Not in the standard scope. Clio's standard migration covers contacts, matters, notes, calendars, tasks, unbilled time (and for many systems expense) activities, and outstanding and trust balances as summative line items — documents can be migrated, but per Clio's data migration overview they are subject to scoping and additional fees based on volume. Third parties like Universal Migrator handle documents directly, and many firms upload documents themselves using browser tools. Exact scope varies by source system — confirm with your Clio onboarding rep.
How long does migrating to Clio take?
+Clio's overview says processing time varies with the size and complexity of your data — there is no published benchmark. As planning guidance, firms commonly see the core data migration measured in weeks, and 6–12 weeks total once you factor data cleanup before export and historical document upload after cutover.
Can I keep using my current system during the migration?
+Carefully. Clio's guidance is to stop entering data in your old system the moment you export — anything entered after the export won't be captured. Most firms keep the old system accessible read-only for a validation window of a few weeks. The key rule: pick one system as the source of truth for billing during that period.
What's the best time of year to migrate to Clio?
+Summer is the window firms most often pick — slower caseloads, vacation-friendly training, time to settle in before fall. Realistically, any 2–3 week window with partner availability and light filing deadlines works.
Can I migrate documents to Clio myself?
+Yes — for documents accessible via browser-authenticated systems like Dropbox, OneDrive, SharePoint, or your old practice-management portal, the Send to Case Chrome extension uploads them directly to Clio matters. For very large libraries or where document version history matters, a paid migration partner is usually the cleaner path. Clio and migration partners will quantify 'very large' during their scoping conversation, based on your firm's storage situation.
Will my old system still bill correctly during the dual-running period?
+Only if you commit to one system as the source of truth for billing. The most common failure mode in a Clio migration is recording time and invoices in both systems, then trying to reconcile after the fact.
How do I verify the document migration is actually complete?
+Reconcile counts before you decommission the old system. For each matter, compare the document count in your source export against the Clio matter, and spot-check a sample by opening matters and confirming the files really are there and open correctly. Document upload is a separate workstream from the structured-data migration, and it is the one most likely to be quietly incomplete — so give it its own 'done and verified' sign-off while the source is still accessible.
Keep going
Clio document management
After you've moved in — the complete guide to organizing matter documents in Clio.
Read guide →Clio folder structure
Set up a consistent folder template before you load migrated files.
Read guide →Clio file management & storage
Documents area, Clio Drive, and storage limits for your migrated files.
Read guide →Verify your Clio migration
The pre-cutover checklist — reconcile document counts, spot-check matters, and sign off documents separately.
Read guide →Already mid-migration?
Send to Case is free for your first 10 uploads — try it on a test matter while Clio's team handles the structured data.