Moving off a system
Migrating from M-Files
Metadata-driven document management in which documents, clients and projects are objects in a vault and folders are views built from metadata. This page sets out what M-Files hold, what moving off it involves and where its records can go.
Where it can go
Routes from M-Files
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
Actionstep5 of 8 kinds of record have a place
Centerbase5 of 8 kinds of record have a place
Clio Manage5 of 8 kinds of record have a place
MyCase5 of 8 kinds of record have a place
Rocket Matter5 of 8 kinds of record have a place
SimpleLaw5 of 8 kinds of record have a place
Smokeball5 of 8 kinds of record have a place
SurePoint Finance Enterprise2 of 8 kinds of record have a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box2 of 8 kinds of record have a place
Dropbox1 of 8 kinds of record has a place
Google Drive1 of 8 kinds of record has a place
OneDrive1 of 8 kinds of record has a place
Server drives1 of 8 kinds of record has a place
SharePoint5 of 8 kinds of record have a place
Sync.com1 of 8 kinds of record has a place
What it holds
The records M-Files keep
Fourteen kinds of record matter to a move. M-Files keep five of them, three in part, and three could not be confirmed from its maker’s own material.
- MattersIn partOnly where the vault defines a matter or project object type.
- ContactsIn partCustomer and contact object types exist where the vault defines them.
- DocumentsYesDocument objects of one or more files, each with a class and a metadata card.
- EmailsTo be confirmedEmails saved to matters or to the store
- NotesTo be confirmedFile notes, matter notes and contact notes
- CalendarNoAppointments, court dates and deadlines
- TasksIn partWorkflows and their states are part of a vault’s metadata.
- 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 fieldsYesObject types, classes, properties and value lists are all configurable.
- TemplatesTo be confirmedPrecedents, document templates and automation
- IntakeNoLeads, enquiries, intake forms and pipelines
Moving off it
Leaving M-Files
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.
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.
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.
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.
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.
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.
The system
What M-Files are
M-Files is a document management system sold to many industries, with professional services among them. Its central idea is that a document is described, not placed: users say what a document is and what it relates to, and the system works out where it appears. Accounting, consulting and some legal practices use it as their client or engagement file.
Everything is stored in a vault, which is a database of objects and not a file system. Documents are one object type. A vault can define others, such as customer or project, and link documents to them through properties. Each object has a class and a metadata card. The folders users see are views calculated from metadata, and every change to a file or its metadata creates a new version.
- Kind
- Document management
- Runs as
- Desktop program with its data in its maker’s cloud (not confirmed from its maker’s material)
- Made by
- M-Files
- Mainly used in
- Worldwide
- Also known as
- M Files, MFiles, M-Files Cloud
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 M-Files hold 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 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.
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
Choose where the M-Files 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 M-Files 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
- Actionstep
- Box
- Centerbase
- Clio Manage
- Dropbox
- Filevine
- Full data export
- Gladiate
- Google Drive
- iManage Cloud
- Lawmatics
- LexWorkplace
- Litify
- Microsoft SQL Server
- MyCase
- Neos
- NetDocuments
- OneDrive
- QuickBooks Online
- Rocket Matter
- Server drives
- SharePoint
- SimpleLaw
- SmartAdvocate
- Smokeball
- Soluno
- SQLite
- SurePoint Finance Enterprise
- Sync.com
Questions
Moving off M-Files: 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.
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.
M-Files and the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off M-Files?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.