Data migration route
LegalServer to Smokeball migration
LegalServer is a cloud case management system for legal aid 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.
LegalServerCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
SmokeballDesktop and cloud- 9 carried
- 2 mapped
- 3 to confirm
What moves
What moves from LegalServer to Smokeball
Each row is a kind of record LegalServer 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases and matters, with case types configured for each site. | Has a placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and the other people connected with a case. | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored on the case, or linked from SharePoint, Google Shared Drives or Dropbox. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partBuilt-in email, and email sent to a case from Gmail through an integration. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a placeAs memos; not importable on the Bill plan. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments, events, tasks and deadlines; entries can show in Outlook. | Has a placeCalendar events and critical dates; plan limits apply. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeNot importable on the Bill plan. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeeping, used for grant and funder reporting. | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| BillingInvoices, payments and debtor balances | To be confirmedBuilt for free legal services; client 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 balances | To be confirmed | Has a place in partMatter account balances load as opening balances; past transactions are not on the import list. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeNo general ledger; the firm’s books stay in an accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldSites add their own fields, forms and processes without code. | Has a place in partValues need a matching field in the matter type’s layouts. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldBuilt-in document templates; HotDocs, Docassemble and Gavel are integrations. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldConfigurable client intake, with a poverty level assessment and conflict check. | 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 LegalServer.
- 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 LegalServer. 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 LegalServer 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 LegalServer is kept running until the checks on Smokeball are finished.
Where the data is now
Leaving LegalServer
Each agency configures its own intake, case types and fields, so a move off LegalServer starts with that site’s configuration, not with a standard list of tables. The data most at risk is the data a commercial practice system never asks for: eligibility answers, funding codes, outcomes and the time recorded against each grant.
Each site has its own shape
Intake processes, case types and data fields are set up by the agency’s own administrators, often over many years. Two programs on the same product can hold quite different records. The analysis reads this site’s configuration first and lists every field that holds data, including ones no current staff member remembers adding.
Time belongs to funders
Timekeeping exists to show funders what their grant paid for, so entries are tied to grants and funding sources, not to a bill. A practice system records time against a matter for invoicing. The funding link has to be carried as its own field, or grant reports for the period before the move cannot be reproduced.
Documents may live elsewhere
LegalServer can store files itself, or link a case to folders in SharePoint, Google Shared Drives or Dropbox. On a site that uses those integrations the documents are not in the case management system at all. Where the files are is established before anything else, because it decides whether they are moved or simply linked again.
Eligibility and outcome data
Intake assesses a client against the poverty level and runs a conflict check, and outcomes are tracked across cases for reporting. These answers justify the service to an auditor. They are carried as fields where the destination allows, and otherwise as a dated intake summary filed on the case.
Feeds from courts and agencies
Some sites receive court data several times a day, create cases from a county system, or send counselling data to HUD. These connections are part of how the office works. Each is listed with what it sends or receives, and a decision is made on whether it is rebuilt, replaced by manual entry, or retired.
Where it is going
Arriving in Smokeball
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.
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.
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.
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.
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.
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.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what LegalServer 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.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in LegalServer, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Smokeball as a trial and checked against LegalServer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LegalServer are frozen for an agreed window, the data is collected a final time and Smokeball goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in LegalServer as at the cutover date. LegalServer 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 LegalServer 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what LegalServer 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.
- 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
LegalServer to Smokeball: what firms ask
Can a commercial practice system hold legal aid data?
It can hold the cases, people, notes, documents and time. It will not have funding codes, eligibility screening or funder reports unless they are built with custom fields and reports. The analysis sets out which of those can be rebuilt in the chosen system and which reporting would have to be done outside it.
What happens to cases closed years ago?
Closed cases matter in legal aid for conflict checks and for funder audits. Bringing every case means a returning client or an adverse party is still found. If older cases are left out, their names should still be loaded for conflict searching, and the full record stays in the read-only copy.
Our documents are in SharePoint, not in LegalServer. Must they move as well?
Not necessarily. If LegalServer only links to SharePoint, the files are already in the program’s own Microsoft 365. They can stay where they are and be linked from the new system, or be moved into it. The choice depends on how the destination stores documents and is made in the analysis.
Do trust balances in LegalServer have a place in Smokeball?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in LegalServer before the plan is fixed. If Smokeball turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in LegalServer have a place in Smokeball?
Most of it does on paper. Billing records, trust ledgers and the firm’s accounts 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 LegalServer data is loaded into Smokeball?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Billing records, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LegalServer and into Smokeball
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
LegalServer and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from LegalServer 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.