Data migration route
SharePoint to Server drives migration
SharePoint is cloud file storage, and Server drives are plain files on equipment the firm controls. The folders move as they are, and the work is in permissions, paths and links.
SharePointCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 3 mapped
- 5 archived
What moves
What moves from SharePoint to Server drives
Each row is a kind of record SharePoint holds, 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 five kinds have no place in Server drives and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNo matter record as such; firms model matters as sites, libraries, folders or list rows. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | Held in partOnly if the firm keeps a contacts list in a SharePoint list. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles in document libraries, with versions, columns and check-out. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly messages saved into a library as .msg or .eml files. | 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 partOneNote notebooks and site pages, where the firm used them. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | Held in partCalendar lists exist; most firms keep calendars in Outlook instead. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partTask lists exist where a firm built them. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldColumns and content types defined by the firm on libraries and lists. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents as files; a library can offer document templates through content types. | 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 SharePoint.
- 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 SharePoint 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 SharePoint 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.
SharePoint is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What SharePoint will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving SharePoint
No two firms’ SharePoint looks alike, because the firm or its IT provider designed it. One has a site per client, another a single library with a folder per matter, a third filed everything by column and has no folders at all. The move starts by reading that design, since the matter a document belongs to may be recorded in any of several places.
Find every site that holds files
Matter documents can be in the main document site, in the Files tab of a Teams channel, and in the separate sites that private channels create. An administrator’s site list is the starting point. Each library is then classed as matter files, firm administration or abandoned, and only the first two are scoped.
Columns hold what folders do not
Where a library uses columns for matter number, client or document type, that information is not in the file or its path. A copy taken through the sync app cannot be relied on to carry it. The column values are exported with each document so the destination can file by them, or they are written into the folder path.
Unique permissions need a report
Permissions can be broken at site, library, folder and file level, and after a few years they usually have been. Nobody can state from memory who may see what. A permissions report across the libraries shows which matters are restricted, and that list is carried into the security design of the new system.
Lists are data, not documents
A matter register, a deeds register or a conflict list kept as a SharePoint list is a table. It moves as records, by export to a spreadsheet and a mapping of its columns to fields, on a separate track from the files. Firms often forget these lists exist until the analysis turns them up.
Versions and checked-out files
Libraries keep major versions, and some keep minor drafts as well. The firm chooses how many come across. Files that someone checked out and never checked back in are a known trap: other people may see only an older copy, so these are found and checked in before the final collection.
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 SharePoint holds 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 SharePoint: 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 SharePoint, a final pass over a weekend picks up what changed since the trial. SharePoint 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 SharePoint 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 SharePoint 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
SharePoint to Server drives: what firms ask
We only use Teams. Do we have anything in SharePoint to move?
Yes. The Files tab in every Teams channel is a folder in a SharePoint site, and each private or shared channel has a site of its own. If matter documents were dropped into channels, they are in SharePoint. Chat messages are stored differently and are a separate question from the files.
Can the new system keep our SharePoint columns?
It depends whether the destination has matching fields. Matter number and client usually map to the matter itself. Document type and author often have a home on the document profile. A column with nowhere to go is either written into the document’s name or description, or left behind, and the firm sees which before the move.
Should we move to SharePoint or to a legal document management system?
That is a decision about how the firm works, and it is the firm’s to make. What can be said plainly is that SharePoint arrives empty of legal structure: matters, filing rules and email filing are all designed and built. The analysis sets out what that build involves for the firm’s matter volume.
Do documents from SharePoint 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 matters, contacts, calendar entries, tasks and custom fields. They are exported from SharePoint 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 SharePoint 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 SharePoint 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.
SharePoint and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from SharePoint 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.