Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Moving into a system

Migrating to 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 has a place for, what loading a firm’s records into it involves and what NewLaw sets up beyond the data.

What it accepts

What has a place in SharePoint

Of the fourteen kinds of record that matter to a move, SharePoint has a place for nine, seven in part. A record with no place there is kept as a readable archive.

  • MattersIn partAs a site, library, folder or list row the firm designs; no built-in matter record.
  • ContactsIn partOnly as rows in a list built for the purpose.
  • DocumentsYesFiles in libraries, with columns and versions.
  • EmailsIn partAs .msg or .eml files, with columns for sender and date if set up.
  • NotesIn partAs documents, or as rows in a notes list if one is built.
  • CalendarIn partPossible as a list; usually left in Outlook.
  • TasksIn partPossible as a list; no legal workflow built in.
  • 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 on libraries and lists.
  • TemplatesIn partPrecedents as files; templates can be offered from a library.
  • IntakeNoLeads, enquiries, intake forms and pipelines

Moving into it

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

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

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint on most routes, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what the old system holds 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.

  2. 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.

  3. Trial load

    A trial is loaded into SharePoint and checked against the old system: 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.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in the old system, a final pass over a weekend picks up what changed since the trial. The old system 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 the system the firm is on now. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Type a few letters to find it. If it is not listed, type its name anyway.

Moving toSharePoint

Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what your old system 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.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Where firms come from

Routes into SharePoint

Each route has a page of its own: what moves, what has no place here and how the move is run.

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

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.

How we do itDiscovery to rollout, step by step

SharePoint and the other product names and logos on this page belong to their owners and are used only to identify the systems.

Moving into SharePoint?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.