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

Data migration route

M-Files to NetDocuments migration

M-Files are a document management system, and NetDocuments is a cloud one. The test of this move is whether profiles, versions and access rules survive it.

FromM-FilesDocument management
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Notes: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Templates: Confirmed in the analysis
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 2 mapped
  • 4 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from M-Files to NetDocuments

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

Records in M-Files and their place in NetDocuments
RecordIn M-FilesIn NetDocumentsWhat 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 client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeld in partCustomer and contact object types exist where the vault defines them.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocument objects of one or more files, each with a class and a metadata card.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows and their states are part of a vault’s metadata.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldObject types, classes, properties and value lists are all configurable.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against M-Files.
Carried with mapping
NetDocuments 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.
Kept as a readable archive
NetDocuments 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, versions and security, kept intact.

Between two document management systems the files are the easy part. What a firm has built in M-Files is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. NetDocuments has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.

Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in NetDocuments before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.

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 NetDocuments 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

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 toNetDocuments

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

Setting up NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

M-Files to NetDocuments: 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 NetDocuments?

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 NetDocuments has no place for?

On this route that is contacts. 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 NetDocuments?

Matters and custom fields are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks 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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from M-Files to NetDocuments?

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

We reply within one business day.