Data migration route
M-Files to OneDrive migration
M-Files are a document management system, and OneDrive 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.
M-FilesDocument management- Documents: Carried across
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Templates: Confirmed in the analysis
OneDriveCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 3 to confirm
- 4 archived
What moves
What moves from M-Files to OneDrive
Each row is a kind of record M-Files hold, whether OneDrive has a place for it, and what is planned. On this route one kind of record carries across, four kinds have no place in OneDrive and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partOnly where the vault defines a matter or project object type. | No placeA matter is a folder in one user’s drive. | Kept as a readable archive |
| ContactsClients, other parties and referrers | Held in partCustomer and contact object types exist where the vault defines them. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocument objects of one or more files, each with a class and a metadata card. | Has a placeFiles and folders up to the service’s size and path limits. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partSaved message files (.msg or .eml) beside the matter’s documents. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as OneNote notebooks created through OneNote. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflows and their states are part of a vault’s metadata. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldObject types, classes, properties and value lists are all configurable. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as ordinary Word files. | Confirmed in the analysis |
What the plans mean
- Carried across
- OneDrive has a place for this kind of record. It is loaded there and checked against M-Files.
- 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.
- Kept as a readable archive
- OneDrive has no place for it. It is exported in a format that opens without M-Files and handed to the firm as a read-only archive.
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 OneDrive 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 OneDrive 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 OneDrive are finished.
Where the data is now
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.
Where it is going
Arriving in OneDrive
Before anything is loaded into OneDrive, the firm has to say whose OneDrive it is. Every drive has one owner and disappears with that person’s account unless someone acts. That suits an individual’s working papers. For the firm’s shared matter files the same question usually leads to a SharePoint library with OneDrive as the way people sync it.
Whose drive holds the files
Loading the Clients folder into the principal’s OneDrive ties every matter to that one account. If the firm wants that, the owner’s manager and a secondary owner are set in Microsoft 365 so access is not lost on a departure. Otherwise the files go to a SharePoint library and each person syncs it.
A 400 character path limit
The full path, folders and file name together, cannot exceed 400 characters in OneDrive. Document systems that file by client, matter, category and long descriptive titles produce paths over that. Each one is flagged before loading, and the firm approves how it will be abbreviated.
Characters and names that fail
OneDrive refuses names containing " * : < > ? / \ or |, names with leading or trailing spaces, and files beginning with ~$. Emails saved with their subject as the file name are worth checking first, because subjects often contain colons. Names are cleaned before loading and logged.
Do not sync the whole archive
Microsoft recommends syncing no more than 300,000 items in total and warns that performance suffers beyond it. A firm’s full matter history is often larger. Open matters are set to sync and closed ones are left in the cloud, reachable from the browser when someone needs an old file.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in OneDrive on this route, 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 OneDrive. 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 OneDrive 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
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
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 OneDrive. 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
OneDrive 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.
OneDrive needs little building and a fair amount of policy. The settings that matter to a law firm are in the SharePoint and Microsoft 365 admin centres: who may share outside the firm, how long a leaver’s drive is kept, and what syncs to laptops. Staff are shown the difference between their own drive and the firm’s shared libraries.
What is agreed and set up
- External sharing limits for OneDrive set by an administrator
- Retention period and secondary owner for leavers’ drives
- Known folder redirection decided for Desktop and Documents
- Sync app deployed with Files On-Demand turned on
- Version history limits set for all users’ drives
- Guidance on what belongs in OneDrive and what in SharePoint
Questions
M-Files to OneDrive: 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 OneDrive?
OneDrive stores documents. Files and folders up to the service’s size and path limits. 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.
What happens to records OneDrive has no place for?
On this route that is matters, contacts, tasks and custom fields. They are exported from M-Files in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before M-Files data is loaded into OneDrive?
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.
Other routes
Other routes from M-Files and into OneDrive
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.
M-Files and OneDrive are the names and marks of their owners, used here only to identify the two systems.
Moving from M-Files to OneDrive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.