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

Data migration route

CasePeer to Smokeball migration

CasePeer is a cloud case management system for personal injury work, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. Case records move into matters, and time, billing and trust are set up in Smokeball, often from a separate accounts package.

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

What moves

What moves from CasePeer to Smokeball

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

Records in CasePeer and their place in Smokeball
RecordIn CasePeerIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldPersonal injury cases with statutes, status and links to connected cases.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldClients, defendants, insurers, providers and referral sources.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldUnlimited storage, a mail centre for incoming post, and Dropbox or OneDrive links.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 partText and email messages with clients are tied to the case.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including notes written automatically by workflows.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents, statutes and litigation event plans. Syncs to Outlook, Google or iCal.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask manager with workflows triggered by case status, age or client details.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime logging is built in. The product is designed for contingency fee work.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesTo be confirmedClient payments are taken through LawPay. Invoicing was not confirmed.Has a placeInvoices and billed invoice entries are on the import list.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient trust tracking by case. Trust accounting itself runs in a linked package.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 confirmedSold as pre-configured. How far fields can be added was not confirmed.Has a place in partValues need a matching field in the matter type’s layouts.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument automation from case data.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake manager with forms, checklists and conversion reporting.Has a placeLeads are a record type of their own and can be converted to matters.Carried across

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Smokeball brings those two sources together. The case records come from CasePeer. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Smokeball, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Where the data is now

CasePeer holds an injury case in a fixed shape that suits the work: treatment, bills, liens, costs and settlement each have their own place. Leaving it means finding where each of those sits in the destination. A system built for injury work will have most of them. A general system needs fields or record types set up first.

  1. Treatment and medical bills

    Each provider on a case carries treatment, billed amounts and the status of the requests made for records and bills. This is the bulk of the structured data and the part clients ring about. It is mapped provider by provider, and billed totals per case are compared after the trial load, since they feed the demand.

  2. Liens and settlement distribution

    Liens are tracked against the case, and the settlement figures work out fees, costs, lien payments and the client’s net. For settled cases the final distribution is a record the firm must be able to produce later. It is carried as data where the destination can hold it, and otherwise as a saved statement on the case.

  3. Cost requests and accounting

    Staff raise cost requests in CasePeer and the payment itself is made in the accounting package. The cost history on a case therefore depends on that link having been used consistently. Case cost totals are reconciled to the accounting package before cutover, so the amount recovered at settlement is the amount actually spent.

  4. Client trust tracking

    The product tracks client trust money by case. Those balances are compared with the firm’s bank and accounting records before any figure is loaded into a new trust ledger. Because a trust cutover cannot be run again like a document load, it is rehearsed on a full trial load first.

  5. Mail centre and flagged documents

    Incoming post is sorted through a mail centre, and documents can be flagged for review. Items still waiting in that queue at cutover belong to no finished process in the new system. The queue is cleared or listed during the freeze window, so nothing sits unread in the old one.

More about moving off CasePeer

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 CasePeer 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 CasePeer, 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 CasePeer: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in CasePeer 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. CasePeer 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 CasePeer 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 fromCasePeer
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 CasePeer 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

CasePeer to Smokeball: what firms ask

Is CASEpeer the same product as 8am CasePeer?

Yes. The product was written CASEpeer for years, and its owner now brands it 8am CasePeer alongside 8am MyCase, LawPay and DocketWise. Nothing about what the system stores changed with the rename. A firm that knows it under any of these names is using the same personal injury system.

Can our treatment and lien data go into a general practice system?

It can, but someone has to build the place for it first. General systems hold parties and documents well and usually have nothing for provider visits, bills and lien balances. Custom fields or record types are set up at the analysis stage, and where the destination cannot hold a table of bills, a schedule is saved to the case.

What happens to leads that never became cases?

Leads in the intake manager are separate from cases. Declined and unconverted leads can move to the new system’s intake module if it has one, be loaded as contacts with a note, or be left in an export. Referral sources are kept in every option, because the marketing reports depend on them.

Do trust balances in CasePeer 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 CasePeer have a place in Smokeball?

Most of it does on paper. Billing records 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 CasePeer data is loaded into Smokeball?

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

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

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