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

Data migration route

Prevail to Smokeball migration

Prevail is a server-based case management system, 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.

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

What moves

What moves from Prevail to Smokeball

Each row is a kind of record Prevail 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 three kinds are confirmed in the analysis.

Records in Prevail and their place in Smokeball
RecordIn PrevailIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with related parties. Stages are configured by the firm.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldA central record for clients, providers, counsel, courts and experts.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldLetters and forms generated from the matter, plus evidence management.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 partAn Outlook integration is offered. What is stored per matter was not confirmed.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
CalendarAppointments, court dates and deadlinesHeldTasks and calendaring.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks, including those set by Process Builder stages.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeld in partListed by the vendor under time, billing and trust. Detail is not published.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeld in partA matter ledger records financial and cost activity.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesHeld in partListed by the vendor under time, billing and trust. Detail is not published.Has a place in partMatter account balances load as opening balances; past transactions are not on the import list.Carried with mapping
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeNo general ledger; the firm’s books stay in an accounting package.Confirmed in the analysis
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 automationHeldMatter-based letters and forms.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldA configurable intake questionnaire and lead management.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 Prevail.
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 Prevail. 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.

Prevail 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

Prevail is used for claimant work in which each matter follows set stages and produces many letters and forms. The data is on a Windows server that either the firm or the vendor runs. Planning starts with where that server is, and with which practice areas the firm actually uses the program for, since each has its own fields.

  1. Stages set by the firm

    Application, reconsideration, hearing and review stages are configured by each firm, and the Process Builder attaches tasks, appointments and document actions to them. The stage a matter has reached is the fact staff look for first. That list is mapped before anything else, and every open matter is checked to arrive at the right stage.

  2. Social Security detail

    Disability matters carry claim identifiers, representation details, work history, medical providers and the status of each evidence request. A destination not built for this work needs custom fields for most of it. Evidence requests still outstanding are loaded as tasks against the provider, so the follow-up continues without a gap.

  3. Own server or vendor hosting

    The program can run on the firm’s Windows server or in the vendor’s managed hosting. How the data is reached differs between the two. On the firm’s own server a backup is taken locally. In the hosted service, how a copy is provided is arranged with the firm at the start of the analysis.

  4. Generated letters and forms

    Letters and forms are produced from matter data and saved or printed. Over years this becomes the larger part of the file. Each document is extracted with its matter and date. The templates behind them use Prevail’s own merge fields and are rebuilt in the destination, most used first.

  5. The matter ledger

    Costs and financial activity are recorded on a ledger connected to the matter. For practices paid on the outcome, the figures that count are costs advanced and fees received. Those are reconciled against the accounting records before loading, and where the destination has no ledger the balance is carried as a figure with a note.

More about moving off Prevail

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

  4. Cutover

    Changes in Prevail 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. Prevail 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 Prevail 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 fromPrevail
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 Prevail 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

Prevail to Smokeball: what firms ask

Is Prevail a desktop program or a cloud system?

It is Windows software that works against a server. Some firms run that server themselves and others use the vendor’s managed hosting, where staff connect remotely. Both hold the same kind of data. The difference for a migration is only in how a copy of the database and documents is obtained.

Can a general practice system cope with Social Security disability matters?

It needs building out. Claim numbers, hearing offices, appeal stages and evidence tracking are not standard fields in a general system. They are added as custom fields with a workflow per stage. The analysis shows the firm a sample disability matter laid out in the destination before it decides.

Will the client portal carry over?

The portal belongs to Prevail, so client logins do not transfer as a working portal. Messages and documents exchanged through it can be filed to each matter if they can be extracted. If the destination has its own portal, clients are invited to it at go-live with a short notice explaining the change.

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

Most of it does on paper. Notes, the firm’s accounts 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 Prevail data is loaded into Smokeball?

Trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Notes, the firm’s accounts 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

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

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