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

Data migration route

M-Files to Soluno migration

M-Files are a document management system, and Soluno is a cloud accounting and billing system. Only names and any financial records have a place in a set of books, so little of this moves.

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
ToSolunoCloud
  • 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 Soluno

Each row is a kind of record M-Files hold, whether Soluno 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 Soluno
RecordIn M-FilesIn SolunoWhat 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 placeAs files, with number, area of practice, responsible lawyer and billing settings.Carried across
ContactsClients, other parties and referrersHeld in partCustomer and contact object types exist where the vault defines them.Has a placeEach contact is numbered; a file must have a primary contact.Carried 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 confirmedNo matter document store is described; NetDocuments can be linked.Confirmed 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
Soluno 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

Little of this belongs in the accounts.

Soluno is an accounting package. It takes customers, suppliers, invoices and ledger entries, and has no place for documents, case notes, calendars or leads. From M-Files, that usually leaves the contact list, loaded as customers, and any financial records it happens to keep. The table above shows which. This is a small job, and it is better to say so plainly before a firm plans around it.

Loading customers into an accounting system has consequences a contact list elsewhere does not. Every customer can be invoiced, so duplicates and half-complete records turn into billing mistakes. The list is cleaned and matched against the customers already in Soluno before anything is added. The rest of what M-Files hold is exported in open formats and kept as an archive, or moved on a different route to a system built for it.

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

Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.

  1. Numbers for contacts and files

    Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.

  2. Groups before files

    File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.

  3. Periods must be open

    Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.

  4. Closed matters need zero balances

    A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.

  5. Documents live beside it

    Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.

More about moving into Soluno

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Soluno 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 Soluno. 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 Soluno 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 toSoluno

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

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

Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.

Set-up decisions in Soluno

  • Chart of accounts, bank accounts and opening financial periods
  • File, billing and rate groups with their default arrangements
  • Contact and file numbering format, set firm-wide or by contact
  • User groups and what each group may see or do
  • Task and activity codes and each lawyer’s shortcuts
  • Link to NetDocuments or to Actionstep practice management

Questions

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

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 Soluno are exported into folders by client and matter.

Does everything in M-Files have a place in Soluno?

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

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

Moving from M-Files to Soluno?

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

We reply within one business day.