Data migration route
Smokeball to Filevine migration
Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and Filevine 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
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
FilevineCloud- 7 carried
- 6 mapped
What moves
What moves from Smokeball to Filevine
Each row is a kind of record Smokeball holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across and six kinds need mapping.
| 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 placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts hold roles on matters. | Has a placeContact cards, linked to projects. | 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 placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter from Outlook, with attachments linked to the email. | Has a placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldFile notes are called memos. | Has a placeHeld as notes in the activity feed. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldEvents linked to matters, synced with Outlook. | Has a placeDeadlines and calendar events. | 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 place in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust accounts with reconciliation and protected funds. | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Carried with mapping |
| 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 sections and fields per project type. | 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 as Filevine document templates. They are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, and intake forms made in a form builder. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Smokeball.
- Carried with mapping
- Filevine 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
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 Filevine. 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 Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine 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 Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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 Smokeball holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 Filevine as a trial and checked against Smokeball: record counts, trust and debtor 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 Filevine 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. 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Smokeball to Filevine: 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 Filevine?
In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Smokeball have a place in Filevine?
On paper, yes: each kind of record Smokeball holds has a place in Filevine. 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 Smokeball data is loaded into Filevine?
Time entries, billing records, trust ledgers, custom fields, templates and intake records 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 Smokeball and into Filevine
Other destinations from Smokeball
Other systems that move into Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Smokeball to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.