How to verify your Clio migration is actually complete
The most expensive migration mistake is cancelling the old system before confirming everything landed. Verification is a deliberate step, not a feeling — and the document side, which moves as a separate workstream, is the part most likely to be quietly incomplete. This is the pre-cutover checklist for proving the move is done while you can still fix it.
What "verified" actually means
A migration is verified when you have proven — not assumed — that two separate things landed: the structured data and the documents. They travel on different tracks. Structured records move through the standard migration; documents move as a scoped, often manual workstream. So "the migration is done" almost always means the structured data is done, and the documents may or may not be. Verification is the step that turns "it looks complete" into "I have confirmed it is complete."
The reason it matters is timing. Once you cancel the old system, fixing a gap gets dramatically harder — and some systems give you only a limited window to pull data after termination. So the entire checklist below runs while the old system is still fully active. The work is cheap now and expensive later; the whole point of verifying is to find the problem while the source is still sitting there to re-pull from.
The rest of this page is the checklist: reconcile document counts, open and confirm a representative sample, check the structured records, reconcile the balances, run a short parallel period, and only then sign off and cut over.
Two sign-offs, not one
Most failed verifications happen because the firm treated the migration as a single event. It is two.
Contacts, matters, notes, calendar events, tasks, and the imported balances came through the standard migration. Confirm a representative sample is present and correctly associated.
Usually the more reliable of the two, because it runs through a repeatable, scripted process.
Files landed in the right matters, in full. This is the workstream most likely to be quietly incomplete — a skipped folder, a missing matter, files truncated by name length or encoding.
Verify this one harder. Counts plus opened files, not a glance at the document list.
Run these before you cut over
Reconcile document counts per matter
For each matter, compare the number of files in your source export (or the old system's document directory) against the count now in the Clio matter. Start with the high-volume and high-stakes matters, then sample the rest. A mismatch is your signal to look closer; matching counts are strong evidence the matter came across intact.
Open and confirm a representative sample
Counts catch missing files; opening catches broken ones. Open a sample of documents across different matters and file types and confirm they actually download and render — not a zero-byte placeholder, not a truncated name. Always include your largest matters, your most active matters, and anything with a live court deadline.
Check the structured records
Open a sample of contacts and matters and confirm the key fields, related contacts, notes attached to the right matter, and calendar events on the right dates. Systemic import problems repeat, so a few dozen records across the firm will surface a pattern if one exists.
Reconcile the financial balances
Accounting history generally does not migrate — accounts-receivable and trust balances arrive as summative line items, not transaction history. Reconcile those opening balances against your old system and your bank statements before cutover, while you can still see both sides. Trust balances especially must tie out exactly.
Account for what doesn't carry
A manual document upload brings the current file, not the source system's prior version history, and Clio dates the document by when it was added. If original dates or version history matter for specific matters, note where they live (the archived export, a paid migrator's output) so nobody assumes they are in Clio.
Run a short parallel period
Keep the old system read-only and start new work in Clio. A week or two of real use surfaces gaps a static audit misses — the file someone needed that wasn't there, the matter that didn't come across. Do not record new work in both systems; pick one source of truth for billing to avoid a reconciliation mess later.
Sign off, then cancel
Only after both sign-offs pass and the parallel period is clean do you cancel the old subscription. Confirm your post-termination export window first; if the system gives a limited time to pull data after cancellation, treat it as a safety net, not part of the plan. Documents and data verified, balances tied, parallel period clean — then cut the cord.
What gets missed most
- —A whole folder type. Email attachments, a "closed matters" archive, or a scanned-correspondence folder that lived somewhere the export didn't reach. Count-reconciliation catches it; a glance at a few open matters won't.
- —Last-minute matters. Matters created in the days right before cutover, after the export snapshot was taken. Re-pull anything new since your export date.
- —Original dates and version history. A manual upload brings the current file, not the source system's history — so don't verify against an expectation that old dates and prior versions came along. Field by field, what survives the move and what resets is catalogued in the document metadata guide.
- —Balances that look right but don't tie. A summative balance can display cleanly and still be off if the source ledger wasn't reconciled first. Reconcile to the bank, not just to the old system's screen.
- —Filename casualties. Very long names, unusual characters, or deep folder nesting can truncate or drop files on some upload paths. Spot-check a few matters known to have awkward filenames.
None of these are exotic. They're the predictable places a migration leaks — which is exactly why they belong on a written checklist instead of in someone's memory on cutover day.
How do I confirm my Clio migration is complete?
+Treat it as two separate sign-offs, both done while the old system is still live. First, structured data: open a representative sample of matters and confirm contacts, matter details, notes, calendar events, and the imported balances look right. Second, documents: reconcile the file count per matter against your source export, and open a sample of files to confirm they actually downloaded and open. Only when both pass do you make the old system read-only — and only after a short parallel period do you cancel it.
Why verify documents separately from the rest of the migration?
+Because they move separately. Structured data (contacts, matters, balances) comes through the standard migration path, while documents are a scoped, often manual workstream — so 'the migration finished' usually means the structured data finished. The documents can be partially uploaded, missing a folder, or skipped for a matter without anything flagging it. A separate documents sign-off is what catches that before it becomes permanent.
What's the fastest way to reconcile document counts?
+Per matter, compare the number of files in your source export (or the source system's document directory) against the count now in the Clio matter, then investigate any gap. You don't have to check every matter exhaustively — count-reconcile the high-volume and high-stakes matters, and spot-check a random sample of the rest. A mismatch is a signal to look closer; matching counts plus a few opened files is strong evidence the matter is intact.
How many matters should I actually open and check?
+Enough to be representative, weighted toward risk. Always open your largest matters, your most active matters, and anything with court deadlines. Then sample randomly across the rest — a few dozen across a mid-size firm usually surfaces any systemic problem (a whole folder type skipped, a date-range cut off, a character-encoding issue in filenames). Systemic failures repeat; you don't need an exhaustive audit to find a repeating pattern.
What should I check besides documents?
+Confirm the structured records landed: a sample of contacts and matters with their key fields, calendar events on the right dates, notes attached to the right matters, and the imported financial balances. Remember that accounting history generally doesn't migrate — accounts-receivable and trust balances arrive as summative line items, not transaction-by-transaction — so reconcile those balances against your old system and your bank before cutover rather than expecting a full ledger.
When is it safe to cancel the old system?
+After documents and data both pass verification, after a short parallel period where new work happens in Clio and the old system stays read-only for reference, and after you've confirmed your post-termination data-export window (some systems give only a limited time to pull data after you cancel). Do the export and verification while your subscription is fully active; treat any post-cancellation window as a safety net, not the plan.
What are the most common things that get missed?
+A document folder type that didn't come across (for example, email attachments or a 'closed matters' archive), files for matters created right before cutover, original dates and version history (a manual upload brings the current file, not the source system's history), and balances that look migrated but don't tie to the bank. Build each of these into the checklist instead of trusting that a clean-looking matter list means everything transferred.
Keep going
Migrating to Clio
The full process playbook — timeline, dual-running, the pre-migration cleanup checklist, and cutover sequencing.
Read guide →What Clio's data migration moves
The reference lists: what a standard migration includes, what it never moves, and why documents are scoped separately.
Read guide →Clio document management
How matter documents are organized once the migrated files land — folders, naming, versions, and search.
Read guide →