Data migration route
Docrio to Neos migration
Docrio is a cloud document management system, and Neos is a cloud case management system for personal injury work. The move is matching each file in Docrio to its case in Neos.
DocrioCloud- Documents: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
NeosCloud- 1 carried
- 1 mapped
- 3 to confirm
What moves
What moves from Docrio to Neos
Each row is a kind of record Docrio holds, whether Neos has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiled against Litify matters, with tags and editable file information. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| 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 |
| TasksTo-dos and workflow steps assigned to people | To be confirmedTasks can be raised against a document; they are Litify records. | Has a placeLoaded as checklist items. | Confirmed in the analysis |
| 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 | HeldDocument generation templates with merge fields and conditional logic. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against Docrio.
- 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
Every document goes to the case it belongs to.
A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Docrio organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.
Cases must exist in Neos before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Docrio 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 Docrio is kept running until the checks on Neos are finished.
Where the data is now
Leaving Docrio
Docrio cannot be separated from the Litify system it sits in. Each file is tied to a Litify record, and that record supplies the matter number, client and case type. Leaving it means extracting the files together with the identifiers of the records they hang from. Usually it happens as part of moving the whole Litify system, not the documents alone.
Files hang off Litify records
A document’s context is the record it was saved to, normally a matter. That relationship is how a file finds its matter in the destination. Keeping the record identifier with every file is what allows it to be joined to the matter export and filed under the right matter.
Folders and tags by case type
Litify firms normally set a standard folder structure for each case type and add tags on top. The structure for a motor vehicle claim differs from the one for a mass tort. Each case type’s folder set is mapped separately, and tags become document categories or are written into the name.
Templates do not travel
Generation templates read fields from Litify by name. In another system those fields are called something else, or do not exist. The documents already generated move as ordinary files. The templates themselves are rebuilt in the destination’s own automation, starting with the ones the firm uses most.
Confirm where files are stored
How Docrio stores file content, and the route for exporting it in bulk, is confirmed with the firm’s Litify administrator at the start. Access is given in whatever way the firm decides. Volumes in injury practices are large, with medical records and video, so transfer time is part of the plan.
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.
Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. 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 Docrio and checking each trial against Docrio.
Analysis
We read what Docrio 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 Docrio: 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 Docrio, a final pass over a weekend picks up what changed since the trial. Docrio 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 Docrio 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 Docrio 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
Docrio to Neos: what firms ask
We are leaving Litify. Are our documents part of that move?
They should be scoped explicitly. A matter export on its own should not be assumed to contain the documents, and the files may come out by a different route from the Litify data. The plan covers both and joins them on the matter, and document counts are checked per matter after the trial load.
Can we keep Litify and move only the documents to iManage or NetDocuments?
Litify publishes integrations with both, so that arrangement exists. The existing files are then moved from Docrio into workspaces that match the Litify matters, and new documents are saved through the integration. The matter number is the join, so it has to be identical on both sides before the load.
Do documents from Docrio keep their folders and dates in Neos?
Neos stores documents. Case Docs tab, organised in sub-tabs. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Docrio have a place in Neos?
Most of it does on paper. Emails, tasks and custom fields 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 Docrio data is loaded into Neos?
Templates are carried with mapping, so each mapping is agreed with you first. Emails, tasks and custom fields 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 Docrio 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.
Docrio and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from Docrio 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.