Data migration route
PCLaw to NetDocuments migration
PCLaw is a server-based practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
PCLawServer- Documents: Carried across
- Matters: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 2 mapped
- 5 to confirm
- 6 archived
What moves
What moves from PCLaw to NetDocuments
Each row is a kind of record PCLaw holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, six kinds have no place in NetDocuments and are archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach matter has a number and a nickname; closed matters get a closed matter number. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | Held | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partDocument Manager, when enabled in System Settings, holds documents and PDF bills against matters. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email items profiled to the matter. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes are loaded as documents in the matter workspace. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldAppointments, tasks and important dates. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldBillable and non-billable time and matter expenses. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldPre-bills, invoices, payments and receivables. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldClient trust ledgers across multiple trust bank accounts, with three-way reconciliation. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, vendor payments and multiple general bank accounts inside the product. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs custom profile attributes, created in the repository before the load. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMerge templates for documents and forms; invoice templates. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against PCLaw.
- Carried with mapping
- NetDocuments 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.
- Kept as a readable archive
- NetDocuments has no place for it. It is exported in a format that opens without PCLaw and handed to the firm as a read-only archive.
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
The documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from PCLaw is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces PCLaw for matters and billing, or into an archive.
PCLaw runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. NetDocuments is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving PCLaw
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what PCLaw holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into NetDocuments and checked against PCLaw: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in PCLaw, a final pass over a weekend picks up what changed since the trial. PCLaw is kept read only as the fall-back record.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what PCLaw holds
What is in it, how its records link, and where each piece would sit in NetDocuments. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
Setting up NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
PCLaw to NetDocuments: 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.
Do trust balances in PCLaw have a place in NetDocuments?
No. NetDocuments does not keep trust ledgers. Trust records from PCLaw are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records NetDocuments has no place for?
On this route that is contacts, calendar entries, time entries, billing records, trust ledgers and the firm’s accounts. They are exported from PCLaw in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before PCLaw data is loaded into NetDocuments?
Matters and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, custom fields and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from PCLaw and into NetDocuments
Other destinations from PCLaw
Other systems that move into NetDocuments
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
PCLaw and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from PCLaw to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.