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

Data migration route

M-Files to SharePoint migration

M-Files are a document management system, and SharePoint is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromM-FilesDocument management
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Tasks: Carried with mapping
  5. Custom fields: Carried with mapping
  6. Emails: Confirmed in the analysis
  7. Notes: Confirmed in the analysis
  8. Templates: Confirmed in the analysis
ToSharePointCloud
  • 1 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from M-Files to SharePoint

Each row is a kind of record M-Files hold, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, four kinds need mapping and three kinds are confirmed in the analysis.

Records in M-Files and their place in SharePoint
RecordIn M-FilesIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partOnly where the vault defines a matter or project object type.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 referrersHeld in partCustomer and contact object types exist where the vault defines them.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldDocument objects of one or more files, each with a class and a metadata card.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows and their states are part of a vault’s metadata.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldObject types, classes, properties and value lists are all configurable.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against M-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.

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

Profiles flatten into folders and an index.

A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from M-Files to SharePoint flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.

What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in SharePoint before anyone else is given access.

How M-Files are run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of M-Files depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to M-Files is kept running until the checks on SharePoint are finished.

Where the data is now

There is no folder tree to copy out of M-Files. A vault holds objects and the relationships between them, and the folders on screen are searches. An extraction therefore exports objects with their properties, then rebuilds a structure the destination understands: usually a client, a matter beneath it, and documents filed to the matter by the properties that linked them in the vault.

  1. Views are not folders

    A document may appear under one view by customer, another by project and a third by class, because each view is a query. Exporting what users see would copy the same file several times. The extraction takes each object once, with its property values, and the mapping picks which properties decide its one home.

  2. Every vault is built differently

    Object types, classes, property definitions and value lists are set per vault, and the same word can mean three things: Customer the object type, Customer the class and Customer the property each have their own identifier. The vault’s metadata structure is exported and read before any content, and the mapping is written against it.

  3. Objects that are not documents

    Customers, contacts or projects held as objects have metadata but need not contain any file. They are data in their own right, sometimes the firm’s only list of engagements. They are extracted as tables and reconciled with the practice management system, so the destination gets one clean list of clients and matters.

  4. A version on every change

    M-Files creates a new version whenever a file or its metadata changes, including when an object moves through a workflow. A document can have dozens of versions, of which only a few differ in content. Versions where the file itself changed are identified, and the firm decides whether the others are needed.

  5. Multi-file documents, outside sources

    A document object can contain more than one file, and a vault can connect to an external database to supply values for an object type. Multi-file objects are split or zipped according to the destination. Values drawn from an outside database are captured at extraction, because that connection will not exist afterwards.

More about moving off M-Files

Where it is going

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.

More about moving into SharePoint

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.

  1. Analysis

    We read what M-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.

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

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in M-Files, a final pass over a weekend picks up what changed since the trial. M-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 M-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

Step 1 of 5: Start with the route

Moving fromM-Files
Moving toSharePoint

The route comes from this page. 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 M-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.

  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.

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

M-Files to SharePoint: what firms ask

We find everything by metadata. Will we lose that in a folder-based system?

Some of it. The properties that identify client, matter, document type, author and date map to fields nearly every legal document system has. Properties particular to your vault go to custom fields where the destination has them. The analysis lists each property against where it will go, including the ones with no place.

Do workflow states come across?

A workflow state is a property value, so it can be exported, for example as draft, approved or signed. The workflow itself, with its transitions and permissions, is configuration and does not move. States are usually kept as a document status field, and open approvals are finished before cutover.

Do documents from M-Files keep their folders and dates in SharePoint?

SharePoint stores documents. Files in libraries, with columns and versions. 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.

Does everything in M-Files have a place in SharePoint?

Most of it does on paper. Emails, notes and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SharePoint is kept as a readable archive, and you see which before the move.

What has to be decided before M-Files data is loaded into SharePoint?

Matters, contacts, tasks and custom fields are carried with mapping, so each mapping is agreed with you first. Emails, notes and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

M-Files and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from M-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.