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

Data migration route

LawCloud to Smokeball migration

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

FromLawCloudCloud
  1. Matters: Carried across
  2. Documents: Carried across
  3. Emails: Carried across
  4. Notes: Carried across
  5. Time and expenses: Carried across
  6. Billing: Carried across
  7. Trust money: Carried with mapping
  8. Contacts: Confirmed in the analysis
  9. Calendar: 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
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Smokeball
  • 6 carried
  • 1 mapped
  • 6 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawCloud to Smokeball

Each row is a kind of record LawCloud 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, one kind has no place in Smokeball and is archived and six kinds are confirmed in the analysis.

Records in LawCloud and their place in Smokeball
RecordIn LawCloudIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOrganised as cases, with every activity logged to the case record.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeMatter roles import on the Grow and Prosper+ plans only.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldDocuments are stored and searched within the case.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are logged to the case record.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeld in partPhone calls are logged against the case.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events and critical dates; plan limits apply.Confirmed in the analysis
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 unbilledHeldBuilt-in time recording.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeldHas a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesHeldClient accounting under Law Society of Scotland and SRA accounts rules.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 payablesHeldSolicitors’ accounts software in the same system as case management.No placeNo general ledger; the firm’s books stay in an accounting package.Kept as a readable archive
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 LawCloud.
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.
Kept as a readable archive
Smokeball has no place for it. It is exported in a format that opens without LawCloud and handed to the firm as a read-only archive.

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. LawCloud and Smokeball 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 LawCloud’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 LawCloud 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 LawCloud is kept running until the checks on Smokeball are finished.

Where the data is now

A LawCloud firm does not hold its own database: LawWare hosts it. Leaving starts with a request for a copy of the data and documents, and with working out which edition the firm is actually on. Because legal accounts sit in the same system as the cases, the client ledgers and the case files leave together and have to agree with each other on arrival.

  1. Hosted LawWare, by another name

    LawCloud is LawWare’s Enterprise edition run from LawWare’s hosting. Staff may call it LawWare, LawCloud or just the case management system. We confirm the edition and version with the vendor at the start, because LawWare describes New LawWare as a complete redesign of version 4, and the extraction has to match the version in use.

  2. The case record logs everything

    Every phone call, document, email and time entry is written to the case record as an activity. That log is the running history of the file. Systems that keep documents, notes and time in separate lists can hold each item, but the single history is rebuilt only if entries keep their dates and authors.

  3. Scottish accounts rules

    The accounts software is written for the Law Society of Scotland’s accounts rules, including real-time monitoring of surpluses, as well as the rules south of the border. A destination must cope with the rules the firm practises under. For Scottish firms that is the first thing to confirm with any replacement.

  4. Outsourced cashiering

    LawWare also runs an outsourced legal cashiering service, and some firms have their books kept that way. If so, the people who know the ledgers are outside the firm. They need to be part of the cutover plan: closing the period, producing the final reconciliation and confirming the balances that are loaded.

More about moving off LawCloud

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

  4. Cutover

    Changes in LawCloud 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. LawCloud 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 LawCloud 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 fromLawCloud
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 LawCloud 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

LawCloud to Smokeball: what firms ask

Who gives us our data if LawWare hosts it?

The firm asks LawWare for it. We set out what is needed: the database, the document store and the closing accounts reports, taken at the same moment. How the copy is supplied and how long it takes are confirmed with LawWare during the analysis, and the cutover date is set around that answer.

Is LawCloud the same thing as LawWare?

For migration purposes, yes. LawCloud was the name for LawWare’s hosted service, and the software behind it is LawWare. What matters is the version: the older version 4 or the redesigned New LawWare. The firm’s support contact can confirm that, and we plan the extraction around it.

Do trust balances in LawCloud 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.

What happens to records Smokeball has no place for?

On this route that is the firm’s accounts. They are exported from LawCloud in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

Trust ledgers are carried with mapping, so each mapping is agreed with you first. Contacts, calendar entries, 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

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

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