Data migration route
Docrio to NetDocuments migration
Docrio and NetDocuments are each a cloud document management system. The test of this move is whether profiles, versions and access rules survive it.
DocrioCloud- Documents: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
NetDocumentsCloud- 1 carried
- 1 mapped
- 3 to confirm
What moves
What moves from Docrio to NetDocuments
Each row is a kind of record Docrio holds, whether NetDocuments 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 placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email items profiled to the matter. | 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. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs custom profile attributes, created in the repository before the load. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument generation templates with merge fields and conditional logic. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against Docrio.
- Carried with mapping
- NetDocuments 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
Profiles, versions and security, kept intact.
Between two document management systems the files are the easy part. What a firm has built in Docrio is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. NetDocuments has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.
Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in NetDocuments before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.
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 NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Docrio holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments 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 NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Docrio to NetDocuments: 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 NetDocuments?
NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 NetDocuments?
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 NetDocuments is kept as a readable archive, and you see which before the move.
What has to be decided before Docrio data is loaded into NetDocuments?
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 NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Docrio to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.