Nickel City Tech Solutions logo
All Resources
Legal Technology

Migrating PCLaw to a New Server Without Losing Billing History

Moving PCLaw to a new server is one of those projects that looks simple until billing history or trust accounting balances don't match after the fact. A methodical, well-sequenced migration avoids that outcome entirely.

Published August 10, 2026 Updated August 10, 2026 10 min read By Joshua Arimoro Greater Sudbury & Ontario
The short answer

A PCLaw server migration should be planned around a defined cutover weekend, with a full verified backup taken immediately before the move, the data file transferred and tested on the new server before staff return, and a reconciliation of billing and trust balances against the old system before the old server is decommissioned.

Why PCLaw migrations need more care than a typical file server move

Unlike migrating a general file share, a PCLaw migration carries the firm's entire billing history, time records, and trust accounting balances. Any inconsistency introduced during the move has direct financial and record-keeping consequences, which is why this project deserves more planning than a routine server refresh.

Planning phase: before the migration weekend

  1. Confirm the new server meets or exceeds PCLaw's requirements for the firm's current data file size and user count.
  2. Take a full, verified backup of the existing PCLaw data file and confirm it restores successfully in a test environment.
  3. Document current user accounts, permissions, and any custom PCLaw configuration settings.
  4. Notify staff of the planned cutover window well in advance so no one works in PCLaw during the migration.
  5. Confirm licensing details with PCLaw's vendor support ahead of the new server going live.

Sequencing the cutover weekend

Migrations should happen outside business hours, typically over a weekend, to avoid any risk of data being written to the old server after the final backup is taken.

  • Take a final backup of the PCLaw data file immediately before beginning the migration
  • Move the data file to the new server and install PCLaw according to vendor guidance
  • Reconfigure workstation connections to point to the new server location
  • Confirm the network share and permissions on the new server match the firm's access control requirements
  • Test PCLaw functionality end to end, including billing entry, time entry, and trust transactions in a test capacity

Planning a PCLaw Server Move?

Get a documented migration plan built around your firm's specific data, billing cycle, and trust accounting requirements.

Request a Migration Plan

Verification before going live Monday morning

Before staff log in for the first time on the new server, verification should confirm that billing history, time records, and trust balances match what existed on the old server exactly. This step is not optional, since discrepancies found weeks later are far harder to trace back to the migration.

PCLaw migration verification checklist
CheckWhat to confirmWhy it matters
Data file integrityPCLaw opens without errors on new serverConfirms a clean, uncorrupted transfer
Billing historyRecent invoices match pre-migration recordsProtects against lost or duplicated billing
Trust balancesTrust account balances reconcile exactlyTrust accounting errors carry serious consequences
User accessAll staff can log in with correct permissionsAvoids day-one access disruptions
Backup jobsNew server is included in backup schedulePrevents an unprotected gap right after migration

Decommissioning the old server safely

Once verification is complete and the firm has operated successfully on the new server for a defined period, typically a few weeks, the old server can be retired. Keep at least one archived copy of the final data file from the old server separately, in case a historical reference is ever needed.

How this connects to broader firm infrastructure

A PCLaw migration is a good opportunity to review the firm's broader backup and disaster recovery plan, as well as coordinate timing if Primafact or other case management systems share the same server and are due for their own infrastructure review.

Frequently asked questions

How long does a typical PCLaw server migration take?

Most small to mid-size firm migrations are planned within a single weekend, though preparation and verification steps extend beyond that window.

Can staff use PCLaw during the migration?

No. Staff should be fully out of PCLaw before the final backup is taken to avoid any data being written after the migration snapshot.

What happens if billing history doesn't match after migration?

This is why verification against the old server happens before staff resume work, so any discrepancy is caught and resolved immediately rather than discovered weeks later.

Should we migrate PCLaw and Primafact at the same time?

If they share the same server, coordinating the timing can reduce overall disruption, though each system's migration should still be planned and verified independently.

About the author

Joshua Arimoro

Joshua Arimoro is the Principal Consultant at Nickel City Tech Solutions, a managed IT and cybersecurity provider based in Lively, Ontario, serving businesses across Greater Sudbury and Northern Ontario. He works hands-on with Microsoft 365, server and network infrastructure, endpoint management, and backup and recovery for small and mid-sized organisations.

More about our team

Move Your Server Without the Risk

A properly sequenced migration protects your billing history and trust accounting records from day one on the new server.

Book a Migration Consultation 705-905-3658

Technologies mentioned in this article

See what we support around each platform on our supported technologies hub.

PCLaw
Keep exploring

Related services, locations, and resources

Related services

Related service areas

Related resources