Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

PCLaw data to Microsoft SQL Server

PCLaw is a server-based practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what PCLaw holds and keeps it readable and open to queries.

FromPCLawServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Trust money: Exported in full
  8. Firm accounts: Exported in full
  9. Documents: Exported with mapping
  10. Templates: Exported with mapping
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 8 carried
  • 2 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PCLaw to Microsoft SQL Server

Each row is a kind of record PCLaw holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route eight kinds of record carry across, two kinds need mapping and four kinds are confirmed in the analysis.

Records in PCLaw and their place in Microsoft SQL Server
RecordIn PCLawIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter has a number and a nickname; closed matters get a closed matter number.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldHas a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partDocument Manager, when enabled in System Settings, holds documents and PDF bills against matters.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldAppointments, tasks and important dates.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldBillable and non-billable time and matter expenses.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldPre-bills, invoices, payments and receivables.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldClient trust ledgers across multiple trust bank accounts, with three-way reconciliation.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, vendor payments and multiple general bank accounts inside the product.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldMerge templates for documents and forms; invoice templates.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeEnquiry rows, where the source recorded them.Confirmed in the analysis

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against PCLaw.
Exported with mapping
Microsoft SQL Server holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

Not a new system. A complete copy the firm can query.

Writing PCLaw out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in PCLaw as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in PCLaw stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

PCLaw has been on sale for more than 40 years, and a firm that has used it for a good part of that time has deep books and a long matter list. The move is led by the accounting: trust ledgers, unbilled time and expenses, receivables and the general ledger are taken at a month end and agreed to PCLaw’s own reports. Matter details, contacts and any documents follow, matched on the matter number.

  1. CTREE or SQL Server

    Help, About PCLaw, License shows which database engine the firm is on. CTREE keeps the data as files in a working folder that can be copied. The SQL Server version keeps it in MDF and LDF database files. Either engine may sit behind the same release, so the About screen is checked and the version number is not taken as the answer.

  2. Numbers, years and Enterprise

    Releases were numbered, with PCLaw 13 to 16 covered by one backup guide, and are now named by year. A firm that says it has PC Law 2014 or 2021 is naming a release, not a different product. PCLaw Enterprise is a separate edition that needs full SQL Server. Release and edition are written down at the start.

  3. Nicknames and closed numbers

    Staff find matters by nickname as often as by number, and a closed matter carries a second number from the Closed Matter Register. A destination usually has room for one matter number. The nickname and the closed number are kept as searchable references, or the index to the archive room stops making sense.

  4. The ledger is inside

    Unlike systems that hand the books to Xero or QuickBooks, PCLaw has its own general ledger, vendor payments and bank accounts. If the destination has no ledger, the books move to an accounting package and the practice system takes the matter side. That split is decided in the analysis, with the firm’s accountant involved.

  5. Document Manager is optional

    Documents are only inside PCLaw if Document Manager was enabled in System Settings. Where it was, PDF copies of bills can be saved there against the matter. Firms that never enabled it keep their documents in folders or in another program, and that becomes a further source for the same move.

More about moving off PCLaw

Where it is going

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what PCLaw holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything PCLaw holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against PCLaw: record counts, totals where PCLaw holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in PCLaw, the export is run a final time and checked again. There is nothing to go live. PCLaw is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in PCLaw and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromPCLaw
Moving toMicrosoft SQL Server

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what PCLaw holds

    What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

PCLaw to Microsoft SQL Server: what firms ask

Can we move without upgrading PCLaw first?

Usually. The data is read from the release the firm has, provided the program still opens and a backup restores cleanly. An upgrade is only suggested when the installed release cannot be read as it stands, or when the books need a repair that has to be done inside PCLaw.

We are in Canada. Does that change the move?

The product is the same, but the trust rules and tax are not. Canadian firms carry GST, HST or provincial tax on fees and disbursements, and law society trust reports must still be producible for past periods. The old PCLaw is kept read only so those reports can be run after cutover.

Does all our billing history come across?

Open invoices and unbilled work have to, because the firm still bills and collects them. Paid invoices can be loaded in summary where the destination accepts historical bills. Where Document Manager holds PDF copies of bills, those are filed to the matter as well, so a client’s question about an old account can be answered without opening PCLaw.

Does the copy in Microsoft SQL Server hold trust ledgers from PCLaw?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in PCLaw as at the export date.

Does everything in PCLaw have a place in Microsoft SQL Server?

Most of it does on paper. Emails, notes, custom fields and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before PCLaw is written out to Microsoft SQL Server?

Documents and templates are exported with mapping, so each mapping is agreed with you first. Emails, notes, custom fields and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

PCLaw and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from PCLaw to Microsoft SQL Server?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.