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

Data migration route

Docrio to Smokeball migration

Docrio is a cloud document management system, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromDocrioCloud
  1. Documents: Carried across
  2. Templates: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Tasks: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
ToSmokeballDesktop and cloud
  • 1 carried
  • 1 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Docrio to Smokeball

Each row is a kind of record Docrio holds, whether Smokeball has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and three kinds are confirmed in the analysis.

Records in Docrio and their place in Smokeball
RecordIn DocrioIn SmokeballWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiled against Litify matters, with tags and editable file information.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeKept in the matter with other files.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTasks can be raised against a document; they are Litify records.Has a placeNot importable on the Bill plan.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partValues need a matching field in the matter type’s layouts.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation templates with merge fields and conditional logic.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping

What the plans mean

Carried across
Smokeball has a place for this kind of record. It is loaded there and checked against Docrio.
Carried with mapping
Smokeball 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 Docrio to Smokeball is a translation from one to the other, and it depends on the client and matter numbers in Docrio matching matters that exist in Smokeball. 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.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Docrio 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 Docrio is kept running until the checks on Smokeball are finished.

Where the data is now

Docrio cannot be separated from the Litify system it sits in. Each file is tied to a Litify record, and that record supplies the matter number, client and case type. Leaving it means extracting the files together with the identifiers of the records they hang from. Usually it happens as part of moving the whole Litify system, not the documents alone.

  1. Files hang off Litify records

    A document’s context is the record it was saved to, normally a matter. That relationship is how a file finds its matter in the destination. Keeping the record identifier with every file is what allows it to be joined to the matter export and filed under the right matter.

  2. Folders and tags by case type

    Litify firms normally set a standard folder structure for each case type and add tags on top. The structure for a motor vehicle claim differs from the one for a mass tort. Each case type’s folder set is mapped separately, and tags become document categories or are written into the name.

  3. Templates do not travel

    Generation templates read fields from Litify by name. In another system those fields are called something else, or do not exist. The documents already generated move as ordinary files. The templates themselves are rebuilt in the destination’s own automation, starting with the ones the firm uses most.

  4. Confirm where files are stored

    How Docrio stores file content, and the route for exporting it in bulk, is confirmed with the firm’s Litify administrator at the start. Access is given in whatever way the firm decides. Volumes in injury practices are large, with medical records and video, so transfer time is part of the plan.

More about moving off Docrio

Where it is going

Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.

  1. Every matter needs a type

    Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.

  2. The plan decides what loads

    Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.

  3. Leave auto-numbering until after

    Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.

  4. Documents arrive by folder

    Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.

  5. An opening balance per matter

    Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.

More about moving into Smokeball

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Smokeball on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Docrio holds and how it is organised, then agree with you where each kind of record will sit in Smokeball. 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 Smokeball and checked against Docrio: 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 Docrio, a final pass over a weekend picks up what changed since the trial. Docrio is 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 Docrio 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 fromDocrio
Moving toSmokeball

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 Docrio holds

    What is in it, how its records link, and where each piece would sit in Smokeball. 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 Smokeball

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

A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.

Set-up decisions in Smokeball

  • Matter types in use, with default document folders for each
  • Internal Reference format and the starting number for new matters
  • Trust account details and the link to the accounting package
  • Staff roles and permissions, including who sees billing and trust
  • Firm precedents and letterhead rebuilt as Smokeball templates
  • Desktop app, Word and Outlook add-ins on every PC

Questions

Docrio to Smokeball: what firms ask

We are leaving Litify. Are our documents part of that move?

They should be scoped explicitly. A matter export on its own should not be assumed to contain the documents, and the files may come out by a different route from the Litify data. The plan covers both and joins them on the matter, and document counts are checked per matter after the trial load.

Can we keep Litify and move only the documents to iManage or NetDocuments?

Litify publishes integrations with both, so that arrangement exists. The existing files are then moved from Docrio into workspaces that match the Litify matters, and new documents are saved through the integration. The matter number is the join, so it has to be identical on both sides before the load.

Do documents from Docrio keep their folders and dates in Smokeball?

Smokeball stores documents. Files and folders import into a matter with the folder structure kept. 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 Docrio have a place in Smokeball?

Most of it does on paper. Emails, tasks and custom fields 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 Smokeball is kept as a readable archive, and you see which before the move.

What has to be decided before Docrio data is loaded into Smokeball?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, tasks and custom fields 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

Docrio and Smokeball are the names and marks of their owners, used here only to identify the two systems.

Moving from Docrio to Smokeball?

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

We reply within one business day.