Data migration route
Legal Files to SimpleLaw migration
Legal Files are a server-based case management system, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.
Legal FilesServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
SimpleLawCloud- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Legal Files to SimpleLaw
Each row is a kind of record Legal Files hold, whether SimpleLaw has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldAny type of case or matter, as configured by the organisation. | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldContact management with checks for duplicate entries. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocument management with text searching. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | HeldTwo-way integration with Outlook and Gmail saves emails and attachments. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldNotes, mail logs and phone logs. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCalendaring with deadline tracking. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflows, alerts and follow-ups. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | Held in partThe vendor lists eBilling among its functions. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeGeneral ledger stays in QuickBooks or another accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustomers add and change fields and screens without programming. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partLegal aid intake is among the uses the vendor describes. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Legal Files.
- Carried with mapping
- SimpleLaw 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
Cases come across. The accounts are set up new.
A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SimpleLaw brings those two sources together. The case records come from Legal Files. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.
Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SimpleLaw, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.
Legal Files run 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. SimpleLaw 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 Legal Files
Each office configured its own file types, fields and workflows, so one Legal Files system does not look like the next. The move starts with an inventory of that configuration. Then come the files, the people on them, documents and saved emails. Where the office is part of a government body or a company, retention rules and access restrictions on certain files have to survive the move as well.
Configuration is the data model
File types, screens and fields were set up by the office’s own administrator, often over many years. The field list has to be taken from that system, not assumed. Every custom field is reported with how many files use it, and the office picks the ones that deserve a place in the new system.
Not built around billing
Many of its users are in-house and government teams, which do not bill clients or hold trust money. If the destination is a law firm practice system, billing fields will be empty on every migrated matter. Where the office does record time or outside counsel spend, that is found in the analysis and mapped separately.
Mail and phone logs
Besides documents and emails, a file keeps logs of mail and of phone calls. Offices that answer to the public rely on these as the record of who was told what. They come across as dated notes on the matter with the log type kept, so they can still be filtered.
Restricted files
Investigations and other sensitive files are kept under controlled access. Those restrictions are extracted as a list of files and the users allowed to see them. The destination’s permissions are set from that list before the trial load is opened to staff, so restricted files are locked down before anyone else looks.
On your servers or hosted
The route to a copy of the data depends on where Legal Files runs. An on-premises site works through its own IT team. A hosted site works through the vendor. Government sites often need a security review before data leaves the building, and that review goes in the timetable.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Legal Files hold and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Legal Files, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against Legal Files: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Legal Files are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Legal Files as at the cutover date. Legal Files are 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 Legal Files 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 Legal Files holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Legal Files to SimpleLaw: what firms ask
Our system has been heavily customised. Does everything have to be rebuilt?
No. Custom fields that are still filled in are recreated. Ones that were abandoned years ago are reported and usually left behind. Workflows and document templates do not transfer between products, so the ones in regular use are rebuilt in the new system and the rest are retired.
Can saved emails stay attached to the right file?
Emails saved into Legal Files through its Outlook or Gmail integration are stored against the file, with attachments. They are loaded to the same matter in the destination with their sent date and sender kept. Counts are run per file, because saved emails are easy to lose in a move without anyone noticing.
What about records we are required to retain?
Retention obligations travel with the records, not the software. Files due to be kept are either loaded as closed matters or held in a read-only copy of Legal Files for the retention period. The choice is written down with the office’s records officer, along with who can reach the copy.
Do trust balances in Legal Files have a place in SimpleLaw?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Legal Files before the plan is fixed. If SimpleLaw turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Legal Files have a place in SimpleLaw?
Most of it does on paper. Emails, time entries, trust ledgers and the firm’s accounts 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Legal Files data is loaded into SimpleLaw?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, time entries, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Legal Files and into SimpleLaw
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.
Legal Files and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Legal Files to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.