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.
AbacusLawServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
GladiateCloud- 6 carried
- 1 mapped
- 7 to confirm
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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters are joined to Names by typed links such as BILLTO. | Has a placePersonal injury cases. | Carried across |
| ContactsClients, other parties and referrers | HeldCalled Names. | Has a placeClients, leads and referral sources. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldEach 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 store | Held in partEmails linked from Outlook through the add-in are copied to an Email folder on the server. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalled Events; court rules can generate dates. | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeTasks and task plans. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is billed through the Abacus Accounting module. | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | Held in partInvoices and receivables are in Abacus Accounting, where the firm has it. | To be confirmed | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust accounting is part of Abacus Accounting. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partGeneral ledger and vendor bills are part of Abacus Accounting. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldPractice area packs and the firm’s own changes add screens, fields and codes. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldAbacus 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 pipelines | HeldIntake 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
Leaving AbacusLaw
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Gladiate
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- 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.
- 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.
Other routes
Other routes from AbacusLaw and into Gladiate
Other destinations from AbacusLaw
Other systems that move into Gladiate
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
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.