Migrate your PCLaw(r) data
Desktop legal practice management, billing, and trust accounting software with 30+ years of maturity. Firms running it are typically migrating away toward cloud-native alternatives.
In its favor
Why people choose PCLaw(r)
The signal that keeps PCLaw(r) on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Firms with decades of historical PCLaw data trust its mature trust accounting engine and don't want to rebuild IOLTA compliance from scratch in a new system.
PCLaw's all-in-one billing and law accounting design eliminates the need for separate tools like QuickBooks or MYOB, reducing vendor count for solo and small-firm practitioners.
Long-term users have built deep familiarity with PCLaw's workflow, including practice-specific billing arrangements and precedent-based form automation, making switching a significant retraining burden.
LexisNexis backs PCLaw as part of a broader legal software portfolio, giving purchasing departments a single enterprise vendor relationship instead of point solutions.
Firms in states with strict IOLTA compliance rules choose PCLaw because its trust accounting module has a long track record of passing bar audits.
The interface is widely described as confusing and subpar compared to modern cloud legal software; Capterra reviewers consistently cite poor ease of use as a primary complaint.
PCLaw runs on-premises and requires Windows desktop installation, making remote work and multi-location collaboration difficult without additional RDP or terminal server infrastructure.
LexisNexis has been actively pushing existing PCLaw customers toward LEAP, its cloud-native successor, creating uncertainty about continued product support and roadmap direction.
Rival products like LeanLaw and Clio are reported to be significantly faster; one Capterra reviewer explicitly notes LeanLaw is 'mostly much faster than PCLaw.'
PCLaw lacks client portals, which modern clients increasingly expect for viewing invoices, matter status, and documents securely online.
Reasons to switch
Why people leave PCLaw(r)
The recurring reasons buyers give for replacing PCLaw(r). Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where PCLaw(r) fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
PCLaw(r) pricing overview
PCLaw is sold as a perpetual license with an annual AMP (Annual Maintenance Program) renewal fee. Pricing is not publicly published and requires a sales contact. Firms report two-license costs around $6,000 back-fees plus renewal charges. The sibling product LEAP is positioned as the cloud upgrade path, and LexisNexis has been actively steering existing PCLaw customers toward that platform.
Professional
Tier 1 of 2
Not publicly published — annual AMP renewal fee required
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on PCLaw(r)'s schedule — see our quote-based pricing →
What gets migrated
PCLaw(r) object support
Object-by-object support for PCLaw(r) migrations. Per-pair details surface during scoping.
Matters
Fully supportedMatters are the primary organizational unit in PCLaw, containing client associations, billing preferences, and linked time entries. We map the full matter hierarchy including status, responsible attorney, and custom data fields exported via PCLaw's native Export to Spreadsheet function.
Clients
Fully supportedClient records in PCLaw hold contact details, billing arrangements, and default billing preferences. We preserve all contact fields and link each client to its associated matters during migration.
Trust Accounts
Fully supportedPCLaw's IOLTA trust accounting is its most mature module. We export all trust ledger entries — deposits, withdrawals, transfers, and running balances — and validate totals against PCLaw's printed trial balance after import to catch any truncation during CSV export.
Billing Records
Mapping requiredInvoice history and line items are exported via the native billing export, but PCLaw stores invoice formatting and arrangement preferences separately from line-item data. We extract all financial line items and map them to the destination's invoice schema; billing arrangement settings require manual reconfiguration or field mapping depending on the target platform.
Time Entries
Fully supportedTime entries link to Matters and track billable hours, expense codes, and billing status. We extract all historical time entries with their matter association, date, duration, and billing flag.
Expenses
Fully supportedMatter-level expenses are tracked separately from time entries in PCLaw. We export expense records with vendor, amount, date, matter association, and reimbursement status.
Vendors
Mapping requiredVendor records in PCLaw are used for AP and expense tracking. We map vendor names, addresses, and payment terms; some firms have duplicate vendor entries that must be deduplicated during export preprocessing.
Documents / File Links
Not in this platformPCLaw's native export does not include document binaries — it exports references and metadata only. Full document migration requires a separate file-system export from the PCLaw documents folder, which we coordinate as a parallel workstream. We do not count this as a full document migration.
Calendar / Appointments
Mapping requiredPCLaw tracks appointments and deadlines linked to Matters. Export is possible via custom report or CSV but calendar data structure varies significantly between PCLaw versions; we map what is exportable and flag any gaps for manual entry or re-creation.
Users / Staff
Mapping requiredPCLaw stores staff records including timekeeper codes, billing rates, and access roles. We extract all user records and map them to the destination's user schema, flagging any inactive or duplicate accounts that need cleanup.
Custom Fields
Mapping requiredPCLaw supports custom data fields via its Custom Reports module. These fields export with the standard export to spreadsheet but may require field-level mapping to match the destination's naming conventions and data types.
Bill分期付款/Arrangements
Mapping requiredPCLaw stores per-client and per-matter billing arrangement preferences (flat fee, hourly, contingency, etc.) in a separate Billing Preferences window. These are not exported by the standard export; we capture them via a structured questionnaire or supplemental data pull and recreate them at the destination.
| Object | Support | Notes |
|---|---|---|
| Matters | Fully supported | Matters are the primary organizational unit in PCLaw, containing client associations, billing preferences, and linked time entries. We map the full matter hierarchy including status, responsible attorney, and custom data fields exported via PCLaw's native Export to Spreadsheet function. |
| Clients | Fully supported | Client records in PCLaw hold contact details, billing arrangements, and default billing preferences. We preserve all contact fields and link each client to its associated matters during migration. |
| Trust Accounts | Fully supported | PCLaw's IOLTA trust accounting is its most mature module. We export all trust ledger entries — deposits, withdrawals, transfers, and running balances — and validate totals against PCLaw's printed trial balance after import to catch any truncation during CSV export. |
| Billing Records | Mapping required | Invoice history and line items are exported via the native billing export, but PCLaw stores invoice formatting and arrangement preferences separately from line-item data. We extract all financial line items and map them to the destination's invoice schema; billing arrangement settings require manual reconfiguration or field mapping depending on the target platform. |
| Time Entries | Fully supported | Time entries link to Matters and track billable hours, expense codes, and billing status. We extract all historical time entries with their matter association, date, duration, and billing flag. |
| Expenses | Fully supported | Matter-level expenses are tracked separately from time entries in PCLaw. We export expense records with vendor, amount, date, matter association, and reimbursement status. |
| Vendors | Mapping required | Vendor records in PCLaw are used for AP and expense tracking. We map vendor names, addresses, and payment terms; some firms have duplicate vendor entries that must be deduplicated during export preprocessing. |
| Documents / File Links | Not in this platform | PCLaw's native export does not include document binaries — it exports references and metadata only. Full document migration requires a separate file-system export from the PCLaw documents folder, which we coordinate as a parallel workstream. We do not count this as a full document migration. |
| Calendar / Appointments | Mapping required | PCLaw tracks appointments and deadlines linked to Matters. Export is possible via custom report or CSV but calendar data structure varies significantly between PCLaw versions; we map what is exportable and flag any gaps for manual entry or re-creation. |
| Users / Staff | Mapping required | PCLaw stores staff records including timekeeper codes, billing rates, and access roles. We extract all user records and map them to the destination's user schema, flagging any inactive or duplicate accounts that need cleanup. |
| Custom Fields | Mapping required | PCLaw supports custom data fields via its Custom Reports module. These fields export with the standard export to spreadsheet but may require field-level mapping to match the destination's naming conventions and data types. |
| Bill分期付款/Arrangements | Mapping required | PCLaw stores per-client and per-matter billing arrangement preferences (flat fee, hourly, contingency, etc.) in a separate Billing Preferences window. These are not exported by the standard export; we capture them via a structured questionnaire or supplemental data pull and recreate them at the destination. |
Gotchas
What to watch for in PCLaw(r) migrations
Issues we've hit on past PCLaw(r) migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API forces reliance on manual CSV exports
Trust account data integrity requires post-migration balance validation
Billing arrangement settings are not exported by the standard export
Document binaries require a parallel file-system export
| Severity | Issue |
|---|---|
| High | No public API forces reliance on manual CSV exports |
| High | Trust account data integrity requires post-migration balance validation |
| Medium | Billing arrangement settings are not exported by the standard export |
| Medium | Document binaries require a parallel file-system export |
Leaving PCLaw(r)?
Where PCLaw(r) customers move next
12 destinations PCLaw(r) can migrate to.
How a PCLaw(r) migration works
Four steps, PCLaw(r)-specific
Connect
None — no public API exists into PCLaw(r). Scopes limited to read-only on the data we move.
Map
We translate PCLaw(r)-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate PCLaw(r) quirks before production.
Migrate
Full migration with PCLaw(r) rate-limit handling. Rollback available throughout.
FAQ
PCLaw(r) migration FAQ
Answers to the questions buyers ask most during PCLaw(r) migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your PCLaw(r) migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate PCLaw(r).
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your PCLaw(r) setup and destination — written quote back within a business day.