Data migration route
INSZoom to Smokeball migration
INSZoom is a cloud case management system for immigration work, 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.
INSZoomCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Calendar: Carried across
- Billing: Carried across
- Intake: Carried across
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SmokeballDesktop and cloud- 7 carried
- 1 mapped
- 5 to confirm
What moves
What moves from INSZoom to Smokeball
Each row is a kind of record INSZoom holds, whether Smokeball has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldImmigration cases with phases and milestones, for US, Canadian and other countries’ processes. | Has a placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | HeldPrivate individuals and corporate clients; HR contacts can have portal access (Enterprise). | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDigital case files, with documents collected from clients. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partTemplated emails and reminders are sent from the system in the Enterprise edition. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs memos; not importable on the Bill plan. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partDeadline and expiry notifications; a general appointment calendar was not confirmed. | Has a placeCalendar events and critical dates; plan limits apply. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeNot importable on the Bill plan. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeUnbilled time, fee and expense entries, with activity codes. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldInvoice generation, with integrations to QuickBooks Online, LawPay and Authorize.net. | Has a placeInvoices and billed invoice entries are on the import list. | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partMatter account balances load as opening balances; past transactions are not on the import list. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partValues need a matching field in the matter type’s layouts. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldForms library, digital questionnaires and email templates. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partAdvance Case Request lets corporate clients start a case (Enterprise edition). | 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 INSZoom.
- 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.
- 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
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 INSZoom. 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of INSZoom 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 INSZoom is kept running until the checks on Smokeball are finished.
Where the data is now
Leaving INSZoom
INSZoom is built for volume immigration work, much of it for employers. A move off it has to keep three things joined up: the company that sponsors, the employee the case is about, and the history of each case’s phases. Documents and invoices are the simple part. The forms data and the reporting that corporate clients receive take the planning.
Employers, HR contacts and employees
A corporate client has HR contacts who log in, and many employees who each have their own cases. That is three levels where most practice systems have a client and a matter. The analysis decides whether the employer becomes the client with one matter per employee case, and where the employee’s own details are then kept.
Cases outside the United States
The system handles Canadian and other countries’ immigration processes as well as US ones, each with different forms and steps. A destination set up around USCIS case types will not have a place for a Canadian work permit. Every case type in use is listed by country before mapping starts, with a count against each.
Phase and milestone dates
Cases are tracked through phases and milestones so that turnaround can be reported to corporate clients against a service level. Those dates are history a client may ask about later. They need date fields of their own in the new system, or a dated summary on each matter if it has none.
Questionnaire answers behind forms
Clients complete digital questionnaires and the answers fill the forms library. Receipt details from USCIS notices are also read into the case. Completed forms are carried as documents. The answers themselves are mapped field by field, and the ones with no destination are listed for the firm instead of being dropped quietly.
Invoices here, ledger elsewhere
Invoices are raised in INSZoom and can be passed to QuickBooks Online, with payments through LawPay or Authorize.net. So the invoice history is in one place and the firm’s books in another. Debtor balances are taken from both and compared before cutover, and any difference is explained while the old system can still be queried.
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 INSZoom 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 INSZoom, 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 INSZoom: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in INSZoom 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 INSZoom as at the cutover date. INSZoom 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 INSZoom 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 INSZoom 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
INSZoom to Smokeball: what firms ask
Our corporate clients use the HR portal. What do they lose?
Their logins end with the old system. What they saw there, such as case status, documents and reports on their employees, has to be offered another way. If the destination has a client portal, HR contacts are invited to it after cutover. If not, the firm agrees a reporting routine with each client before go-live.
Can cases in progress be moved without losing their place?
Yes, provided the current phase and its dates are mapped. Each open case is loaded with its status, the milestones already reached and the deadlines still ahead. In the trial load a sample of open cases is opened side by side with INSZoom to confirm the next step and its due date agree.
Does our forms library move?
No. The library belongs to the product and is kept current by Mitratech. What belongs to the firm is each client’s data and each completed form. If the destination is another immigration system it has its own library. If it is a general practice system, form preparation needs a separate tool.
Do trust balances in INSZoom have a place in Smokeball?
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 INSZoom before the plan is fixed. If Smokeball 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 INSZoom have a place in Smokeball?
Most of it does on paper. Notes, tasks, time entries, trust ledgers and custom fields 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 Smokeball is kept as a readable archive, and you see which before the move.
What has to be decided before INSZoom data is loaded into Smokeball?
Templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, time entries, trust ledgers and custom fields 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 INSZoom and 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.
INSZoom and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from INSZoom 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.