Data migration route
Local folders to Server drives migration
Local folders and Server drives are both plain files on equipment the firm controls. The folders move as they are, and the work is in permissions, paths and links.
Local foldersFiles- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- 1 carried
- 3 mapped
- 2 archived
What moves
What moves from Local folders to Server drives
Each row is a kind of record Local folders hold, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and two kinds have no place in Server drives and are archived.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in one user’s folders, with no sharing or versions. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partSaved .msg files, and Outlook data files stored under Documents. | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partFile notes kept as Word documents or text files. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimesheets kept as spreadsheets, where a practitioner works that way. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partInvoices as Word or PDF files; no ledger. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPersonal precedents and Word templates saved by the user. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against Local folders.
- Carried with mapping
- Server drives 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
- Server drives has no place for it. It is exported in a format that opens without Local folders 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
Same folders, new home.
Copying folders from Local folders to Server drives sounds like a drag and drop, and for a few gigabytes it is. For a firm’s whole document store the trouble is in the detail. The two stores have different limits on path length and different rules about characters in file names. Files open on someone’s desk during the copy are skipped. Modified dates are reset unless the copy is made with a tool that preserves them. Each of these is checked on a trial copy first.
Permissions and links do not travel. Who can see which folder is set up again in Server drives, and it is a good moment to replace access granted to individuals over the years with groups. Shared links sent to clients stop working when the old store is switched off, so the live ones are listed and reissued. Documents that point at other documents by path, common in spreadsheets, are found and reported. The final pass copies only what changed since the trial.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Local folders stays untouched until the copy in Server drives has been checked.
Where the data is now
Leaving Local folders
Collecting from local folders means going machine by machine, and person by person, because nobody else knows what is there. Volumes are small next to a server drive. The value can be high: the only signed copy of a deed, a partner’s twenty years of precedents, the working files of every matter a sole practitioner has open.
An inventory per computer
Every PC, Mac and laptop in scope is scanned for documents outside the system folders, including machines kept at home and the one in the storeroom nobody has started in a year. Each user profile on a shared computer is scanned separately. The result is a list by machine that the firm signs off.
Local drafts against the shared copy
Where the firm also has a server or cloud drive, a local file is often a later draft of something filed there, or an older one. Files are compared by content. Identical copies are dropped, and the differing ones are shown side by side with their dates so the lawyer can say which is current.
Folders that only look local
A OneDrive, Dropbox or Google Drive folder appears in Explorer like any other, but its contents belong to the cloud account and may not be on the disk in full. Those are collected from the service. Scanning them as local folders double counts files and can copy empty placeholders.
Mail archives under Documents
Outlook’s default location for data files is an Outlook Files folder inside Documents. A scan for documents will find them, sometimes many gigabytes each. They are set aside and handled as mail, matched to matters by folder and correspondent, not loaded as single enormous files.
One person’s own system
A lawyer’s local folders follow a private logic: by year, by court, by the other side’s surname. The owner spends half an hour explaining it, and the mapping to matters is written from that conversation. Where the owner has left the firm, folders are matched on client names and dates alone.
Where it is going
Arriving in Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Local folders hold and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against Local folders: 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 Local folders, a final pass over a weekend picks up what changed since the trial. Local folders 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 Local folders 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 Local folders holds
What is in it, how its records link, and where each piece would sit in Server drives. 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
Structure, permissions and handover
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
Local folders to Server drives: what firms ask
I am a sole practitioner and everything is on my laptop. Where do we start?
With a full copy of the laptop’s user folders taken to a second disk, before anything else. Then a list of your open matters, even handwritten. Folders are matched to that list, the rest is treated as closed files, and you check a sample in the new system before the laptop copy is retired.
Do you need to take our computers away?
No. It is the files that are needed, not the machines. Whether they are collected at each desk or remotely with the firm’s IT provider, and at what hours, is agreed in the analysis. A laptop needs to be switched on, signed in and on the office network or a reliable connection for as long as its copy takes.
What about personal files mixed in with work?
They stay where they are. Each person is shown the list of top-level folders found on their machine and marks the ones that are private. Those paths are excluded before any file is copied. Installed programs and system files are left out in any case.
Do documents from Local folders keep their folders and dates in Server drives?
Server drives store documents. Files in folders, named and dated during the load. 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 Server drives have no place for?
On this route that is time entries and billing records. They are exported from Local folders 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 Local folders data is loaded into Server drives?
Emails, notes and 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 Local folders and into Server drives
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.
Local folders and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Local folders to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.