Data migration route
Juris to Neos migration
Juris is a server-based accounting and billing system, and Neos is a cloud case management system for personal injury work. Only part of what Juris holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
NeosCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 2 mapped
- 6 to confirm
- 1 archived
What moves
What moves from Juris to Neos
Each row is a kind of record Juris holds, whether Neos has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping, one kind has no place in Neos and is archived and six kinds are confirmed in the analysis.
| Record | In Juris | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as financial records, coded by lawyer, practice class and office. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients, vendors and names typed on note cards. | 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 | To be confirmed | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNote cards at client or matter level. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partThe vendor’s site lists a Juris Calendar beside the main product. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeLoaded as checklist items. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered in Juris, Juris Suite or the Juris Go mobile app. | 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 | HeldIncludes electronic billing. | 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 | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with multi-level sub-accounts, payables and cheque reconciliation. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeUser-defined fields are created on the relevant tab first. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt for Neos document generation. | 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 Juris.
- 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.
- Kept as a readable archive
- Neos has no place for it. It is exported in a format that opens without Juris 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
Clients and jobs move. The books stay books.
An accounting or billing system and a case management system overlap less than firms expect. Juris knows clients, jobs, time and invoices. Neos knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.
So the plan has two halves. Records with a place in Neos are loaded and checked there. The rest is exported from Juris as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Juris is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.
Juris 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 Juris
Juris holds the firm’s financial history and little else, so a move off it is mostly about money and the codes that classify it. Work in progress, receivables, trust, payables and the ledger are each agreed to a Juris report. Matter documents and calendars usually live in another product beside it, and that product is brought into the same plan.
Three kinds of charge
Juris separates fees, cash expenses and non-cash expenses, and supports accrual, billed and cash accounting methods. Many destinations know only time and disbursements. The mapping has to say where non-cash expenses go, or unbilled and billed cost totals will not agree after the load.
Codes carry the reporting
Billing lawyer, originating lawyer, working timekeeper, practice class, office and billing agreement are all coded on the matter. Partner reports are built on them. Each code table is extracted and mapped, and codes that have drifted into near-duplicates are tidied in Juris before extraction.
Note cards feed conflict searches
Clients and matters can have note cards with other names and special information, and the conflict search reads them. They are where related parties were typed when there was no better field. Note cards come across as notes, and names inside them are flagged in case the firm wants them as contacts.
Juris Suite is a second layer
Firms with Juris Suite enter time, run collections and keep budgets through it. Budgets and collection notes are extra records worth asking about. They are listed in the analysis so nobody finds after go-live that the collections history was never in scope.
Sub-accounts in the chart
The chart of accounts can be split into multi-level sub-accounts to match how the firm is organised. A destination with a flat chart needs those collapsed or turned into tracking categories. The firm’s accountant agrees the new chart first, and the closing trial balance is restated into it before loading.
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 Juris and checking each trial against Juris.
Analysis
We read what Juris 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 Juris, 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 Juris: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Juris 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 Juris as at the cutover date. Juris 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 Juris 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 Juris 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
Juris to Neos: what firms ask
Can we keep our client and matter codes?
Juris codes are carried over wherever the destination allows a firm-set number, with the same padding and separators so old bills still match. If the new system numbers matters itself, the Juris code is stored as a reference and printed on invoices where clients expect to see it.
How much billing history should we bring?
Enough to answer a client’s question about a bill and to run aged debtors properly. Open invoices are loaded with their original dates. Paid invoices from earlier years can be loaded as summaries or left in Juris, kept read only. The destination’s limits usually decide it.
Our e-billing clients have strict formats. What happens?
The task codes, timekeeper classifications and client rates behind your e-bills are extracted and rebuilt in the new system. Past submissions stay where they are. Before go-live one real invoice for each e-billing client is produced from the trial load and checked against that client’s rules.
Do trust balances in Juris 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 Juris 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.
What happens to records Neos has no place for?
On this route that is the firm’s accounts. They are exported from Juris 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 Juris data is loaded into Neos?
Time entries and billing records are carried with mapping, so each mapping is agreed with you first. Documents, emails, tasks, trust ledgers, custom fields and templates 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 Juris and into Neos
Other destinations from Juris
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.
Juris and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from Juris 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.