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

Data migration route

eBillity to Smokeball migration

eBillity is a cloud accounting and billing system, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. The financial records lead: balances and open items move, and the matters in Smokeball are built around them.

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

What moves

What moves from eBillity to Smokeball

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

Records in eBillity and their place in Smokeball
RecordIn eBillityIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldLawBillity tracks time and expenses against clients and matters.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeld in partClients and their billing details.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeld in partReceipt images attached to expense entries and invoices.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
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeAs memos; not importable on the Bill plan.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendar entries can be converted into time entries.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeNot importable on the Bill plan.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimers, weekly timesheets and expenses, approved before billing.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeldInvoices, LEDES billing and online payments through LawPay or Stripe.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesHeld in partIn LawBillity only: client trust funds managed beside billing.Has a place in partMatter account balances load as opening balances; past transactions are not on the import list.Carried with mapping
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 automationTo be confirmedHas a placeFirm precedents are rebuilt as Smokeball templates.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads are a record type of their own and can be converted to matters.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 eBillity.
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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in eBillity needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of eBillity. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Smokeball are agreed to the trial balance and aged debtors from eBillity as at the cutover date, and that load is rehearsed before it is done for real.

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

Where the data is now

A LawBillity account holds the firm’s time, expenses, invoices and, where it was used, trust balances, under a list of clients and matters. It does not hold the firm’s books, which are in QuickBooks or another package beside it. A move is mostly about carrying unbilled time and unpaid invoices across correctly and keeping the link to the accounting package intact.

  1. Which eBillity product

    The company sells general Time Tracker plans as well as LawBillity, and a firm may be on either. Those general plans track time for payroll, projects and client invoicing. Only LawBillity is described as having matters, UTBMS codes and trust, so the plan decides what records exist to move.

  2. Billing lives apart from books

    Invoices and payments are raised in LawBillity and synchronised to QuickBooks. Two systems therefore hold a version of each invoice. Before cutover the two are agreed to each other, so the receivables loaded into the new system match what the accounting package already says the firm is owed.

  3. Receipts on expense entries

    Staff can photograph a receipt and attach it to an expense entry, and the image can be attached to the invoice. These are easy to overlook because the product is not thought of as holding documents. They are collected with their expense entries so the evidence for a disbursement is not lost.

  4. Trust in LawBillity

    LawBillity manages client trust funds alongside billing. Each client’s trust balance is listed with its history and agreed to the trust bank statement at the cutover date. If the firm also tracked trust in QuickBooks, the two records are compared first and any difference is explained before either is loaded.

More about moving off eBillity

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.

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

  1. Analysis

    We read what eBillity holds and how its records link, then agree with you, field by field, where each piece will sit in Smokeball. 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 eBillity, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in eBillity are frozen for an agreed window, the data is collected a final time and Smokeball 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. eBillity 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 eBillity 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 fromeBillity
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 eBillity 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

eBillity to Smokeball: what firms ask

Does our unbilled time come across?

Time and expense entries that have not been invoiced are read with their date, person, matter, service item, description and rate. They are loaded as unbilled entries where the new system accepts them. A final billing round in LawBillity before cutover means less work in progress has to be carried.

We also use QuickBooks with it. Does that change?

QuickBooks stays where it is unless the firm is replacing it too. What changes is the connection: the new practice system has to post invoices and payments to the same QuickBooks company in place of LawBillity. The switch is timed so no invoice is posted twice or missed.

Can we keep our invoice numbers?

Invoice numbers belong to the invoice record, and where the LawBillity data supplies them they are kept on each historical invoice brought across. The new system’s next number is then set above the highest LawBillity number so the sequence continues, provided the destination allows the starting number to be set. That is checked in the analysis.

Do trust balances in eBillity have a place in Smokeball?

In part. Matter account balances load as opening balances; past transactions are not on the import list. The analysis sets out which trust records have a place in Smokeball 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 eBillity have a place in Smokeball?

Most of it does on paper. Emails, notes, tasks, custom fields, templates and intake records 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 eBillity data is loaded into Smokeball?

Trust ledgers are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, custom fields, templates and intake records 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

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

Moving from eBillity 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.