Data migration route
LawBase to Neos migration
LawBase is a case management system, and Neos is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.
LawBaseCase management- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Documents: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
NeosCloud- 5 carried
- 3 mapped
- 6 to confirm
What moves
What moves from LawBase to Neos
Each row is a kind of record LawBase holds, whether Neos has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldScreens and fields are designed per office and practice area. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldA configurable address book; contacts are entered once and linked to matters. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeCase Docs tab, organised in sub-tabs. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | Held in partBi-directional integration with Microsoft Outlook. | 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 | HeldCase notes of unlimited free text. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldDocketing of appointments and tasks through the email calendar. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeThe general ledger stays in QuickBooks. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldThe whole database layout is defined by the office. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly through HotDocs. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Confirmed in the analysis |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against LawBase.
- 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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. LawBase and Neos may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Neos, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
How LawBase is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. LawBase 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. Neos 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 LawBase
No two LawBase databases are the same, because each office designed its own screens and fields. A move off it starts with reading that design: what tables exist, what each field means in this office, and which are still used. Offices that have run it for decades also hold very long case histories, and the retention decision is made early.
A database the office designed
LawBase lets an office lay out its own screens and choose its own fields for each practice area. A field labelled Adjuster or Docket Number exists because someone asked for it. There is no standard layout to map from. We document the one in use, with the office’s own people explaining what each field has come to mean.
SmartFolders are groupings
SmartFolders group files automatically by attorney, subject or any other value in the system. They behave like saved searches, not containers, so there is nothing in them to move. The useful ones are recreated as saved views or reports in the destination, once the fields they depend on have been loaded.
HotDocs templates
Document assembly runs through HotDocs, and producing a document can also create notes and tasks. The templates are HotDocs files with their own variables and logic. If the destination also works with HotDocs, they may be reused with remapped variables. Otherwise each template is rebuilt in the new system’s own tool.
File room records
LawBase is used for file room management, tracking physical files as well as electronic records. Those entries say where a paper file is. Few cloud systems have a file room module. The location data is brought across in custom fields, or exported as a register for whoever looks after the firm’s storage.
Workflow fired by field changes
Changing a single field can trigger an email, a document, other field updates, a note or calendar tasks. Over the years offices build many of these rules. They are listed during the analysis, because staff often no longer know which steps the system does for them until the new one fails to do it.
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.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Neos, they get a rehearsed cutover of their own. 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 LawBase and checking each trial against LawBase.
Analysis
We read what LawBase holds and how it is organised, then agree with you where each kind of record will sit in Neos. 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 Neos and checked against LawBase: 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
After a short freeze on changes in LawBase, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. LawBase 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 LawBase 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 LawBase 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
LawBase to Neos: what firms ask
Our LawBase has thirty years of cases. Do they all move?
They can, but the office does not have to take them all. Open matters and those inside the retention period move as full records. Older ones can come across as a summary record with notes, or remain in the LawBase database kept read only. The office’s retention policy and how often old files are consulted decide the line.
Does LawBase hold our billing?
The vendor’s material describes case, matter and practice management and does not describe a billing ledger, so we do not assume one. If your office records time or costs in LawBase fields it designed, those are found in the analysis. Any separate billing system is scoped as its own source.
Can our custom screens be recreated?
The fields can, where the destination supports custom fields by matter type. Exact screen layouts usually cannot, and they are rarely worth chasing. We agree with each practice group which fields they still need on screen, load the rest where they can be reported on, and drop fields that have sat empty for years.
Do trust balances in LawBase 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 LawBase 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 LawBase have a place in Neos?
Most of it does on paper. Documents, time entries, billing records, trust ledgers, the firm’s accounts and intake records 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 LawBase data is loaded into Neos?
Emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, time entries, billing records, trust ledgers, the firm’s accounts 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 LawBase and 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.
LawBase and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from LawBase 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.