Data migration route
Server drives to NetDocuments migration
Server 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.
Server drivesFiles- Documents: Carried across
- Emails: Carried across
- Templates: Carried with mapping
NetDocumentsCloud- Notes: Kept as a readable archive
- Billing: Kept as a readable archive
- 2 carried
- 1 mapped
- 2 archived
What moves
What moves from Server drives to NetDocuments
Each row is a kind of record Server drives hold, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and two kinds have no place in NetDocuments and are archived.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders; path, name and dates are the only description. | 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 partMessages dragged from Outlook into matter folders as .msg files. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partFile notes kept as Word documents or text files in the matter folder. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partCopies of invoices saved as PDFs; no ledger. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partA precedents folder of Word templates, with or without macros. | 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 Server drives.
- 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.
- Kept as a readable archive
- NetDocuments has no place for it. It is exported in a format that opens without Server drives 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
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 Server 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 Server 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 Server drives
Moving off a server drive is a job of interpretation. The files copy easily. Working out which matter each folder belongs to does not, because the tree was built by many hands over many years and the naming changed with every new secretary. The analysis reads the tree, proposes rules for matching folders to matters, and shows the firm what the rules fail to place.
The folder tree is the index
Each matter folder is matched to a matter in the new system by the client name and matter number in its path. Some match exactly. Others say only Smith or Old files 2011. The unmatched folders are listed with their size and last-modified date, and the firm assigns them, archives them or leaves them.
Paths past 260 characters
Windows has long limited a full path to 260 characters, and deep matter trees routinely pass it. Such files exist but Explorer and Word may refuse to open or copy them. They are counted in the analysis and shortened to suit the destination’s own limit.
Permissions do not travel with files
Who may open the Partners folder or a restricted matter is set in Windows permissions on the server. A copy of the files should not be assumed to carry any of that. The permissions on each top-level and matter folder are reported before the move and rebuilt as groups or matter security in the new system.
Folders another system owns
The same drive often holds the document store of a practice management or accounting system, in folders with coded names. Those files are indexed in that system’s database and mean little without it. They are moved through the system that owns them, and kept out of the loose-file scan.
What accumulates over twenty years
Server drives collect shortcuts, temporary Word files, copies named Final v3 and whole duplicated matter folders. Exact duplicates are identified and reported. The firm sets the rule for near-duplicates, since only a person can say whether Final or Final v3 is the one that went to court.
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 Server 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 Server 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 Server drives, a final pass over a weekend picks up what changed since the trial. Server 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 Server 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 Server 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
Server drives to NetDocuments: what firms ask
Our folders are a mess. Do we have to tidy them before the move?
No, and it is better not to rename things by hand beforehand. The analysis works from the tree as it stands and proposes matching rules. Staff time is better spent on the short list of folders the rules cannot place, and on deciding what is old enough to archive without filing it to a matter.
Will the dates on our documents be kept?
The modified date on each file is read from the server and passed to the new system where it accepts a document date. Created dates on a server are less reliable, because copying files between drives in the past can have changed them. The trial load compares document dates on sample matters against the old folders.
Can staff keep using the S: drive after go-live?
For reading, yes: the drive is kept read only as the fall-back record. Not for filing. If people can still save to the old drive, some will, and within a month the firm has two places to look for every document. The drive is switched to read only at cutover.
Do documents from Server 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.
What happens to records NetDocuments has no place for?
On this route that is notes and billing records. They are exported from Server drives 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 Server drives data is loaded into NetDocuments?
Templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Server 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.
Server drives and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Server 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.