Data migration route
Smokeball to Actionstep migration
Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and Actionstep is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
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 across
- Trust money: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
ActionstepCloud- 10 carried
- 3 mapped
What moves
What moves from Smokeball to Actionstep
Each row is a kind of record Smokeball holds, whether Actionstep has a place for it, and what is planned. On this route ten kinds of record carry across and three 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 placeImported with a matter type, a status and the old number as File Reference. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts hold roles on matters. | Has a placeImported first, then linked to matters through a parties import. | 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 placeFiled in matter folders; not part of the spreadsheet import tool. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter from Outlook, with attachments linked to the email. | Has a placeSaved emails sit on the matter they were filed to. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldFile notes are called memos. | Has a placeThe import tool has a file notes template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldEvents linked to matters, synced with Outlook. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and workflows. | Has a placeThe import tool has a tasks template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered by hand or captured automatically by AutoTime. | Has a placeTime entries and disbursements each have an import template. | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust accounts with reconciliation and protected funds. | Has a placeTrust balances load per matter through the trust accounts import. | Carried across |
| 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 placeData collections are built per matter type before values are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA precedent library of forms and templates that fill from the matter. | Has a placeRebuilt as Actionstep templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, and intake forms made in a form builder. | Has a place | Carried across |
What the plans mean
- Carried across
- Actionstep has a place for this kind of record. It is loaded there and checked against Smokeball.
- Carried with mapping
- Actionstep 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. Smokeball and Actionstep 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 Smokeball’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 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 Actionstep 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 Actionstep
Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.
Matter types before any data
A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.
Old numbers go to File Reference
Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.
Check before anyone edits
The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.
Folders come from the matter type
Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.
Opening balances can be locked
Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live 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 Smokeball holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. 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 Actionstep 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 Actionstep 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 Actionstep. 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 Actionstep
Loaded data is not yet a working system. This is what NewLaw sets up in Actionstep, beyond the migration, so that people can work in it from the first day.
Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.
Set-up decisions in Actionstep
- Matter types, with workflow steps and default document folders
- Participant types and data collections for each matter type
- Document and email templates rebuilt with Actionstep merge fields
- Trust accounts, chart of accounts and the optional Xero link
- System roles and data permissions for each group of staff
- Outlook add-in, divisions and the firm’s billing preferences
Questions
Smokeball to Actionstep: 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 Actionstep?
Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. Balances are loaded by matter and agreed to the trust report from Smokeball as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in Smokeball have a place in Actionstep?
On paper, yes: each kind of record Smokeball holds has a place in Actionstep. 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 Actionstep?
Billing records, 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 Smokeball and into Actionstep
Other destinations from Smokeball
Other systems that move into Actionstep
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 Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from Smokeball to Actionstep?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.