Data migration route
USB drives to SharePoint migration
USB drives are plain files on equipment the firm controls, and SharePoint is cloud file storage. The folders move as they are, and the work is in permissions, paths and links.
USB drivesFiles- Documents: Carried across
- Emails: Carried with mapping
SharePointCloud- 1 carried
- 1 mapped
What moves
What moves from USB drives to SharePoint
Each row is a kind of record USB drives hold, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across and one kind needs mapping.
| 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 placeFiles in libraries, with columns and versions. | 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 place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against USB drives.
- Carried with mapping
- SharePoint holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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 USB drives to SharePoint 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 SharePoint, 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.
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 SharePoint.
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 SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 SharePoint. 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
SharePoint is 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
USB drives to SharePoint: 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 SharePoint?
SharePoint stores documents. Files in libraries, with columns and versions. 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 SharePoint?
On paper, yes: each kind of record USB drives hold has a place in SharePoint. 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 SharePoint?
Emails 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 USB drives and into SharePoint
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 SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from USB drives to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.