Data migration route
M-Files to Rocket Matter migration
M-Files are a document management system, and Rocket Matter is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.
M-FilesDocument management- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Custom fields: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Templates: Confirmed in the analysis
Rocket MatterCloud- 4 carried
- 1 mapped
- 3 to confirm
What moves
What moves from M-Files to Rocket Matter
Each row is a kind of record M-Files hold, whether Rocket Matter has a place for it, and what is planned. On this route four kinds of record carry across, one kind needs mapping 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. | Has a placeMatter File # and matter name are required on import. | Carried across |
| ContactsClients, other parties and referrers | Held in partCustomer and contact object types exist where the vault defines them. | Has a placeImported as clients or as other contact types. | Carried across |
| 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 placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails can be filed to matters; it does not hold whole mailboxes. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | 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. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldObject types, classes, properties and value lists are all configurable. | Has a placeCustom fields and custom pages on contacts and matters. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partWord merge templates are rebuilt with the product’s own merge fields. | Confirmed in the analysis |
What the plans mean
- Carried across
- Rocket Matter has a place for this kind of record. It is loaded there and checked against M-Files.
- Carried with mapping
- Rocket Matter 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
Profiled documents become matter documents.
A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from M-Files to Rocket Matter is a translation from one to the other, and it depends on the client and matter numbers in M-Files matching matters that exist in Rocket Matter. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.
Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.
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 Rocket Matter 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 Rocket Matter
This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.
A file number on every matter
Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.
Clients and address-book contacts
A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.
Accounting set-up comes first
Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.
Pick the document store early
Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.
One ledger of record
NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Rocket Matter 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 Rocket Matter. 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 Rocket Matter 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 Rocket Matter. 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
Setting up Rocket Matter
Loaded data is not yet a working system. This is what NewLaw sets up in Rocket Matter, beyond the migration, so that people can work in it from the first day.
Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.
Set-up decisions in Rocket Matter
- Timekeepers, matter owners and the rates each one bills at
- Matter File number format and matter templates by work type
- Bank accounts, chart of accounts and the QuickBooks Online decision
- Custom fields and custom pages for contacts and matters
- Document storage choice and the matter folder naming pattern
- Word merge templates, invoice layouts and intake forms
Questions
M-Files to Rocket Matter: 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 Rocket Matter?
Rocket Matter stores documents. Native storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. 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 Rocket Matter?
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 Rocket Matter 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 Rocket Matter?
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.
Other routes
Other routes from M-Files and into Rocket Matter
Other destinations from M-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.
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 Rocket Matter are the names and marks of their owners, used here only to identify the two systems.
Moving from M-Files to Rocket Matter?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.