Data migration route
SimpleLaw to Neos migration
SimpleLaw is a cloud practice management system, and Neos is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
SimpleLawCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
NeosCloud- 7 carried
- 5 mapped
- 1 to confirm
What moves
What moves from SimpleLaw to Neos
Each row is a kind of record SimpleLaw holds, whether Neos has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping 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 placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldLeads, clients and other contacts in one CRM. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| 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 placeCase Docs tab, organised in sub-tabs. | 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 partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldClients can also add notes through the portal. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments by firm member or type, synced with Google or Outlook. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldWorkflows create tasks, appointments and documents for standard case types. | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldOne timer per matter, plus manual entries. | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee, instalment, contingency, pro bono and LEDES invoices. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust billing and initial trust payments are supported; ledger detail was not confirmed. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields feed intake forms, reports and document automation. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable templates filled from stored data and intake answers. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldWebsite forms, custom intake forms and lead tracking in the CRM. | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Carried across |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against SimpleLaw.
- Carried with mapping
- Neos 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Neos. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from SimpleLaw has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without SimpleLaw, and kept as the record of what was billed and held.
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 Neos 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 Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in SimpleLaw and checking each trial against SimpleLaw.
Analysis
We read what SimpleLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 SimpleLaw, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Neos as a trial and checked against SimpleLaw: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in SimpleLaw are frozen for an agreed window, the data is collected a final time and Neos 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 SimpleLaw as at the cutover date. 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 Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
SimpleLaw to Neos: 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 Neos?
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 SimpleLaw before the plan is fixed. If Neos 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 SimpleLaw have a place in Neos?
Most of it does on paper. Trust ledgers 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 Neos is kept as a readable archive, and you see which before the move.
What has to be decided before SimpleLaw data is loaded into Neos?
Emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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 SimpleLaw and into Neos
Other destinations from SimpleLaw
Other systems that move into Neos
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 Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from SimpleLaw to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.