PCLaw to Clio: how to switch without losing your documents
PCLaw firms didn't pick poorly. You picked a serious accounting product two or three decades ago, and PCLaw's trust accounting fidelity is still respected. What changed is strategy: after the 2019 LEAP–LexisNexis joint venture, PCLaw publicly conceded it wouldn't move to a native cloud product and pointed customers toward LEAP. Clio is the most common US landing spot for firms looking elsewhere — and the document side is the part nobody warns you about.
First, the honest part
Why firms move — and what they're not.
PCLaw is not being shut down. PCLaw 2025 R2 ships in 2025. There's no death notice, and we're not going to pretend there is one. What there is, instead, is structural pressure that's been building since the May 2019 LEAP–LexisNexis joint venture: PCLaw publicly conceded it would not transition to a native cloud product and recommended LEAP for firms wanting modern cloud delivery. That's not a vendor sunsetting a product — it's a vendor telling its on-prem customer base that the cloud roadmap they hoped for isn't coming.
On top of that strategic concession, three real things have tightened the runway. The December 31, 2023 end-of-version cutoff hit v16 and earlier. Support and pricing have gradually firmed up across more recent reviews. And the structural fact that hasn't changed: PCLaw is on-prem accounting software, with hosted-desktop options sometimes marketed as "cloud," but it's not SaaS. For firms that want browser-based access, modern integrations, and a cloud-native rebuild path, that gap matters more every year.
We're writing this for the people actually doing the work: bookkeepers, office managers, and partners researching this together. PCLaw firms picked a serious accounting product, often 25 years ago, and the strategy shifted around them. This isn't an evacuation. It's a planned move. Clio is the most common US landing spot — but that doesn't make it cheaper, simpler, or a one-click replacement. Read on for what actually transfers, what doesn't, and where the document side is going to surprise you. (For the broader Clio migration framework, see our migrating to Clio pillar; for a high-level vendor comparison, Clio's own comparison page covers the marketing claims.)
Where PCLaw stores your data — and why it matters for the move
Structured records and documents live in different places. The document distinction is what most plans miss.
PCLaw's structured records — contacts, matters, time entries, trust transactions, billing history — live in a FAIRCOM CTree database. On a typical install you'll find DynData and StatData subfolders inside the PCLaw data directory; that's the database. CTree isn't SQL Server or Postgres, which is why most third-party migrators treat the extraction as a specialist task rather than a standard ODBC export.
Documents are different — and this is where most migration plans go sideways. PCLaw doesn't store documents inside CTree. Instead, your documents are either managed by Document Manager (which writes to a folder named PCLawDocs by default — often relocated to a network share by whoever administered your install) or they sit on a network file server as ordinary OS folders, with PCLaw indexing them via path links. Most older installations are a hybrid after years of attorney-by-attorney saving habits. Confirm the layout with whoever administers your PCLaw install before doing anything else; the answer changes which document path makes sense for you (more on that below).
On-prem PCLaw vs hosted-desktop "PCLaw cloud." The distinction matters. Some firms run PCLaw on a local server; others run it via RDP or Citrix on a hosted desktop, sometimes marketed as "PCLaw cloud." That hosted version is remote-desktop access to the same on-prem product — it isn't a SaaS rebuild. As Lawyerist puts it, hosted-desktop delivery doesn't make PCLaw a web-based product. The data lives in CTree files and OS folders either way, which is good news for the move: your data isn't trapped behind a SaaS API. (For where files end up after the move, see our security and architecture page — the on-prem-to-cloud anxiety is fair, and worth reading on.)
What Clio's free migration team handles
An honest scope list for a PCLaw-to-Clio handoff.
- ✓ Contacts clients, opposing counsel, vendors
- ✓ Matters extra fields migrate as custom fields
- ✓ Tasks
- ✓ Calendar events
- ✓ Unbilled time and expense entries
- ✓ Outstanding balances a single line item per matter invoice at time of export
- ✓ Trust balances as summative line items per matter and per contact
- • Documents. Migratable, but subject to scoping and additional fees based on volume — like every legal-SaaS migration.
- • Billing and accounting history. Invoices, billed time entries, A/R ledgers, and bill payments don't migrate; outstanding A/R comes over as a single line item per matter invoice.
- • Transaction-level trust ledger history. Balances import; per-deposit, per-disbursement detail does not.
- • Custom reports. PCLaw's reporting depth is well-loved, and most of it has to be rebuilt in Clio's reports plus Clio Accounting (or QBO).
Confirm the exact PCLaw scope with your Clio onboarding rep — Clio's help-center entry for PCLaw may have updated specifics by the time you read this. This is industry standard, not a Clio gotcha.
The trust ledger question (the one bookkeepers actually ask)
Two parts: what to do before cutover, and what to do after.
Part 1 — Pre-cutover: reconcile, then export
Trust balances migrate as per-matter and per-contact line items. Trust transaction history does not. That distinction is the single most important thing for your bookkeeper to internalize before cutover. Reconcile every trust account in PCLaw against bank statements before exporting anything — three-way reconciliation, IOLTA-by-IOLTA, the way you'd do it for a year-end audit. The whole point of a clean migration is balances tying out on day one in Clio. If PCLaw and the bank don't agree, that imbalance carries straight into Clio and becomes harder to chase down once the data has been transformed and imported.
Part 2 — Post-cutover: keep PCLaw archived for audit access
For bar-audit and IOLTA history access, plan to keep an archived read-only PCLaw instance running — or at minimum retain a CTree backup with appropriate query tooling — for 3 to 7 years, depending on your jurisdiction's records-retention rules. Don't cancel PCLaw the day Clio goes live. The audit risk isn't theoretical; trust audits routinely ask for transaction-level history that, post-migration, only lives in your old system.
One workflow change worth flagging early: Clio Manage plus Clio Accounting (or Clio + QBO) replaces PCLaw's native general ledger and check-printing workflow. That's a real change for the bookkeeper — the daily flow of entering disbursements, printing checks, and reconciling will look different — but it's a workflow change, not a feature loss. Bookkeepers who've made the move tend to settle in within a billing cycle or two; the first month is the hardest. It also doesn't have to be all-or-nothing on day one: some firms with deep trust-accounting needs keep PCLaw (or another dedicated accounting system) running as the active back office while they move practice management and documents to Clio first, then transition the accounting workflow once the rest has settled.
Where your PCLaw documents actually live
Three storage realities. Audit before you plan the move.
Almost every PCLaw firm we've talked to falls into one of three buckets, and the document plan is different for each:
- (a) Document Manager → PCLawDocs folder. The PCLawDocs folder is the default location, but it's often relocated to a network share named something else (\\fileserver\Legal\Documents, etc.). The folder structure inside is generally organized by matter ID. Document Manager handles versioning and check-in/check-out; metadata lives partly in CTree.
- (b) Network file server with PCLaw indexing path-linked files. Very common in older installations. Documents live in OS folders on the file server; PCLaw stores path links so attorneys can open them from inside the matter view. Very little metadata is in PCLaw — the folder structure on the server is the source of truth.
- (c) A hybrid mess. Some matters in Document Manager, some on the file server, some on a partner's local machine, after years of attorney-by-attorney saving habits.
Audit first. Walk through 10–20 representative matters with whoever administers PCLaw and find out where the documents really sit. The audit takes a couple of hours and saves weeks of recovery work later.
The key insight nobody mentions: most PCLaw documents are accessible without PCLaw running, because they're already in OS folders on a file server you already manage. That's good news. It means drag-drop into Clio's web UI, matter-by-matter, is often the cleaner bulk path — no specialist required, no per-GB fees, just file-server folders moving into Clio matters.
Three paths for the document side
Pick the one that matches your firm's size, document volume, and storage reality.
Clio's paid scoped migration
Clio's migration team can migrate documents, subject to scoping and additional fees based on volume. Exact scope varies — confirm with your onboarding rep.
BEST FOR
- • Large document libraries
- • Mid-size firms (10+ attorneys)
- • Matters where version history matters
- • You'd rather it be done by Clio's team
Ask your Clio onboarding rep for a quote.
Third-party migrator
Specialists who work with the FAIRCOM CTree database directly. Universal Migrator handles PCLaw CTree extraction technically — but their public catalog does not include a PCLaw → Clio Manage destination page, the way it does for MyCase, PracticePanther, or Smokeball. Verify Clio Manage as a destination directly before assuming. Other options: Soluno/Actionstep specialists, bookkeeper-led consultancies.
BEST FOR
- • Document Manager installs with metadata to preserve
- • Multi-source migrations (PCLaw + Time Matters)
- • Consultant-led switches
License + consultant fees scaled by volume.
DIY: drag-drop + Send to Case
If your documents live on a file server (very common for PCLaw), drag-drop the file-server folder into Clio's web UI matter-by-matter. Free, transparent, slower than a paid migrator, but it works. Clio Drive — Clio's desktop app that mounts your Clio documents as a virtual drive (Windows and Mac) — adds a native Bulk File Upload that moves large quantities of documents in the background via a "Pending Upload Queue"; Clio cautions that moving large amounts of files in bulk may cause the system to freeze, so move files in smaller chunks. Pair either with Send to Case for late-arrival files from email and court e-filing portals during cutover.
BEST FOR
- • Solos and small firms (under 10 attorneys)
- • File-server-based document storage
- • Matter-by-matter migration
- • Limited budget for a paid migrator
A realistic migration timeline (with bookkeeper checkpoints)
8–12 weeks, with the bookkeeper involved from week 1.
Weeks 1–2 — Audit + reconcile
Audit document storage realities (Document Manager vs file-server vs hybrid). Bookkeeper reconciles every trust account to bank statements. This week is unglamorous and load-bearing.
Weeks 3–4 — Structured-data import
Generate CSV exports from PCLaw via in-product menus (File → Matter → Export, File → Contact Manager → Export, unbilled time/expense registers, and the Billing Journal and Trust Listing reports for outstanding and trust balances). Bookkeeper sets up QBO before the import lands so accounting can hand off cleanly. Hand the export to Clio's migration team; they import it.
Weeks 5–6 — Dual-running
Run PCLaw and Clio in parallel. 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 (timing-aware)
Coordinate with the bookkeeper around fiscal-year and quarter boundaries. Do not cut over mid-quarter close if you can avoid it. A cutover scheduled in the calm week after a quarter-end is far easier than one that collides with reporting deadlines.
Weeks 8–12 — Documents
The part outside Clio's standard migration scope (document migration carries additional fees based on volume). Whichever path you chose — Clio paid, third-party migrator, or DIY drag-drop plus Send to Case for portal capture — this is where it executes. If uploads fail, see our troubleshooting guide.
Bookkeeper checklist
- ☐ Pre-export trust reconciliation (every IOLTA, against bank statements)
- ☐ Period-end timing — avoid mid-quarter cutover
- ☐ QBO setup before structured-data import lands
- ☐ Archival PCLaw retention plan (3–7 years, jurisdiction-dependent)
- ☐ Open invoices: send and collect what you can in PCLaw before cutover
What you'll have to rebuild
Honest list of what doesn't transfer.
Custom reports. PCLaw's reporting flexibility is one of its real strengths, and it doesn't transfer. Clio's report builder plus Clio Accounting (or QBO) covers most needs, but specific per-firm reports — partner compensation breakdowns, custom WIP aging, jurisdiction-specific tax summaries — usually have to be rebuilt from scratch.
Check-printing workflow. PCLaw's native check printing is replaced by Clio + QBO (or Clio Accounting), which changes the daily flow for whoever cuts checks. Workflow change, not feature loss — but plan for the bookkeeper to spend a billing cycle adjusting.
Time Matters integrations. If your firm uses both PCLaw and Time Matters, the case-management surface migrates to Clio Manage — but Power Views, custom records, and document automation built in Time Matters do not carry over. Clio Manage replaces the surface; the rebuild is real.
Intake and document templates. PCLaw document automation templates and intake form definitions don't translate. Rebuild the handful you actually use, in Clio Grow and Clio's document automation, after cutover.
What PCLaw firms get wrong
Five concrete pitfalls.
1. Cancelling PCLaw before documenting where files actually live
If documents are path-linked from a file server, that's fine — you still have them. If they're inside Document Manager and you cancel PCLaw before extracting them, you can lose access to the management layer. Audit first, cancel last.
2. Assuming trust transaction history transfers
Balances do. Transaction-by-transaction history does not. Plan for archival PCLaw retention if you need audit-grade history.
3. Trying CTree → SQL conversion themselves
FAIRCOM CTree isn't a standard format you can ODBC into. Let Clio's migration team or a specialist handle the database extraction; it's the part most likely to chew weeks if attempted in-house.
4. Skipping the archival PCLaw read-only retention plan
Bar audits and IOLTA reviews routinely ask for transaction-level history. Without an archived PCLaw instance, that history is functionally gone post-migration.
5. Underestimating the bookkeeper's role in cutover
PCLaw is bookkeeper-heavy software, and the bookkeeper has to lead trust reconciliation, QBO setup, and the cutover-week reporting close. Treat them as project lead for the accounting workstream, not a downstream consumer.
An honest cost note
Clio Manage plus Clio Accounting (or Clio + QBO) is meaningfully more expensive than a maintained PCLaw install, especially for firms running on perpetual licenses with low annual maintenance fees. Firms make the switch because remote access, support quality, and integration runway matter more than the cost gap — not because Clio is cheaper. If saving money is the only goal, staying on PCLaw is the rational call. If the gap between on-prem and cloud-native is starting to limit hiring, integrations, or partner mobility, the math usually works out within a couple of years. Pricing fluctuates; check Clio's current plans rather than relying on what someone quoted last year. See Send to Case pricing.
How Send to Case fits
Send to Case is not a migration tool. It does not move matters, contacts, calendars, billing, or trust data.
It's a free Chrome extension that uploads files from your browser into a Clio matter. Where it actually helps in a PCLaw-to-Clio switch:
- Batch upload from your browser post-Clio-import — once Clio's free team has imported matters, Send to Case lets you upload multiple files at once from your browser to the right matter, or scan a portal page and send everything in one pass.
- Late-arrival documents during cutover — email attachments, court e-filing portal downloads, opposing counsel deliveries that show up while you're dual-running.
- Ongoing capture after switch — the day-to-day reason most people install it.
Honest scope: most PCLaw documents that live on a file server can also be drag-dropped into Clio's web UI directly, free, without an extension. Send to Case is a complement — useful for the per-matter, browser-portal, and late-arrival cases — not a replacement for the bulk file-server-to-Clio move. Learn more about the extension.
Coming from a different practice management system? See the migrating-to-Clio pillar, the MyCase guide, the PracticePanther guide, or the Smokeball guide.
Does Clio's free migration include my PCLaw documents?
+Not in the standard scope. Documents can be migrated, but subject to scoping and additional fees based on volume — that's industry-standard across legal-SaaS migrations, not a Clio-specific gotcha. The standard PCLaw migration covers contacts, matters (extra fields come over as custom fields), tasks, calendar events, unbilled time and expense entries, outstanding balances as a single line item per matter invoice, and trust balances as summative per-matter and per-contact line items. Billing and accounting history — invoices, billed time entries, A/R ledgers, bill payments — does not migrate. Exact scope varies — confirm with your Clio onboarding rep.
How does PCLaw store documents — is everything inside PCLaw?
+Mixed. PCLaw firms typically have either Document Manager pointing at a PCLawDocs folder (default name, often relocated to a network share) or path-linked files that live on a network file server with PCLaw simply indexing them. Many older installations are a hybrid after years of attorney-by-attorney saving habits. Audit the file server before any move — most documents are accessible at the OS level without PCLaw running.
Will my PCLaw trust ledger transfer transaction-by-transaction?
+No. Trust balances migrate as summative line items per matter and per contact. Transaction-level history does not. Have your bookkeeper reconcile every trust account to bank statements before export. For bar audit and IOLTA history access, keep a read-only PCLaw instance running (or a CTree backup with appropriate query tooling) for 3–7 years depending on your jurisdiction. Don't cancel PCLaw the day Clio goes live.
Is PCLaw being shut down?
+No — PCLaw 2025 R2 still ships in 2025. The pressure is structural rather than a sunset. After the May 2019 LexisNexis–LEAP joint venture, PCLaw publicly conceded it would not transition to a native cloud product and recommended LEAP for firms wanting cloud. End-of-version cutoffs (December 31, 2023 for v16 and earlier), tightening support and pricing, and the structural fact that PCLaw is not SaaS are the real pressure points.
What about Time Matters if my firm uses both?
+Same playbook. Clio Manage replaces both the practice-management surface of Time Matters and the back-office accounting surface of PCLaw. Power Views, custom records, and document automation built in Time Matters don't carry over and will need to be rebuilt. Confirm Time Matters scope with your Clio onboarding rep early — it's a separate import discussion from PCLaw.
Do I need a third-party migrator like Universal Migrator?
+Maybe. Universal Migrator handles PCLaw CTree extraction technically — their knowledge base has the procedure for extracting from FAIRCOM CTree databases. They do not, however, publish a dedicated PCLaw → Clio Manage destination page like they do for MyCase, PracticePanther, or Smokeball. Verify Clio Manage as a supported destination directly with them before assuming. Other reasonable options include Soluno/Actionstep specialists and bookkeeper-led consultancies.
Is Send to Case a PCLaw migration tool?
+No. Send to Case is a free Chrome extension that uploads files from your browser into Clio matters. It does not migrate matters, contacts, calendars, billing, trust ledger data, or any structured records out of PCLaw. It's useful as a complement during cutover and after — for late-arrival documents from email, court e-filing portals, and opposing counsel — not as a replacement for the bulk file-server-to-Clio move, which drag-drop into Clio's web UI handles for free.
If I upload the documents myself, does Clio keep PCLaw's version history and original dates?
+A manual upload brings the current copy of each file into Clio — not PCLaw's history. Clio has its own document version history, but it begins once a document lives in Clio; the prior versions held in PCLaw's Document Manager, and its document-management metadata, don't reconstruct themselves on a drag-and-drop upload, and Clio's document date reflects when you add the file rather than its original PCLaw date. If retaining that history or metadata matters, that's the case for a paid migrator that maps it across — or keep your PCLaw archive read-only for reference. The DIY upload is the right call when the current version of each file is what you need going forward.
Keep going
Document management & retention in Clio
After the move — folders, naming, versions, and retention in Clio.
Read guide →Clio file management & storage
Documents area, Clio Drive, and storage limits for migrated files.
Read guide →Document retention & records
Retention scheduling for the historical matters you migrate.
Read guide →Talk to Clio's onboarding team first
Book the free migration consultation, scope your PCLaw export, and confirm what's in vs. out of scope before doing anything else. Then come back for the document side.