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

Data migration route

M-Files to SurePoint Finance Enterprise migration

M-Files are a document management system, and SurePoint Finance Enterprise 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: Confirmed in the analysis
  4. Emails: Confirmed in the analysis
  5. Notes: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Custom fields: Confirmed in the analysis
  8. Templates: Confirmed in the analysis
ToSurePoint Finance EnterpriseCloud
  • 2 carried
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from M-Files to SurePoint Finance Enterprise

Each row is a kind of record M-Files hold, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route two kinds of record carry across and six kinds are confirmed in the analysis.

Records in M-Files and their place in SurePoint Finance Enterprise
RecordIn M-FilesIn SurePoint Finance EnterpriseWhat 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 placeCarried across
DocumentsFiles stored in or linked from the systemHeldDocument objects of one or more files, each with a class and a metadata card.To be confirmedConfirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed 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.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedTo be confirmedConfirmed in the analysis

What the plans mean

Carried across
SurePoint Finance Enterprise 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.

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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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

Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.

  1. Entities and tax IDs first

    The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.

  2. History has to balance

    Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.

  3. E-billing detail on time entries

    For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.

  4. Dockets as well as appointments

    Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.

  5. Cost recovery codes

    Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.

More about moving into SurePoint Finance Enterprise

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SurePoint Finance Enterprise 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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 toSurePoint Finance Enterprise

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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise

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

The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.

Set-up decisions in SurePoint Finance Enterprise

  • Entity structure, tax IDs and the chart of accounts
  • Bank and trust accounts with reconciliation set-up
  • Timekeeper rates, classifications and task code sets
  • Pre-bill approval steps and client billing rules
  • LEDES e-billing formats for each corporate client
  • Management and compensation reports the partners use

Questions

M-Files to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in M-Files before the plan is fixed. Documents that have no place in SurePoint Finance Enterprise are exported into folders by client and matter.

Does everything in M-Files have a place in SurePoint Finance Enterprise?

Most of it does on paper. Documents, emails, notes, tasks, custom fields 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise?

Documents, emails, notes, tasks, custom fields 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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.

Moving from M-Files to SurePoint Finance Enterprise?

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

We reply within one business day.