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

Data migration route

Abacus Accounting to Gladiate migration

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

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

What moves

What moves from Abacus Accounting to Gladiate

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

Records in Abacus Accounting and their place in Gladiate
RecordIn Abacus AccountingIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partOnly matters sent from AbacusLaw with a BILLTO link appear.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeld in partBill-to names and vendors.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeld in partCopies of invoices and posting reports are saved as files in a Bills folder.Has a placeFiled to the firm’s folder structure.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTo be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldIncludes split billing, rate cards and interest on late accounts.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust by client and matter, including IOLTA accounts.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, vendor bills and bank reconciliation, with month-end and year-end closing.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 automationHeld in partBilling templates set the layout of invoices.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 Abacus Accounting.
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. Abacus Accounting 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 Abacus Accounting as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Abacus Accounting 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.

Abacus Accounting 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

Moving the books out of Abacus Accounting is a ledger job more than a document job. Unbilled time and costs, open invoices, trust balances by client and matter, and the general ledger each have to arrive agreeing with a report run on the last day. The matters themselves come from AbacusLaw, so the two are extracted together and matched on the matter.

  1. Only billed matters appear

    A matter exists in accounting only after someone linked a name to it in AbacusLaw with the link type BILLTO. So the list of matters with money on them is shorter than the list of matters. The two lists are reconciled first, which also finds matters that were billed under the wrong name.

  2. Soft closes and hard closes

    A month-end close in this module can be undone later, and it closes every earlier month with it. The year-end close is the firmer one. Opening balances for the new system are taken at a closed period end so they agree with printed reports, and the firm leaves that period closed.

  3. Saved bills are files

    Copies of invoices and posting reports are kept as files in the Abacus\Bills folder, outside the tables. Those are the bills as the client received them. They can be filed against each matter in the destination even where invoice history is loaded only as balances.

  4. Trust by matter and by bank

    Trust money is held by client and matter, and a firm may run more than one trust bank account, IOLTA among them. The trial load is checked against the trust listing for each bank account, matter by matter. A matter with a trust balance but no open file in the new system is listed for the firm to decide.

More about moving off Abacus Accounting

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 Abacus Accounting 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 Abacus Accounting: 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 Abacus Accounting, 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. Abacus Accounting 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 Abacus Accounting 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 fromAbacus Accounting
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 Abacus Accounting 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

Abacus Accounting to Gladiate: what firms ask

Can we bring across full transaction history or only balances?

It depends on what the destination can take. Many systems accept opening balances, unbilled time and costs and open invoices, but not years of posted ledger entries. The usual answer is balances and open items loaded, with older detail kept in the read-only copy and in the saved bill files.

Does the general ledger move too?

Only if the new system has a general ledger of its own. If it posts to a separate accounting package, the chart of accounts and closing balances go there instead, as an opening journal the firm’s accountant approves. The analysis settles which before any data is taken.

What if our trust ledger does not reconcile today?

Then it is fixed in Abacus before extraction, not after. Unreconciled items, old uncleared cheques and balances on finished matters are listed during the analysis. The firm clears what it can, and anything left is carried across as a named exception with the same figure on both sides.

Do trust balances in Abacus Accounting 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 Abacus Accounting 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 Abacus Accounting have a place in Gladiate?

Most of it does on paper. Notes, time entries, billing records, trust ledgers, the firm’s accounts 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 Abacus Accounting 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, the firm’s accounts 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

Abacus Accounting and Gladiate are the names and marks of their owners, used here only to identify the two systems.

Moving from Abacus Accounting 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.