Data migration route
PCLaw to iManage Cloud migration
PCLaw is a server-based practice management system, and iManage Cloud 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
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
iManage CloudCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: 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
- 4 to confirm
- 7 archived
What moves
What moves from PCLaw to iManage Cloud
Each row is a kind of record PCLaw holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, seven kinds have no place in iManage Cloud and are archived and four 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 workspace with client and matter metadata. Parties and status 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 placeEach needs a workspace and valid client and matter values; its class sets default security. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email documents into the workspace’s email folders. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes can be loaded as documents on the matter. | 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 | No placeiManage Tracker is a separate product with its own set-up. | Kept as a readable archive |
| 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 place in partA fixed number of custom profile fields, each a validated list. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldMerge templates for documents and forms; invoice templates. | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- iManage Cloud has a place for this kind of record. It is loaded there and checked against PCLaw.
- Carried with mapping
- iManage Cloud 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
- iManage Cloud 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. iManage Cloud 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 iManage Cloud 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. iManage Cloud 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 iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 iManage Cloud. 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 iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
PCLaw to iManage Cloud: 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 iManage Cloud?
No. iManage Cloud 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 iManage Cloud has no place for?
On this route that is contacts, calendar entries, tasks, 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 iManage Cloud?
Matters and templates are carried 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 which closed matters and how many versions of a document are in scope.
Other routes
Other routes from PCLaw and into iManage Cloud
Other destinations from PCLaw
Other systems that move into iManage Cloud
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 iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from PCLaw to iManage Cloud?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.