Data migration route
USB drives to NetDocuments migration
USB drives are plain files on equipment the firm controls, and NetDocuments is a cloud document management system. The move adds structure the folders never had: a client, a matter and a document type for every file.
USB drivesFiles- Documents: Carried across
- Emails: Carried across
NetDocumentsCloud- 2 carried
What moves
What moves from USB drives to NetDocuments
Each row is a kind of record USB drives hold, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldLoose files and folders; no sharing, versions or access control on FAT formats. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partSaved message files or copied Outlook data files, where someone put them there. | Has a placeLoaded as email items profiled to the matter. | Carried across |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against USB drives.
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
Folders go in. Profiled workspaces come out.
A document management system asks questions of every file that a folder never did: which client, which matter, what type of document, who wrote it. Coming from USB drives, the answers have to be worked out from where a file sits and what it is called. The analysis reads the folder tree, proposes how its levels map to client, matter and folder in NetDocuments, and lists what does not fit. Those exceptions go to the firm as a spreadsheet to correct.
Not everything should move. Shared drives collect installers, duplicates, personal files and working copies ten versions deep. The firm decides what is in scope by folder, by age or by file type, and the rest is left where it is or archived. File dates are preserved. Paths too long for NetDocuments, characters it does not allow and files that will not open are reported before the load. The copy can be repeated, so the final pass picks up only what changed.
With USB drives the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in NetDocuments.
Where the data is now
Leaving USB drives
Each USB drive is its own small puzzle, and the first task is to say what it is. A working copy of matter files is handled one way. The backup of an old practice system is a database to be restored, not a set of documents. Material received from a client belongs to one matter and may need to be kept exactly as it was received.
Identify each drive first
Every drive is labelled and listed, and its contents are classed as loose documents, a system backup, or third-party material for a known matter. A stick holding a .bak or other backup file goes to whoever is handling that old system, because the documents inside cannot be reached by copying.
Copy once, then put it away
Flash drives can fail without warning, and each reading is a small risk. It is safer to copy a drive once and do the sorting and matching on the copy than to keep going back to the stick. How the copy is made and checked is agreed with the firm’s IT provider, and the drive goes back in the safe.
Times shift on FAT drives
FAT file systems store times in local time and record the modified time only to the nearest two seconds. The same document on a stick and on the server can show dates an hour apart after a daylight saving change. Matching dates is therefore an unreliable way to find duplicates on these drives.
Encrypted drives need their password
A drive protected with BitLocker To Go or a hardware keypad opens only with its password or recovery key. Where the person who set it has left, the firm’s IT provider may hold a recovery key. If nobody does, the contents cannot be read, and that is recorded against the drive.
Material from clients and other parties
Drives received in a matter are evidence of what was handed over. The original folder structure and file dates are preserved in the copy, and the files are filed to the matter as a set under the date received. What happens to the physical drive, kept or returned, follows the firm’s own file rules.
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 USB drives hold 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 USB drives: 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 USB drives, a final pass over a weekend picks up what changed since the trial. USB drives are 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 USB drives 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 USB drives 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
USB drives to NetDocuments: what firms ask
We have a box of old USB drives and no idea what is on them. Is it worth including them?
Usually it is worth the listing, which is quick. Each drive is summarised: how many files, what kinds, what date range, which client names appear. The firm then chooses which drives are loaded, which are kept as they are, and which hold nothing but copies of files already on the server.
One drive has a backup from the system we used ten years ago. Can that be brought in?
Possibly. It depends on whether the backup can be restored, which needs a copy of the old software or a database engine that reads its format. That is tested on its own before any promise is made. If it restores, its matters and documents are treated like any other source system.
Is it safe to plug unknown drives into our network?
That is a question for the firm’s IT provider, and the cautious answer is no. A drive of unknown origin can carry malicious software as well as documents. How unknown drives are read, and on which machine, is agreed with the IT provider before any of them is opened.
Do documents from USB drives 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 USB drives have a place in NetDocuments?
On paper, yes: each kind of record USB drives hold has a place in NetDocuments. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before USB drives data is loaded into NetDocuments?
Less than on most routes: each kind of record here either carries across or is archived. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from USB drives 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.
USB drives and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from USB drives 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.