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

Data migration route

Tabs3 Billing to Gladiate migration

Tabs3 Billing is a server-based accounting and billing system, and Gladiate is a cloud case management system for personal injury work. Only part of what Tabs3 Billing holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromTabs3 BillingServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Templates: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Time and expenses: Confirmed in the analysis
  6. Billing: Confirmed in the analysis
  7. Trust money: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
ToGladiateCloud
  • 2 carried
  • 1 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Billing to Gladiate

Each row is a kind of record Tabs3 Billing holds, whether Gladiate has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and five kinds are confirmed in the analysis.

Records in Tabs3 Billing and their place in Gladiate
RecordIn Tabs3 BillingIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter is a Client ID; the digits after the decimal point are the matter.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeld in partClient names and addresses; fuller contact records are in PracticeMaster.Has a placeClients, leads and referral sources.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldFees with hours worked and hours to bill, plus costs.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldDraft and final statements, payments and a client ledger.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient funds for retainers; trust ledgers are in the Trust Accounting module.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldStatement layouts built in the Statement Designer.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping

What the plans mean

Carried across
Gladiate has a place for this kind of record. It is loaded there and checked against Tabs3 Billing.
Carried with mapping
Gladiate 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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Tabs3 Billing knows clients, jobs, time and invoices. Gladiate knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Gladiate are loaded and checked there. The rest is exported from Tabs3 Billing as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Tabs3 Billing is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

Tabs3 Billing 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. Gladiate 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

Billing is where a Tabs3 firm’s money history sits. A move takes unbilled fees and costs, open statements, payments, client funds and the receivable ledger, and agrees each to a Tabs3 report at a statement cut-off. The archive of billed transactions is large and is handled as its own decision. Trust and the general ledger are other modules and move alongside.

  1. Work in process and archive

    Updating a final statement moves its fees, costs and payments out of the working files into archive files named T3ARCH. So unbilled work is in one place and billed history in another. Unbilled items are loaded as unbilled. The archive is loaded as history only where the destination can hold billed entries without billing them again.

  2. Statements can be undone

    Tabs3 can undo an updated statement, which moves its transactions back from the archive to work in process. Before the final extraction, the firm confirms that no statements are waiting to be undone or run again. A statement reversed after the data is taken would leave the two systems disagreeing about what has been billed.

  3. Client funds are not trust

    The client funds feature tracks non-refundable retainers and similar money kept in the firm’s general account, apart from the receivable balance. It is a different thing from the Trust Accounting module. Each client funds balance is mapped on purpose, usually to a retainer or credit on the matter, and not to the trust ledger.

  4. Courtesy discounts change history

    When a client is billed with a courtesy discount, each archived fee is reduced by its share of the discount. The archive therefore shows fees net of discount, not as first recorded. History loaded elsewhere is compared with Tabs3 on that basis, or the totals look wrong when they are not.

  5. Deleted clients take history

    Deleting a client in Tabs3 deletes its archived transactions too. A firm that tidied its client list years ago may hold less history than it expects. The analysis reports the earliest transaction date for each client, so nobody plans around records that are no longer there.

More about moving off Tabs3 Billing

Where it is going

Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.

  1. Injury fields come first

    Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.

  2. Templates and task plans

    The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.

  3. A folder structure per case

    Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.

  4. What it may not hold

    Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.

More about moving into Gladiate

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Tabs3 Billing holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Gladiate and checked against Tabs3 Billing: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    After a short freeze on changes in Tabs3 Billing, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Tabs3 Billing 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 Billing 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 Billing
Moving toGladiate

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 Billing holds

    What is in it, how its records link, and where each piece would sit in Gladiate. 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 Gladiate

Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.

Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.

Set-up decisions in Gladiate

  • Set up and test the firm’s document templates
  • Write task plans for each stage of a case
  • Agree one folder structure for case documents
  • Enter litigation deadlines for the firm’s jurisdictions
  • Prepare client questionnaires, surveys and scheduled case updates
  • Connect Outlook or Google calendars for two-way sync

Questions

Tabs3 Billing to Gladiate: what firms ask

Can billed fee history be loaded, or only balances?

Open statements and their balances are loaded, because the firm still has to collect them. Whether every billed fee line from the archive comes across depends on the destination: some accept billed time as history, others only take invoice totals. Where detail cannot be loaded, the archive stays readable in Tabs3, which is kept read only.

What about our statement templates?

Statement layouts are built in the Tabs3 Statement Designer and do not open in another product. The firm picks the layouts it still uses, and those are rebuilt as invoice templates in the new system. A side-by-side print of one real client’s bill from each system is the test.

Do timekeeper rates and billing categories move?

Timekeepers, rate tables and transaction codes are extracted as lists and set up in the destination before any time is loaded, because every fee entry refers to them. Client and matter rate exceptions are loaded with the matter. Codes nobody has used in years are left out by agreement.

Do trust balances in Tabs3 Billing have a place in Gladiate?

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 Tabs3 Billing before the plan is fixed. If Gladiate 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 Tabs3 Billing have a place in Gladiate?

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

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

Templates are carried with mapping, so each mapping is agreed with you first. Notes, time entries, billing records, trust ledgers and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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 Billing and Gladiate are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 Billing to Gladiate?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.