Data migration route
Smokeball to Litify migration
Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
SmokeballDesktop and cloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
LitifyCloud- 7 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Smokeball to Litify
Each row is a kind of record Smokeball holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach has a matter type for an area of law and a jurisdiction; the number is the Internal Reference. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts hold roles on matters. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles and folders inside each matter, with version history and full-text search. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter from Outlook, with attachments linked to the email. | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldFile notes are called memos. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldEvents linked to matters, synced with Outlook. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and workflows. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered by hand or captured automatically by AutoTime. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust accounts with reconciliation and protected funds. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partFields come from each matter type’s layouts; firm-added fields are confirmed in the analysis. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA precedent library of forms and templates that fill from the matter. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, and intake forms made in a form builder. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Smokeball.
- Carried with mapping
- Litify 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Smokeball has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Smokeball, and kept as the record of what was billed and held.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Smokeball 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 Smokeball is kept running until the checks on Litify are finished.
Where the data is now
Leaving Smokeball
Smokeball keeps its data in its own cloud, so a move off it starts with getting a full copy out: matter and contact lists, the files in every matter, and the billing and trust reports. Its reports export contacts and matters to CSV. The detail that takes the time is the matter-type fields, which differ from one kind of matter to the next.
Fields belong to the matter type
Matter details are held in layouts, such as Case Details or Property Details, and the set of layouts depends on the matter type. A family matter and a conveyance have different fields. The extract has to be taken type by type, and each layout mapped to custom fields or a note in the new system.
Internal Reference is the number
What other systems call a matter number, Smokeball calls the Internal Reference. It can be typed by hand or generated from parts, with a counter that some firms reset each calendar year, and individual matters can be overridden. We test the references for duplicates and gaps before using them as the key that documents are matched on.
Memos, and emails with attachments
File notes are memos. Emails saved from Outlook sit in the matter with their attachments, and each attachment keeps a link back to the email it arrived on. Most destinations store the email and the attachment as two unrelated files. Both come across, but that link is generally lost unless the attachment stays inside the email file.
Version history stays behind
Smokeball keeps earlier versions of a file and lets users compare and restore them. A bulk copy of the documents takes the current version of each. If earlier versions of particular documents matter, for instance negotiated contracts, the firm names those matters and the versions are pulled out for them as separate files.
No ledger to move
There is no general ledger in Smokeball. Billing and trust are inside it, and transactions are passed to a linked accounting package: MYOB or Xero in Australia, QuickBooks Online in the US. So the firm’s books stay where they are. What changes is the feed into them: the new system has to be connected to the same accounts from an agreed date.
Where it is going
Arriving in Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Smokeball and checking each trial against Smokeball.
Analysis
We read what Smokeball holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Smokeball, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Litify as a trial and checked against Smokeball: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Smokeball are frozen for an agreed window, the data is collected a final time and Litify 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 Smokeball as at the cutover date. Smokeball 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 Smokeball 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 Smokeball holds
What is in it, how its records link, and where each piece would sit in Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Smokeball to Litify: what firms ask
Can we take our Smokeball matter numbers with us?
Yes in most cases. The Internal Reference is exported with each matter and loaded as the matter number wherever the destination accepts one. If the counter was reset each year, the reference needs its year component to stay unique. We check that before the trial load and report any references used twice.
Do closed matters need to move?
They do not have to. Closed matters can move as full records, as documents only, or stay in the archived copy. The choice turns on how often the firm reopens old files and on its retention obligations. Archive details recorded when a matter was closed are captured in the analysis so they are not lost.
Our office accounts are in a separate accounting package. Does anything happen to them?
The ledger stays in that package. Smokeball has been sending it invoices and payments, and that feed stops at cutover. The new system is connected to the same file from an agreed date, with the account mapping checked on a trial so double posting shows up before go-live. Which system produced each entry is then clear from its date.
Do trust balances in Smokeball have a place in Litify?
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 Smokeball before the plan is fixed. If Litify 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 Smokeball have a place in Litify?
Most of it does on paper. Notes and trust ledgers 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Smokeball data is loaded into Litify?
Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and trust ledgers 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 Smokeball and into Litify
Other destinations from Smokeball
Other systems that move into Litify
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.
Smokeball and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Smokeball to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.