Data migration route
Legal Files to SharePoint migration
Legal Files are a server-based case management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
Legal FilesServer- Documents: Carried across
- Matters: Carried with mapping
- Contacts: Carried with mapping
- Emails: Carried with mapping
- Notes: Carried with mapping
- Calendar: Carried with mapping
- Tasks: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Time and expenses: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
SharePointCloud- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 8 mapped
- 3 to confirm
- 2 archived
What moves
What moves from Legal Files to SharePoint
Each row is a kind of record Legal Files hold, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping, two kinds have no place in SharePoint and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldAny type of case or matter, as configured by the organisation. | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldContact management with checks for duplicate entries. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldDocument management with text searching. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | HeldTwo-way integration with Outlook and Gmail saves emails and attachments. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes, mail logs and phone logs. | Has a place in partAs documents, or as rows in a notes list if one is built. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldCalendaring with deadline tracking. | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflows, alerts and follow-ups. | Has a place in partPossible as a list; no legal workflow built in. | Carried with mapping |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | Held in partThe vendor lists eBilling among its functions. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustomers add and change fields and screens without programming. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partLegal aid intake is among the uses the vendor describes. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against Legal Files.
- 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.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
- Kept as a readable archive
- SharePoint has no place for it. It is exported in a format that opens without Legal Files 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Legal Files into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Legal Files.
Legal Files run on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SharePoint is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Legal Files
Each office configured its own file types, fields and workflows, so one Legal Files system does not look like the next. The move starts with an inventory of that configuration. Then come the files, the people on them, documents and saved emails. Where the office is part of a government body or a company, retention rules and access restrictions on certain files have to survive the move as well.
Configuration is the data model
File types, screens and fields were set up by the office’s own administrator, often over many years. The field list has to be taken from that system, not assumed. Every custom field is reported with how many files use it, and the office picks the ones that deserve a place in the new system.
Not built around billing
Many of its users are in-house and government teams, which do not bill clients or hold trust money. If the destination is a law firm practice system, billing fields will be empty on every migrated matter. Where the office does record time or outside counsel spend, that is found in the analysis and mapped separately.
Mail and phone logs
Besides documents and emails, a file keeps logs of mail and of phone calls. Offices that answer to the public rely on these as the record of who was told what. They come across as dated notes on the matter with the log type kept, so they can still be filtered.
Restricted files
Investigations and other sensitive files are kept under controlled access. Those restrictions are extracted as a list of files and the users allowed to see them. The destination’s permissions are set from that list before the trial load is opened to staff, so restricted files are locked down before anyone else looks.
On your servers or hosted
The route to a copy of the data depends on where Legal Files runs. An on-premises site works through its own IT team. A hosted site works through the vendor. Government sites often need a security review before data leaves the building, and that review goes in the timetable.
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 Legal Files 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 Legal Files: 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 Legal Files, a final pass over a weekend picks up what changed since the trial. Legal Files 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 Legal Files 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 Legal Files 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
Legal Files to SharePoint: what firms ask
Our system has been heavily customised. Does everything have to be rebuilt?
No. Custom fields that are still filled in are recreated. Ones that were abandoned years ago are reported and usually left behind. Workflows and document templates do not transfer between products, so the ones in regular use are rebuilt in the new system and the rest are retired.
Can saved emails stay attached to the right file?
Emails saved into Legal Files through its Outlook or Gmail integration are stored against the file, with attachments. They are loaded to the same matter in the destination with their sent date and sender kept. Counts are run per file, because saved emails are easy to lose in a move without anyone noticing.
What about records we are required to retain?
Retention obligations travel with the records, not the software. Files due to be kept are either loaded as closed matters or held in a read-only copy of Legal Files for the retention period. The choice is written down with the office’s records officer, along with who can reach the copy.
Do trust balances in Legal Files have a place in SharePoint?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Legal Files before the plan is fixed. If SharePoint turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records SharePoint has no place for?
On this route that is billing records and intake records. They are exported from Legal Files 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 Legal Files data is loaded into SharePoint?
Matters, contacts, emails, notes, calendar entries, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Time entries, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Legal Files 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.
Legal Files and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Legal Files 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.