Data migration route
SharePoint data to Full data export
SharePoint is cloud file storage, and Full data export is a store of data kept as files the firm holds. What lands in Full data export is the register: every file’s name, place, dates and details, with the files themselves stored beside it.
SharePointCloud- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
Full data exportFiles- 6 carried
- 3 mapped
What moves
What moves from SharePoint to Full data export
Each row is a kind of record SharePoint holds, whether Full data export has a place for it, and what is planned. On this route six kinds of record carry across and three kinds need mapping.
| 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. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | Held in partOnly if the firm keeps a contacts list in a SharePoint list. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldFiles in document libraries, with versions, columns and check-out. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| 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 partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held in partOneNote notebooks and site pages, where the firm used them. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held in partCalendar lists exist; most firms keep calendars in Outlook instead. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partTask lists exist where a firm built them. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldColumns and content types defined by the firm on libraries and lists. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents as files; a library can offer document templates through content types. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against SharePoint.
- Exported with mapping
- Full data export 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
The files, and a register of what each one is.
A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from SharePoint are exported to storage the firm controls, and Full data export receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.
How useful the register is depends on how much SharePoint knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Full data export, and opening the file to confirm it is the same one.
SharePoint is hosted by its maker and Full data export sits 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 Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what SharePoint holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything SharePoint holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against SharePoint: record counts, totals where SharePoint holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in SharePoint, the export is run a final time and checked again. There is nothing to go live. SharePoint is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Full data export. 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
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
SharePoint to Full data export: 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.
Does the copy in Full data export hold documents from SharePoint?
Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in SharePoint as at the export date.
Does everything in SharePoint have a place in Full data export?
On paper, yes: each kind of record SharePoint holds has a place in Full data export. 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 SharePoint is written out to Full data export?
Emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from SharePoint and into Full data export
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 Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from SharePoint to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.