Data migration route
Zola Suite to Smokeball migration
Zola Suite 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.
Zola SuiteCloud- 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
- Billing: Carried across
- Intake: Carried across
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
SmokeballDesktop and cloud- Firm accounts: Kept as a readable archive
- 10 carried
- 3 mapped
- 1 archived
What moves
What moves from Zola Suite to Smokeball
Each row is a kind of record Zola Suite holds, whether Smokeball has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in Smokeball and is archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | 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 | HeldAny file type, indexed for search, with a new version saved on each edit. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | HeldAn email client is part of the product and files messages against matters. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | Held | Has a placeAs memos; not importable on the Bill plan. | Carried across |
| CalendarAppointments, court dates and deadlines | Held | 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 | Held | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| BillingInvoices, payments and debtor balances | HeldOne matter can be split between several billing clients, each with its own invoice. | Has a placeInvoices and billed invoice entries are on the import list. | Carried across |
| Trust moneyTrust or client account ledgers and balances | Held | 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 payables | HeldVendor bills, cheque writing and financial statements sit in the same system. | 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 itself | Held | Has a place in partValues need a matching field in the matter type’s layouts. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads and intake forms are handled in the built-in CRM. | 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 Zola Suite.
- 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.
- Kept as a readable archive
- Smokeball has no place for it. It is exported in a format that opens without Zola Suite 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. Zola Suite 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 Zola Suite’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 Zola Suite 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 Zola Suite is kept running until the checks on Smokeball are finished.
Where the data is now
Leaving Zola Suite
Nobody moves off Zola Suite as such any more. The records are in CARET Legal, and that is the system the data is taken from. Firms that joined in the Zola years tend to have the longest history in it, with billing arrangements and document links set up long ago that current staff may not know about. Finding those early is most of the analysis.
One account, two names
Staff who say Zola and staff who say CARET are talking about the same login. The vendor announced a new name, not a new system, so there should be no older archive to hunt for. Old bookmarks, saved report names and procedure documents may still carry the Zola name, and it helps to list them before cutover.
Split billing on a matter
A single matter can be billed to several clients at set percentages, with fees and costs split separately and a distinct invoice number for each payer. Many systems expect one bill-to client per matter. Split matters are listed in the analysis, and the firm chooses between sub-matters and a manual split in the destination.
Payables and cheques
Vendor bills, outgoing payments and cheque runs are recorded here, along with the costs passed on to matters. When the firm leaves, its unpaid vendor bills and its vendor list need a home in whatever accounting package comes next. That list is reconciled to the payables report on the day of the freeze.
Worldox or NetDocuments links
Some firms never used the built-in document store. They linked each matter to a Worldox cabinet or a NetDocuments workspace and worked from there. Those documents are not in the practice management database at all. The analysis records which store each matter points to, so no folder is assumed to be empty when it is only held elsewhere.
Every edit kept as a version
Editing a Word document inside the product saves a new version each time, and any earlier one can be restored. A long-running matter may hold dozens of versions of one agreement. The firm decides whether all of them move or only the current one, and the document count in the trial load is checked against that decision.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Zola Suite 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 Zola Suite, 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 Zola Suite: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Zola Suite 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. Zola Suite 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 Zola Suite 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 Zola Suite 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
Zola Suite to Smokeball: what firms ask
Is Zola Suite still available?
Not under that name. The vendor renamed it CARET Legal after AbacusNext became CARET, and the Zola Suite web address now leads to the CARET Legal site. It was presented as a rebrand, so a firm that never left is simply using CARET Legal.
Our invoices go back to when we started on Zola. Can the full billing history move?
It depends on what the destination will accept. Some systems take historic invoices and payments as records. Others take only open balances, with the old invoices attached as PDFs. Split-billed matters need the closest look, since each payer has its own invoice number.
Do we plan the move as Zola Suite or as CARET Legal?
As CARET Legal, because that is what the firm logs into and what the vendor supports. The planning is the same either way. One extra step for a long-standing Zola firm is checking for features switched on years ago, such as split billing or a Worldox link.
Do trust balances in Zola Suite 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 Zola Suite 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 Zola Suite data is loaded into Smokeball?
Trust ledgers, 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 Zola Suite and into Smokeball
Other destinations from Zola Suite
Other systems that move 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.
Zola Suite and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from Zola Suite 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.