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

Data migration route

AbacusLaw to Gladiate migration

AbacusLaw is a server-based practice management system, and Gladiate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from AbacusLaw to Gladiate

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

Records in AbacusLaw and their place in Gladiate
RecordIn AbacusLawIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters are joined to Names by typed links such as BILLTO.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldCalled Names.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeldEach document record stores the path to a file on disk, with type codes, author, status and notes.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails linked from Outlook through the add-in are copied to an Email folder on the server.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalled Events; court rules can generate dates.Has a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime is billed through the Abacus Accounting module.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partInvoices and receivables are in Abacus Accounting, where the firm has it.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partTrust accounting is part of Abacus Accounting.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partGeneral ledger and vendor bills are part of Abacus Accounting.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldPractice area packs and the firm’s own changes add screens, fields and codes.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldAbacus forms and court forms filled from name and matter data.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake screens and lead management.Has a placeLeads and client sign-up.Carried across

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Gladiate. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from AbacusLaw has to be given a case type in Gladiate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Gladiate is exported as reports and ledgers the firm can open without AbacusLaw, and kept as the record of what was billed and held.

AbacusLaw 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

A move off AbacusLaw starts with which database version the firm runs and which folders its files sit in. The case data lives in tables on the server, while documents, linked emails and forms are ordinary files in folders beside them. Names and Matters are joined by typed links, and those links decide who the client is on each matter in the new system.

  1. Check the database version

    Many installs run on Advantage Database Server, which the vendor calls the ADS version, with tables in a data folder usually named data01. Releases up to v23.16 also kept DBF files there. Which version and release a firm has decides how the data is read out, so it is the first thing checked.

  2. Names are linked, not typed

    A person is entered once as a Name and then linked to matters with a link type. One Name can be the client on one matter and a witness on another. The link types a firm has used are mapped one by one to contact roles in the destination, because that is where the client relationship is recorded.

  3. Documents are paths on disk

    Each document record stores the full path to a file, plus type codes, author, status, a box number and notes. Files commonly sit in an Abacus\Docs folder and linked Outlook emails in an Email folder. If a file was moved or renamed outside the program, the record still points at the old place, so paths are tested before the trial load.

  4. Accounting is a separate module

    Billing, trust and the ledgers belong to Abacus Accounting, which keeps its tables in an accounting subfolder. A matter only appears there after a Name is linked to it as BILLTO. Firms that never bought the module have their time and costs in some other program, and that program joins the scope.

  5. Practice packs change the fields

    Practice Area Essentials add input screens, codes, rules and forms for a practice area. Two firms on the same version can hold quite different fields on a matter. The field list is read from the firm’s own database, not from a standard layout.

More about moving off AbacusLaw

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 AbacusLaw 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 AbacusLaw: 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 AbacusLaw, 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. AbacusLaw 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 AbacusLaw 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 fromAbacusLaw
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 AbacusLaw 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

AbacusLaw to Gladiate: what firms ask

Can we keep our AbacusLaw matter numbers?

Usually, if the destination lets you set the matter number yourself or has a reference field for it. The file number and the matter name are both carried so staff can search by either. If the new system insists on its own numbering, the old number comes across as a searchable reference.

What happens to our court forms and templates?

Forms built in Abacus are tied to its own field names, so they do not run anywhere else. The analysis lists the forms the firm really uses and each one is rebuilt as a template in the new system. Standard court forms supplied by the vendor are replaced with the destination’s own library where it has one.

Do emails linked from Outlook come across?

Emails linked through the Outlook add-in are copied to a folder on the server, with a record against the name or matter. Those copies can be filed to the same matter in the new system. Mail that was never linked stays in the mailbox and is not part of the move.

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

Most of it does on paper. Emails, 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 AbacusLaw data is loaded into Gladiate?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, 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

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

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