AbacusLaw to Clio: a practical migration playbook
Clio's migration path covers your AbacusLaw contacts, matters, notes, tasks, calendars, and emails. Your documents — files sitting on your firm's server — take a separate route. Here's the whole playbook, for both AbacusLaw and Abacus Sky.
An AbacusLaw-to-Clio switch is really two migrations
Structured data follows Clio's published Abacus path. Documents live on your server and take a different route.
AbacusLaw has been running law offices since the era of on-premise everything, and plenty of firms still run their practice on it. The reasons firms move to Clio are usually structural — a desktop-and-server install that's aging, key staff who knew the system retiring, or wanting the cloud ecosystem — not a sudden failure of the software.
The first migration is the structured one. Clio publishes a dedicated Abacus export guide, and its migration path covers contacts, matters, contact notes, matter notes, related contacts, tasks, calendar events, and email communications. You run the export (steps below), hand it over, and Clio's team converts and imports it.
The second migration is documents. Clio's Abacus migration article doesn't mention documents at all — because in AbacusLaw, documents aren't database records. They're files on your firm's server, linked from the matter records. They come out by locating them on the server, and they go into Clio by uploading them. That gap is most of this page.
For the system-agnostic playbook, see our general guide to migrating to Clio. The rest of this page is the Abacus-specific part.
AbacusLaw vs. Abacus Sky
Clio's migration article lists the two variants separately — know which one you're on before the consultation.
Clio's migration article for A–B software has two Abacus entries: Abacus (the desktop AbacusLaw install) and Abacus Sky (the hosted edition). The migratable-data lists are nearly identical — contacts, matters, contact notes, related contacts, tasks, calendar events, and email communications appear on both — with one visible difference: matter notes appear on the Abacus list but not the Abacus Sky list. If matter notes are load-bearing for your firm, confirm their scope with your Clio migration specialist before cutover.
The published export mechanics are the same for both variants, including the all-users-logged-out prerequisite and the PostgreSQL caveat covered below.
One naming note while you're searching for vendor documentation: AbacusLaw was AbacusNext's flagship product, and abacusnext.com now redirects to CARET (getcaret.com). CARET Legal is a different product — make sure a help page is actually about AbacusLaw before following its steps.
What a standard Clio migration covers
An honest scope list for an Abacus handoff, straight from Clio's published documentation.
- ✓ Contacts
- ✓ Matters
- ✓ Contact notes
- ✓ Matter notes (Abacus list; not shown on the Sky list)
- ✓ Related contacts
- ✓ Tasks
- ✓ Calendar events
- ✓ Email communications
Documents. Excluded from the standard, self-serve path. Per Clio's data migration overview, documents can be migrated subject to scoping and additional fees based on volume — raise them in your consultation.
Not migrated at all: accounting and financial history (trust account transactions, invoices, billed time entries, A/R ledgers, bill payments, historical bills), billable rates, reports, user permissions, and settings. Trust and A/R balances, when in scope, arrive as a single summative line item per matter or contact.
We'll cover three realistic ways to handle the document side below.
How the Abacus export actually works
Clio's published steps, including the PostgreSQL trap that quietly produces stale data.
Before anything else: ensure all users are logged out of AbacusLaw, Abacus Accounting, MessageSlips, and Microsoft Outlook. To force everyone out, go to File > Setup > Scheduled Shutdown and click Shutdown Now under the Immediate shutdown section.
Option 1 — back up your data. Log in to Abacus, go to File > Utilities > Backup > Backup, confirm the destination, and click Backup. You get a LAW_XXX.zip backup file in the selected directory. The PostgreSQL caveat: if your firm runs a PostgreSQL server for Abacus, standard backup methods will not produce a complete export — the DATA01 folder will not contain up-to-date data. Check Help > About Abacus to identify your server type before trusting this option.
Option 2 — export reports. Go to File > Reports and select Names, Calendar, Matters, Matter Notes, or Name Notes. Create a new report (e.g., "Clio Contact Export"), click Add, then Run, then Comma Delimited, and save the file. The article also points to law9.adt or law9.dbf in the Abacus folder on your computer. Note these report exports cover contacts, matters, and notes — for calendar events or tasks, Clio's article defers to the Abacus help center.
Option 3 — PostgreSQL servers. Use the export feature in Abacus Accounting, or in AbacusLaw select File > Export and follow the instructions. You can also contact Abacus directly to request an export — for a fee.
What none of these produce: your documents. The export covers the database side; the files stay where they've always been, on your server.
Clio's migration article has the current published steps for both Abacus variants.
Three realistic paths for your historical documents
Pick the one that matches your document volume and how much of the work you want to do yourself.
Clio-scoped document migration
Per Clio's data migration overview, documents can be migrated subject to scoping and additional fees based on volume. Raise it in your migration consultation and let Clio's team quote it for your library.
BEST FOR
- • Firms that want one vendor handling everything
- • Libraries too large to move by hand
- • Keeping the document move inside the official process
Fees scale with volume; scoped per firm, not published.
Third-party paid migrator
Commercial legal-data migrators move document libraries into Clio as a service — typically four-figure engagements priced by volume, with the vendor handling extraction and matter mapping.
BEST FOR
- • Very large or messy server shares
- • Firms without in-house IT help
- • When folder-to-matter mapping is complicated
Priced by volume; get the matter-mapping approach in writing.
Locate files + bulk-upload tool
Find your Abacus data/documents directory on the server (your IT admin or Abacus consultant knows where), then bulk-upload each matter's folder to the matching Clio matter with a tool like Send to Case.
BEST FOR
- • Small to mid-size firms
- • Migrating matter-by-matter
- • Avoiding per-GB fees and scoping calls
No fees, no scoping — but you do the work.
A native desktop option worth knowing: Clio's own desktop app, Clio Drive, has a Bulk File Upload feature that moves large quantities of documents — or large individual files — in the background through a "Pending Upload Queue," on both Windows and Mac. One caveat straight from Clio's guidance: moving large amounts of files in bulk may cause the system to freeze, so move files in smaller chunks. Confirm the current details in Clio's help center before you rely on it for the whole library.
Pre-cutover checklist + six-step playbook
A scannable plan, in order, with the document path baked in.
Pre-cutover checklist
- ☐ Identify your edition and server type. AbacusLaw or Abacus Sky, and Help > About Abacus to check for PostgreSQL — it changes which export option works.
- ☐ Book Clio's migration consultation. Confirms what's in vs. out of scope for your firm, and is where you raise documents and balances explicitly.
- ☐ Decide your document path (Clio-scoped, paid migrator, or locate + bulk-upload) before kickoff — and find your Abacus documents directory while your server admin is available.
- ☐ Preserve your accounting records. Accounting and financial history doesn't migrate. Keep Abacus Accounting accessible or archive the reports you need before decommissioning anything.
- ☐ Plan the post-export freeze. Once you export, stop using Abacus — anything entered afterward won't be captured and must be transferred by hand. Tell staff the date.
The six-step playbook
Identify your Abacus edition and server type
AbacusLaw or Abacus Sky; standard or PostgreSQL server (Help > About Abacus). Five minutes now saves a stale-data export later.
Book Clio's migration consultation
Clio's migration can run self-serve or with the migrations team's hands-on help. The consultation scopes your structured-data import and quotes a document migration if you want Clio to handle that too.
Log all users out of Abacus
All users out of AbacusLaw, Abacus Accounting, MessageSlips, and Outlook. Force stragglers out via File > Setup > Scheduled Shutdown > Shutdown Now.
Run the backup or export
File > Utilities > Backup > Backup for the LAW_XXX.zip, or File > Reports exported as Comma Delimited. PostgreSQL firms: use the Abacus Accounting export or File > Export instead.
Clio processes and imports — review before touching anything
Clio converts the export and imports it. Review for accuracy and report corrections immediately; don't modify imported data until it's confirmed, or the import may not be revertible.
Locate document files and upload them to Clio matters
Copy each matter's folder from your Abacus documents directory and upload it to the matching Clio matter using your chosen path. If uploads fail, the Clio upload troubleshooting guide covers the common causes.
Gotchas and common pitfalls
The things that bite firms a week after cutover.
Variant confusion. Clio documents Abacus and Abacus Sky separately, and the lists differ on matter notes. Confirm which variant you're on — and which list applies — before assuming any data type is covered.
Accounting history is not in the standard scope. Trust account transactions, invoices, billed time, A/R ledgers, bill payments, and historical bills don't migrate, full stop. Your Abacus Accounting records need an archival plan of their own; don't decommission the server the day Clio goes live.
Balances arrive summative, not transactional. When trust or A/R balances are in scope, they come over as a single line item per matter or contact — the balance at export time. Reconcile against the bank before exporting, because an imbalance carries into Clio with no transaction history behind it to debug.
The PostgreSQL backup trap. On a PostgreSQL server, the standard File > Utilities backup looks like it worked but the DATA01 folder won't contain up-to-date data. Check Help > About Abacus first and use the PostgreSQL export options instead.
The post-export freeze is real. Clio's overview is blunt: once you export, stop using the old system immediately. Anything entered into Abacus afterward isn't captured and must be moved by hand.
Common pitfalls
- Running the standard backup on a PostgreSQL server and shipping stale data to Clio.
- Editing imported records in Clio before confirming accuracy — modifications can prevent the import from being reverted.
- Decommissioning the Abacus server before the document folders are located and uploaded — the export doesn't contain your files.
An honest cost note
Clio's own framing: "Clio offers a complimentary data migration service for many common systems. However, the cost can vary for more complex migrations or systems not directly supported." Abacus has a published export path in Clio's migration guides, so the structured side is well-trodden — but documents are scoped separately with fees based on volume, third-party migrators run four-figure engagements priced by volume, and a PostgreSQL export from Abacus itself may carry its own fee. The do-it-yourself document path costs time instead of money; pick deliberately rather than discovering the line items mid-migration.
How Send to Case fits
Send to Case is a free Chrome extension that uploads files from your browser into a Clio matter. It is not a migration service — it doesn't move matters, contacts, calendars, or notes, and it can't run your Abacus export. Its role starts after you've located the document folders on your server: you point Send to Case at a matter's folder and bulk-upload it to the right Clio matter in one pass, or capture files straight from the browser without downloading them first.
That's the only part it plays in an AbacusLaw-to-Clio switch: closing the document side after Clio handles the structured data. Learn more about the extension or see how bulk upload works.
Coming from a different practice management system? See the Clio migration guide, the Amicus Attorney, or Needles guides.
I'm on AbacusLaw — does the Abacus or the Abacus Sky migration list apply to me?
+Clio's migration article lists the two variants separately. The Abacus (desktop AbacusLaw) list covers contacts, matters, contact notes, matter notes, related contacts, tasks, calendar events, and email communications. The Abacus Sky list — Sky is the hosted edition — is nearly identical but shows contact notes without matter notes. The published export steps are the same for both. If you're unsure which variant your firm runs, confirm with whoever administers your Abacus server, and confirm the exact scope with your Clio migration specialist.
Does my Abacus Accounting and billing history migrate to Clio?
+It doesn't. Clio's data migration overview rules out accounting and financial history — that includes trust account transactions, invoices, billed time entries, accounts receivable ledgers, bill payments, and historical bills. Billable rates, reports, user permissions, and settings don't migrate either. Plan to keep Abacus Accounting accessible (or archive the reports you need) for your historical financial records.
Where do my AbacusLaw documents actually live?
+AbacusLaw documents are files stored on your firm's server, linked from the matter records — they aren't bundled inside the structured-data export. The usual home is your Abacus data/documents directory on the server; your IT admin or Abacus consultant will know the exact path for your installation. Locate and copy those folders while you still have full access to the server.
Our AbacusLaw install is old and nobody at the firm knows it well — who runs the export?
+The published steps are menu-driven (File > Utilities > Backup, or File > Reports exported as Comma Delimited), so a comfortable admin user can usually run them. Two caveats: all users must be logged out of AbacusLaw, Abacus Accounting, MessageSlips, and Outlook first, and if your firm runs a PostgreSQL server the standard backup will not produce complete data. If nobody in-house is confident, an Abacus consultant can run it — and per Clio's article, you can also contact Abacus directly to request an export for a fee.
How do trust and A/R balances come over?
+When balances are in scope, Clio's overview says they migrate as a single summative line item per matter or contact — the balance at the time of export, not transaction-by-transaction history. Note that Clio's Abacus-specific list doesn't itemize balances at all, so raise them explicitly with your migration specialist, and reconcile your trust ledger against the bank before exporting so the numbers you carry forward are right.
Does Clio's migration include my documents?
+Documents are excluded from the standard, self-serve migration path — but they're not impossible to migrate. Clio's data migration overview lists documents as migratable subject to scoping and additional fees based on volume. Raise it in your migration consultation if you want Clio to handle them; otherwise the do-it-yourself path is to locate the files on your server and bulk-upload them to the matching Clio matters.
How long does an AbacusLaw to Clio migration take?
+Clio's overview describes a four-step process — export, prepare and submit, processing, import and review — and says the time required depends on the size and complexity of your data; a migrations team member contacts you with a timeline after receiving your export. Budget separately for the document side: locating files on the server and uploading them to Clio matters is usually the longest do-it-yourself phase.
Does Clio limit how large a single file can be?
+Yes. A single file can be up to 5 GB in Clio, and that ceiling applies to both the web Documents area and the Clio Drive desktop app. A file over 5 GB must be split or kept in external storage and linked from the matter; no upload path beats the limit, and zipping rarely gets it under. It only comes up for unusually large media, such as a long recorded video.
Keep going
Migrating to Clio: the pillar guide
The system-agnostic playbook — scoping, cutover, and the document gap every migration shares.
Read guide →Documents in a Clio data migration
Why documents are scoped separately, what that costs, and every path for closing the gap.
Read guide →Amicus Attorney to Clio
The same playbook for Amicus Attorney's Premium, Cloud, and Small Firm editions.
Read guide →Tabs3 to Clio
Moving from Tabs3 and PracticeMaster — billing-heavy data with the same document question.
Read guide →Migrating from AbacusLaw?
Don't upload a server's worth of matter documents one file at a time.