Data migration route
SimpleLaw to Server drives migration
SimpleLaw is a cloud practice management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
SimpleLawCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- Matters: Kept as a readable archive
- 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
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 9 archived
What moves
What moves from SimpleLaw to Server drives
Each row is a kind of record SimpleLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and nine kinds have no place in Server drives and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldThe vendor uses matter and case interchangeably. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldLeads, clients and other contacts in one CRM. | No placeCan be kept only as an exported spreadsheet. | 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 placeFiles in folders, named and dated during the load. | 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 place in partAs .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldClients can also add notes through the portal. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| 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. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldOne timer per matter, plus manual entries. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee, instalment, contingency, pro bono and LEDES invoices. | Has a place in partInvoices as PDF files; no ledger. | 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 placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields feed intake forms, reports and document automation. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldReusable templates filled from stored data and intake answers. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | 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
- Server drives has a place for this kind of record. It is loaded there and checked against SimpleLaw.
- Carried with mapping
- Server drives holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- Server drives 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from SimpleLaw into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in SimpleLaw.
SimpleLaw is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What SimpleLaw will release depends on its export tools, and that is confirmed in the analysis.
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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives 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 Server drives. 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 Server drives 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 Server drives. 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
Structure, permissions and handover
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
SimpleLaw to Server drives: 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 Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. 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 Server drives have no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, custom fields 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 Server drives?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. 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 Server drives
Other destinations from SimpleLaw
Other systems that move into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from SimpleLaw to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.