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

Data migration route

M-Files to SimpleLaw migration

M-Files are a document management system, and SimpleLaw is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

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

What moves

What moves from M-Files to SimpleLaw

Each row is a kind of record M-Files hold, whether SimpleLaw 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.

Records in M-Files and their place in SimpleLaw
RecordIn M-FilesIn SimpleLawWhat 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 placeCarried across
ContactsClients, other parties and referrersHeld in partCustomer and contact object types exist where the vault defines them.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldDocument objects of one or more files, each with a class and a metadata card.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed 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 placeCarried across
Custom fieldsFields and record types the firm added itselfHeldObject types, classes, properties and value lists are all configurable.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt using SimpleLaw’s own automation.Confirmed in the analysis

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against M-Files.
Carried with mapping
SimpleLaw 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 SimpleLaw 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 SimpleLaw. 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 SimpleLaw 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 a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SimpleLaw 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 SimpleLaw. 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 SimpleLaw 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

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

SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. 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 SimpleLaw?

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 SimpleLaw 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 SimpleLaw?

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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from M-Files to SimpleLaw?

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

We reply within one business day.