Data migration route
PracticeMaster to Smokeball migration
PracticeMaster 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.
PracticeMasterServer- 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
SmokeballDesktop and cloud- 9 carried
- 2 mapped
What moves
What moves from PracticeMaster to Smokeball
Each row is a kind of record PracticeMaster holds, whether Smokeball has a place for it, and what is planned. On this route nine kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient file mirrored with Tabs3 Billing, one record per Client ID. | Has a placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocument Management records link files to a client or contact, with check-out and versions. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail records in the Journal, created through the Outlook integration. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNote, phone call and research records in the Journal. | Has a placeAs memos; not importable on the Bill plan. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldFirm-wide calendar with Outlook integration and calendar plan templates. | Has a placeCalendar events and critical dates; plan limits apply. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and reminders on the calendar. | Has a placeNot importable on the Bill plan. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimer records and fees that pass to Tabs3 Billing. | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldAreas of Practice with the firm’s own files and fields. | Has a place in partValues need a matching field in the matter type’s layouts. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly with Word or HotDocs, WorkFlows and calendar plan templates. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partTabs3 CRM handles leads and intake and passes them to PracticeMaster. | 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 PracticeMaster.
- 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.
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 PracticeMaster. 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.
PracticeMaster 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
Leaving PracticeMaster
PracticeMaster is the part of Tabs3 that looks most like other practice systems, and the part firms have customised most. Contacts, calendar and journal records move in a familiar way. The detail is in the Areas of Practice the firm built, the documents it linked, and the WorkFlows it depends on, none of which have the same shape in another product.
Areas of Practice are tables
Each Area of Practice has its own files, and firms add files and fields through File Maintenance. A probate area might hold assets and heirs, a family area children and hearings. These can hold many rows for one matter. Every file is listed with its row counts, and each needs a home or a decision.
The Journal mixes record types
Timer records, phone calls, emails, research and notes are all stored in one Journal file, told apart by a record type. Destinations usually split those into time entries, emails and file notes. Journal records are sorted by type on the way out, so a timer record already billed is not loaded a second time as a note.
Documents are linked, with versions
The Document Management file links documents to a client or contact, with check-out, check-in and versions. Each record is only the link, and the document is a file on the firm’s storage. PracticeMaster has its own verify function for these links, and it is run before extraction so broken ones are known.
Template paths by practice area
Document assembly templates sit in a Template Path for each Area of Practice, by default a DOCS folder under that area, and may be Word or HotDocs templates. Their merge codes refer to PracticeMaster fields. Templates are rebuilt against the new system’s fields, starting with the ones produced most often.
WorkFlows and calendar plans
WorkFlows fire when records are added or changed, and calendar plan templates lay down a series of dated events. Events already created come across as calendar entries. The automation itself is described and rebuilt with the destination’s own tools, because rules do not transfer between products.
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 PracticeMaster 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 PracticeMaster, 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 PracticeMaster: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in PracticeMaster 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 PracticeMaster as at the cutover date. PracticeMaster 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 PracticeMaster 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 PracticeMaster 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
PracticeMaster to Smokeball: what firms ask
Do emails saved from Outlook come across?
Emails saved through the Outlook integration become journal records on the client. They are loaded to the matter as emails where the destination has an email record, otherwise as dated notes with the message saved as a file.
We want to keep PracticeMaster and replace billing. Is that possible?
The two are tied by mirrored client files and only integrate when installed together. Replacing Billing alone breaks the flow of fees from PracticeMaster. If the plan is to split them, the analysis sets out the manual steps that would stand in for the link, and what they cost in staff time.
What happens to conflict searching?
Conflict searching in PracticeMaster reads the fields the firm marked for it, across clients, contacts and linked documents. After the move, searches run in the new system over the migrated contacts and matters. Names that lived only in free text or old documents are worth a check, since they may not be indexed the same way.
Do documents from PracticeMaster keep their folders and dates in Smokeball?
Smokeball stores documents. Files and folders import into a matter with the folder structure kept. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in PracticeMaster have a place in Smokeball?
On paper, yes: each kind of record PracticeMaster holds has a place in Smokeball. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before PracticeMaster data is loaded into Smokeball?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from PracticeMaster and into Smokeball
Other destinations from PracticeMaster
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.
PracticeMaster and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from PracticeMaster 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.