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

Data migration route

Smokeball data to Full data export

Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Smokeball holds and keeps it readable and open to queries.

FromSmokeballDesktop and cloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Notes: Exported in full
  5. Calendar: Exported in full
  6. Tasks: Exported in full
  7. Time and expenses: Exported in full
  8. Billing: Exported in full
  9. Trust money: Exported in full
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Templates: Exported with mapping
  13. Intake: Exported with mapping
ToFull data exportFiles
  • 9 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Smokeball to Full data export

Each row is a kind of record Smokeball holds, whether Full data export has a place for it, and what is planned. On this route nine kinds of record carry across and four kinds need mapping.

Records in Smokeball and their place in Full data export
RecordIn SmokeballIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach has a matter type for an area of law and a jurisdiction; the number is the Internal Reference.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldContacts hold roles on matters.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldFiles and folders inside each matter, with version history and full-text search.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeldSaved to the matter from Outlook, with attachments linked to the email.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesHeldFile notes are called memos.Has a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldEvents linked to matters, synced with Outlook.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks and workflows.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldEntered by hand or captured automatically by AutoTime.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldHas a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust accounts with reconciliation and protected funds.Has a placeA trust transactions table; ledger reports can be kept as PDF beside it.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partFields come from each matter type’s layouts; firm-added fields are confirmed in the analysis.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldA precedent library of forms and templates that fill from the matter.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads, and intake forms made in a form builder.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against Smokeball.
Exported with mapping
Full data export holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Not a new system. A complete copy the firm can query.

Writing Smokeball out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Smokeball as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Smokeball is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Smokeball will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

Smokeball keeps its data in its own cloud, so a move off it starts with getting a full copy out: matter and contact lists, the files in every matter, and the billing and trust reports. Its reports export contacts and matters to CSV. The detail that takes the time is the matter-type fields, which differ from one kind of matter to the next.

  1. Fields belong to the matter type

    Matter details are held in layouts, such as Case Details or Property Details, and the set of layouts depends on the matter type. A family matter and a conveyance have different fields. The extract has to be taken type by type, and each layout mapped to custom fields or a note in the new system.

  2. Internal Reference is the number

    What other systems call a matter number, Smokeball calls the Internal Reference. It can be typed by hand or generated from parts, with a counter that some firms reset each calendar year, and individual matters can be overridden. We test the references for duplicates and gaps before using them as the key that documents are matched on.

  3. Memos, and emails with attachments

    File notes are memos. Emails saved from Outlook sit in the matter with their attachments, and each attachment keeps a link back to the email it arrived on. Most destinations store the email and the attachment as two unrelated files. Both come across, but that link is generally lost unless the attachment stays inside the email file.

  4. Version history stays behind

    Smokeball keeps earlier versions of a file and lets users compare and restore them. A bulk copy of the documents takes the current version of each. If earlier versions of particular documents matter, for instance negotiated contracts, the firm names those matters and the versions are pulled out for them as separate files.

  5. No ledger to move

    There is no general ledger in Smokeball. Billing and trust are inside it, and transactions are passed to a linked accounting package: MYOB or Xero in Australia, QuickBooks Online in the US. So the firm’s books stay where they are. What changes is the feed into them: the new system has to be connected to the same accounts from an agreed date.

More about moving off Smokeball

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Smokeball holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Smokeball holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against Smokeball: record counts, totals where Smokeball holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Smokeball, the export is run a final time and checked again. There is nothing to go live. Smokeball is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Smokeball 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 fromSmokeball
Moving toFull data export

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

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

Structure, permissions and handover

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

Smokeball to Full data export: what firms ask

Can we take our Smokeball matter numbers with us?

Yes in most cases. The Internal Reference is exported with each matter and loaded as the matter number wherever the destination accepts one. If the counter was reset each year, the reference needs its year component to stay unique. We check that before the trial load and report any references used twice.

Do closed matters need to move?

They do not have to. Closed matters can move as full records, as documents only, or stay in the archived copy. The choice turns on how often the firm reopens old files and on its retention obligations. Archive details recorded when a matter was closed are captured in the analysis so they are not lost.

Our office accounts are in a separate accounting package. Does anything happen to them?

The ledger stays in that package. Smokeball has been sending it invoices and payments, and that feed stops at cutover. The new system is connected to the same file from an agreed date, with the account mapping checked on a trial so double posting shows up before go-live. Which system produced each entry is then clear from its date.

Does the copy in Full data export hold trust ledgers from Smokeball?

Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Smokeball as at the export date.

Does everything in Smokeball have a place in Full data export?

On paper, yes: each kind of record Smokeball holds has a place in Full data export. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Smokeball is written out to Full data export?

Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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

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

Moving from Smokeball to Full data export?

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

We reply within one business day.