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

Data migration route

Document Locator to Smokeball migration

Document Locator is a server-based 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.

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

What moves

What moves from Document Locator to Smokeball

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

Records in Document Locator and their place in Smokeball
RecordIn Document LocatorIn SmokeballWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn repository folders, with automatic versions, profiles and an audit log.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments can be captured and managed with the documents.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeAs memos; not importable on the Bill plan.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflow and approval steps routed to people.Has a placeNot importable on the Bill plan.Carried across
Custom fieldsFields and record types the firm added itselfHeldMetadata is applied through profiles the administrator defines.Has a place in partValues need a matching field in the matter type’s layouts.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeFirm precedents are rebuilt as Smokeball templates.Confirmed in the analysis

What the plans mean

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

Document Locator runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Smokeball is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Because Document Locator presents itself as folders in Windows, people assume the documents can be dragged out like files on a drive. They are in a SQL Server repository. A copy made that way should not be expected to bring versions, profile values or permissions with it. A planned extraction reads the repository for those, and for check-out state as well.

  1. A repository, not a share

    The folder tree users see is drawn from a Microsoft SQL Server repository. On-premises, that database is on the firm’s server and can be backed up and read. In the hosted service it is on Azure and access is arranged with ColumbiaSoft. Which of the two applies shapes how the work begins.

  2. Folders stand in for matters

    There is no client or matter record, so firms build the equivalent with a folder convention, sometimes created automatically by a project-folder rule. The convention is read off the tree and tested: how many top-level folders match a client in the practice management system, and how many are something else.

  3. Version numbers and notes

    Every check-in adds a version with an incrementing number, users can add a version note, and prior versions can be promoted. For controlled documents such as policies and precedents, that history is the point of the system. The firm decides folder by folder whether history comes across or only the current version.

  4. Workflow and required reading

    Approvals in progress, review reminders and acknowledgements that staff have read a policy are records of process. A legal document system will usually have nowhere to put them. Reports are run from Document Locator before cutover and saved as documents, so the evidence is kept even though the workflow is not.

More about moving off Document Locator

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 Document Locator 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 Document Locator: 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 Document Locator, a final pass over a weekend picks up what changed since the trial. Document Locator 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 Document Locator 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 fromDocument Locator
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 Document Locator 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

Document Locator to Smokeball: what firms ask

Can we simply copy the folders out through Windows?

It will produce files, and for a small set that may be all that is needed. It should not be relied on for a whole repository, because versions, profile metadata, permissions and audit history are in the database. The analysis establishes what the repository records about a document beyond the file itself.

How do documents get matched to matters when there is no matter record?

By the folder path or a profile field, whichever the firm used consistently. A matter list from the practice management system is matched against folder names, and the matches, near-matches and orphans are reported. Near-matches are confirmed by someone at the firm who knows the files.

Do documents from Document Locator 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 Document Locator have a place in Smokeball?

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

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

Custom fields are carried with mapping, so each mapping is agreed with you first. 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

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

Moving from Document Locator 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.