Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Mitratech CaseCloud to Smokeball migration

Mitratech CaseCloud 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.

FromMitratech CaseCloudCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried across
  9. Billing: Carried across
  10. Intake: Carried across
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Trust money: Confirmed in the analysis
ToSmokeballDesktop and cloud
  • 10 carried
  • 2 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mitratech CaseCloud to Smokeball

Each row is a kind of record Mitratech CaseCloud holds, whether Smokeball has a place for it, and what is planned. On this route ten kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.

Records in Mitratech CaseCloud and their place in Smokeball
RecordIn Mitratech CaseCloudIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, each with a stage, a status and its participants.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldAccounts and contacts in Salesforce, attached to matters by participant role.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldRelated Files on the matter, or an integrated document system.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail can be sent from a matter. Filing from a mailbox needs the email integration.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeldMatter comments.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesHeldMatter Calendar. CalendarRules is listed for court rules dates.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask checklists and activity plans with dependencies.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimekeepers, rates, UTBMS codes and batch time entry.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeld in partBillings are generated from time, expenses and fee arrangements.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas 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 itselfHeldFields can be added to matters, participants and time layouts.Has a place in partValues need a matching field in the matter type’s layouts.Carried with mapping
TemplatesPrecedents, document templates and automationHeldAdvoDoc templates, budget templates and activity plan templates.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes and intake forms with a convert-to-matter action.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 Mitratech CaseCloud.
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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Mitratech CaseCloud 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 Mitratech CaseCloud’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 Mitratech CaseCloud 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 Mitratech CaseCloud is kept running until the checks on Smokeball are finished.

Where the data is now

CaseCloud data is Salesforce data, so leaving it starts with the org and not with an export button. What has to be established is which of the vendor’s applications the firm installed, how far the administrator customised them, and whether spend management records for outside counsel are in scope as well as the firm’s own matters.

  1. Three applications, one org

    Matter Management, Spend Management and Access Control are separate packages in the same org. A law firm may use only the first. A legal department may hold invoices from outside counsel in the second. Scope is set package by package, so nothing is extracted that the firm never used and nothing in use is missed.

  2. Access rules do not export

    Access Control decides which users and groups can see a matter and its related records. Those rules are configuration, not data, and the destination has its own security model. Restricted matters are listed with who may see them, and the equivalent restriction is rebuilt and tested in the new system before go-live.

  3. Intakes convert to matters

    An intake is its own record, filled in through an intake form and later converted to a matter. Converted intakes repeat what the matter already holds. Unconverted ones are leads or declined enquiries. The firm decides whether those go to the new system’s intake module, become contacts with a note, or stay behind.

  4. Fee arrangements drive the numbers

    Fees can be charged through a matter fee arrangement, once or on a recurring schedule, and the arrangement governs how time and expenses are treated. Few destinations model this the same way. Open arrangements are documented matter by matter, so that the next bill after the move is raised on the agreed terms.

  5. Legal holds and conflict checks

    The product keeps legal hold notices with their acknowledgements, and conflict checks can be run and their results managed. These are compliance records where the dates matter. If the destination has no place for them, they are exported as documents and filed to the matter or to the firm’s risk records.

More about moving off Mitratech CaseCloud

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Smokeball

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Mitratech CaseCloud 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Mitratech CaseCloud, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Smokeball as a trial and checked against Mitratech CaseCloud: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Mitratech CaseCloud 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 Mitratech CaseCloud as at the cutover date. Mitratech CaseCloud 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 Mitratech CaseCloud 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

Step 1 of 5: Start with the route

Moving fromMitratech CaseCloud
Moving toSmokeball

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Mitratech CaseCloud 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.

  3. 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

Mitratech CaseCloud to Smokeball: what firms ask

We bought AdvoLogix years ago. Is this page about our system?

Almost certainly. The product was sold as AdvoLogix Matter Management before Mitratech introduced the CaseCloud name in late 2024, and the two share a help centre. A quick check is the Salesforce app launcher. If it shows matters and participants under an AdvoLogix or CaseCloud application, the firm is on this product whatever the invoice says.

Can we stay on Salesforce and only replace the legal application?

Yes, if the destination also runs on Salesforce, as Litify does. The accounts and contacts can stay where they are, and the matter records are remapped inside the org or moved to a new one. It is still a migration, because each product brings its own objects for matters, parties and time.

What about documents held in NetDocuments or iManage?

If the files are in a document system through the integration, they may not need to move at all. The matter in the new system is pointed at the existing workspace, provided the destination integrates with the same store. Where it does not, the files are moved and the matter number is used to file each one.

Do trust balances in Mitratech CaseCloud 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 Mitratech CaseCloud 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 Mitratech CaseCloud have a place in Smokeball?

Most of it does on paper. 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 Smokeball is kept as a readable archive, and you see which before the move.

What has to be decided before Mitratech CaseCloud data is loaded into Smokeball?

Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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.

How we do itDiscovery to rollout, step by step

Mitratech CaseCloud and Smokeball are the names and marks of their owners, used here only to identify the two systems.

Moving from Mitratech CaseCloud 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.