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

Data migration route

Tabs3 to Smokeball migration

Tabs3 is a server-based 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.

FromTabs3Server
  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. Trust money: Carried with mapping
  12. Custom fields: Carried with mapping
  13. Templates: Carried with mapping
ToSmokeballDesktop and cloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Smokeball
  • 10 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 to Smokeball

Each row is a kind of record Tabs3 holds, whether Smokeball has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in Smokeball and is archived.

Records in Tabs3 and their place in Smokeball
RecordIn Tabs3In SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA matter is the part of the Client ID after the decimal point.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldHas a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeld in partPracticeMaster links documents to clients and contacts.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 partPracticeMaster keeps email records in its Journal.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeld in partNote, phone and research records in the PracticeMaster Journal.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesHeld in partIn PracticeMaster.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partIn PracticeMaster.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldIn Tabs3 Billing, with timers in PracticeMaster.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeldIn Tabs3 Billing.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesHeld in partWith the Trust Accounting module.Has a place in partMatter account balances load as opening balances; past transactions are not on the import list.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger and Accounts Payable modules.No placeNo general ledger; the firm’s books stay in an accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partPracticeMaster Areas of Practice carry the firm’s own files and fields.Has a place in partValues need a matching field in the matter type’s layouts.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument assembly in PracticeMaster; statement layouts in Billing.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partTabs3 CRM covers leads and intake and works with PracticeMaster.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 Tabs3.
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.
Kept as a readable archive
Smokeball has no place for it. It is exported in a format that opens without Tabs3 and handed to the firm as a read-only archive.

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. Tabs3 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 Tabs3’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.

Tabs3 runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Smokeball is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.

  1. One ID for client and matter

    A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.

  2. Everything in one directory

    The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.

  3. Standard and Platinum

    The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.

  4. Figures that are not stored

    The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.

  5. Cloud or server

    Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.

More about moving off Tabs3

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.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Tabs3 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 Tabs3, 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 Tabs3: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Tabs3 are frozen for an agreed window, the data is collected a final time and Smokeball 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. Tabs3 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 Tabs3 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 fromTabs3
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 Tabs3 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

Tabs3 to Smokeball: what firms ask

We only have Tabs3 Billing and PracticeMaster. Is that a problem?

No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.

Can we keep the client dot matter numbering?

If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.

How are the modules extracted together?

From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.

Do trust balances in Tabs3 have a place in Smokeball?

In part. Matter account balances load as opening balances; past transactions are not on the import list. The analysis sets out which trust records have a place in Smokeball and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Smokeball has no place for?

On this route that is the firm’s accounts. They are exported from Tabs3 in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

Trust ledgers, 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.

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

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

Moving from Tabs3 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.