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

Data migration route

Smokeball to SimpleLaw migration

Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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

What moves

What moves from Smokeball to SimpleLaw

Each row is a kind of record Smokeball holds, whether SimpleLaw has a place for it, and what is planned. On this route eight kinds of record carry across, four kinds need mapping and one kind is confirmed in the analysis.

Records in Smokeball and their place in SimpleLaw
RecordIn SmokeballIn SimpleLawWhat 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 placeCarried across
ContactsClients, other parties and referrersHeldContacts hold roles on matters.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles and folders inside each matter, with version history and full-text search.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to the matter from Outlook, with attachments linked to the email.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldFile notes are called memos.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldEvents linked to matters, synced with Outlook.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks and workflows.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldEntered by hand or captured automatically by AutoTime.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust accounts with reconciliation and protected funds.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
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 placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldA precedent library of forms and templates that fill from the matter.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads, and intake forms made in a form builder.Has a placeLeads and intake forms.Carried across

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Smokeball.
Carried with mapping
SimpleLaw 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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Smokeball and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Smokeball’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

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

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Smokeball holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Smokeball, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into SimpleLaw as a trial and checked against Smokeball: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Smokeball are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Smokeball 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 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Smokeball to SimpleLaw: 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.

Do trust balances in Smokeball have a place in SimpleLaw?

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Smokeball have a place in SimpleLaw?

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

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

Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

Moving from Smokeball to SimpleLaw?

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

We reply within one business day.