CUTOVR

Onboarding

A quiet, careful path off PCLaw.

A plain-English walkthrough for law-firm staff. How to move PCLaw transaction history into QuickBooks Online, what to check at each step, and how to roll it back if something looks wrong.

Before your first real run

  • Don’t upload a full client ledger on your first run. Export a small slice of the transaction history (one or two transactions) and confirm it lands correctly in QuickBooks first.
  • Review the Map accounts screen before sending. A wrong match sends records to the wrong QuickBooks account and has to be reversed.
  • Production sends to the real QuickBooks company. We’ll ask you to type IMPORT to confirm — double-check the company name on screen.
  • Reversal is one-click but not invisible. QuickBooks shows reversed entries as new REV-… records alongside the originals.

Getting your reports out of PCLaw

You don't need to learn any new PCLaw screens to use this tool. Below is what each report is, why we want it, and roughly where to find it inside PCLaw. If your PCLaw build labels a menu differently, the export should still be available from your PCLaw reporting / export area — the report name is the key.

  1. Account List (Chart of Accounts). The list of accounts your firm uses. We match these against your QuickBooks accounts.
    Run from your PCLaw reporting/export area — look for “Chart of Accounts” or “Account List”. Export as CSV.
  2. Transaction History (General Ledger). The actual entries to move. Run for the period you want to bring over.
    Run from your PCLaw reporting/export area — look for “General Ledger” or “Transaction History”. Export as CSV.
  3. Starting Balances (Trial Balance). The balance of every account as of your switchover date. Used to seed opening balances in QuickBooks and to check the books afterward.
    Run from your PCLaw reporting/export area — look for “Trial Balance” as of your switchover date.
  4. Final Balance Check (Trial Balance, end of period). A second Trial Balance run for the end of the period you moved. Used at the very end to confirm every dollar landed cleanly.
    Same export as above, just dated at the end of your migration window.
  5. Client Trust Balances (Trust Listing). Per-matter trust balances. Reconciled against your trust liability and trust-bank totals. Never auto-posted — see the IOLTA section below.
    Run from your PCLaw reporting/export area — look for “Trust Listing” or “Client Trust Balances”.
  6. Customer / Vendor lists (if your PCLaw build supports a direct export). Helps QuickBooks attach Accounts Receivable lines to the right client and Accounts Payable lines to the right vendor. If you can't export these, we create the customers and vendors during import based on the transaction history.

Don't worry about getting the column order “right” — we look at the header row, not the position. As long as the file is a CSV with sensible column headings, the app will figure the rest out.

What you can upload

Four PCLaw report exports. Only your transaction history (General Ledger) posts to QuickBooks; the others are previewed and reconciled.

ReportWhat happensSample
Transaction history

(General Ledger)

 Sent to QuickBooks Each transaction posts as one journal entry, after you confirm. Sample CSV
Account list

(Chart of Accounts)

 Preview only We compare against QuickBooks and show what matches and what would be created. Sample CSV
Starting / final balances

(Trial Balance)

 Validation only Parsed and totaled. Used to seed opening balances and reconcile after import. Never auto-posted. Sample CSV
Client trust balances

(Trust Listing)

 Validation only Reconciled against QuickBooks trust liability / trust bank totals. Never auto-posted. Sample CSV

The full workflow

  1. Export from PCLaw. Run the General Ledger report for the period you want and save as CSV.
  2. Upload. From the dashboard, enter the firm name and pick the CSV. The file is encrypted before processing.
  3. Review the preflight. The job page shows transaction count, debit / credit totals, whether the file balances, and which accounts were detected.
  4. Map accounts. Open the matching screen and pair each PCLaw account with a QuickBooks account. The import is blocked until every account is matched.
  5. Connect QuickBooks. Sign in with Intuit and pick the company that should receive these records.
  6. Confirm. In production, type IMPORT on the confirmation card to enable the post.
  7. Send. Each PCLaw transaction posts as one QuickBooks journal entry. Duplicate protection runs first.
  8. Verify. Re-fetch every entry from QuickBooks and compare against the CSV.
  9. Reverse if needed. Type REVERSE to post offsetting entries.

Sample files

Want to try the flow before exporting from PCLaw? Download a sample CSV that already has the columns we expect.

Download sample CSV template Larger sample CSV
Technical details for support — required CSV columns

You usually don't need to look at this — the app reads sensible column names automatically. Open this only if support asks you about the underlying format. Optional extras — description, reference, client_id, matter_id, customer_name, vendor_name — are kept.

ColumnMeaningExample
transaction_idUnique id for the entry. Multiple rows with the same id form one balanced journal entry.JE-0001
datePosting date, ISO format.2026-05-01
account_numberPCLaw account number. Matched first.1000
account_namePCLaw account name. Fallback if number doesn’t match.Operating Bank
debitDebit amount, or 0.1000.00
creditCredit amount, or 0.0.00
memo (optional)Free-text description copied into the QuickBooks line.Opening operating cash

About trust / IOLTA accounts

Trust accounts are the most sensitive part of a law-firm migration. Here is exactly how Cutovr treats them.

  • Trust balances are checked and reconciled, not blindly auto-posted. We compare your PCLaw client trust listing against the trust liability and trust-bank totals before anything is sent to QuickBooks.
  • Per-client trust balances do not auto-post to QuickBooks trust accounts. The trust listing is treated as a reconciliation input. If your firm needs per-client trust balances mirrored into QuickBooks, that's a separate manual step under your accountant's supervision.
  • If trust balances don't reconcile, the migration is flagged. You'll see an explicit “Needs attention” on the review step before you can send anything.
  • You decide what to do with mismatches. We surface the variance with the underlying numbers so you (or your bookkeeper / accountant) can make the call — we never silently “fix” a trust discrepancy.

Bar rules vary by jurisdiction. Cutovr is a migration tool, not legal or accounting advice. If you're unsure about the trust posture for your migration, please involve your firm's accountant or a trust-account specialist.

What we check before posting
  • Every required column is present.
  • Each transaction balances (debits == credits).
  • Every row has a date and an account number or name.
  • Every PCLaw account is matched to a QuickBooks account.
  • QuickBooks is connected and the realm id is known.
  • The same file hasn’t already been imported into this QuickBooks company.
  • None of the transaction ids already exist in this QuickBooks company.
  • You typed IMPORT on the confirmation card.

Need help?

Read the support page for common issues, or email support@cutovr.com. Include the job id and the exact flash message — please don’t paste raw ledger content or OAuth tokens.

Create your firm workspace → Sign in