Moving off a system
Migrating from SharePoint
Microsoft 365’s shared document platform, built from sites and document libraries with columns, version history and layered permissions. This page sets out what SharePoint holds, what moving off it involves and where its records can go.
Where it can go
Routes from SharePoint
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep9 of 9 kinds of record have a place
Centerbase9 of 9 kinds of record have a place
Clio Manage9 of 9 kinds of record have a place
MyCase9 of 9 kinds of record have a place
Rocket Matter9 of 9 kinds of record have a place
SimpleLaw8 of 9 kinds of record have a place
Smokeball9 of 9 kinds of record have a place
SurePoint Finance Enterprise3 of 9 kinds of record have a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
What it holds
The records SharePoint keeps
Fourteen kinds of record matter to a move. SharePoint keeps nine of them, seven in part.
- MattersIn partNo matter record as such; firms model matters as sites, libraries, folders or list rows.
- ContactsIn partOnly if the firm keeps a contacts list in a SharePoint list.
- DocumentsYesFiles in document libraries, with versions, columns and check-out.
- EmailsIn partOnly messages saved into a library as .msg or .eml files.
- NotesIn partOneNote notebooks and site pages, where the firm used them.
- CalendarIn partCalendar lists exist; most firms keep calendars in Outlook instead.
- TasksIn partTask lists exist where a firm built them.
- Time and expensesNoTime and expense entries, billed and unbilled
- BillingNoInvoices, payments and debtor balances
- Trust moneyNoTrust or client account ledgers and balances
- Firm accountsNoGeneral ledger, office account and payables
- Custom fieldsYesColumns and content types defined by the firm on libraries and lists.
- TemplatesIn partPrecedents as files; a library can offer document templates through content types.
- IntakeNoLeads, enquiries, intake forms and pipelines
Moving off it
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.
The system
What SharePoint is
SharePoint is where shared files live in Microsoft 365. A firm may have set it up on purpose as its document store, or may be using it without knowing: every team in Microsoft Teams keeps its files in a SharePoint site. Older firms may still run SharePoint Server on their own hardware.
Content sits in sites, and each site has document libraries. A library is more than a folder. It can have columns, so a document carries a matter number or a document type as data and not only in its name. Versions are kept, and permissions can be set on the site, the library, a folder or a single file.
- Kind
- File storage
- Runs as
- Cloud, hosted by its maker
- Made by
- Microsoft
- Mainly used in
- Worldwide
- Also known as
- Sharepoint, SharePoint Online, SharePoint in Microsoft 365, SharePoint Server, Microsoft Teams files
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in the new system on most routes, 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 the new system. 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 the new system 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
Choose where the SharePoint data is going, or tell us you have not decided. 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 the new system. 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.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
Questions
Moving off SharePoint: 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.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
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 the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.