Data migration route
SimpleLaw to NetDocuments migration
SimpleLaw is a cloud 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.
SimpleLawCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: 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
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 1 to confirm
- 7 archived
What moves
What moves from SimpleLaw to NetDocuments
Each row is a kind of record SimpleLaw holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, seven kinds have no place in NetDocuments and are archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldThe vendor uses matter and case interchangeably. | 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 | HeldLeads, clients and other contacts in one CRM. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldStored on SimpleLaw’s servers or in the firm’s Dropbox, Google Drive or OneDrive. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails sent from within SimpleLaw through Google or Outlook are tracked by matter. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldClients can also add notes through the portal. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | HeldAppointments by firm member or type, synced with Google or Outlook. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldWorkflows create tasks, appointments and documents for standard case types. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldOne timer per matter, plus manual entries. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee, instalment, contingency, pro bono and LEDES invoices. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust billing and initial trust payments are supported; ledger detail was not confirmed. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields feed intake forms, reports and document automation. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable templates filled from stored data and intake answers. | 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 | HeldWebsite forms, custom intake forms and lead tracking in the CRM. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against SimpleLaw.
- 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 SimpleLaw 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 SimpleLaw 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 SimpleLaw for matters and billing, or into an archive.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SimpleLaw depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to SimpleLaw is kept running until the checks on NetDocuments are finished.
Where the data is now
Leaving SimpleLaw
SimpleLaw lets a firm rename and rearrange a good deal, so the first step in leaving it is learning this firm’s version: what it calls its record types, where it chose to store files and which clients were given portal access. With that understood the move itself is usually modest in size, since the product is sold to solo lawyers and small firms.
Files in your drive or theirs
A firm chooses whether documents sit on SimpleLaw’s servers or in its own Dropbox, Google Drive or OneDrive. In the second case the files already belong to the firm and need no extraction. What has to be preserved is the record of which folder belongs to which matter.
The firm’s own labels
Documents, activities, expenses and contact IDs can all be renamed to suit the firm. Staff describe their records in those terms, and screens and reports follow them. A short glossary is written first, so that something the firm calls a Disbursement or a File Ref is mapped to the right field in the destination.
What clients added
Through the portal, clients upload documents, add notes, complete intake forms and message the legal team. Client-written notes sit among the firm’s own. They are marked with their author on the way out, so that in the new system nobody mistakes a client’s comment for a lawyer’s file note.
Referred and co-counsel matters
Matters referred or shared with co-counsel through the SimpleLaw network are visible to both firms inside the platform. That shared view does not exist elsewhere. The other lawyer is recorded as a contact with a role on the matter, and the firm tells co-counsel how documents will be exchanged afterwards.
Payments recorded in two ways
Clients may pay through an integrated processor, or the firm may manage payments offline or through QuickBooks. Where the second route was used, the payment record inside SimpleLaw may be incomplete. Receivables are checked against the bank statement or QuickBooks before any balance is carried forward to the new system.
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 SimpleLaw 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 SimpleLaw: 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 SimpleLaw, a final pass over a weekend picks up what changed since the trial. SimpleLaw 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 SimpleLaw 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 SimpleLaw 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
SimpleLaw to NetDocuments: what firms ask
Does SimpleLaw replace our accounting software?
No. It records time, raises invoices and takes payments, and it can sync with QuickBooks. The general ledger, payroll and tax reporting stay in the accounting package. A firm moving to it from an all-in-one system should plan where its books will be kept before the practice data is moved.
Our documents are in Google Drive. Do they have to be uploaded?
Not necessarily. SimpleLaw offers Google Drive, Dropbox and OneDrive as storage options alongside its own servers. If the firm keeps Google Drive, the work is arranging folders so each matter finds its files. How the connection handles an existing folder tree is confirmed in the analysis.
We are leaving SimpleLaw. Can clients still reach their documents?
Only for as long as the SimpleLaw account and its portal remain active. Documents clients uploaded are extracted with the matter. If the new system has a client portal, access is set up again there, and clients are told in advance where to find their files from the cutover date.
Do trust balances in SimpleLaw have a place in NetDocuments?
No. NetDocuments does not keep trust ledgers. Trust records from SimpleLaw 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, notes, calendar entries, time entries, billing records, trust ledgers and intake records. They are exported from SimpleLaw 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 SimpleLaw data is loaded into NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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 SimpleLaw and into NetDocuments
Other destinations from SimpleLaw
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.
SimpleLaw and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from SimpleLaw 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.