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

Data migration route

CollectMax to Gladiate migration

CollectMax is a server-based case management system for debt recovery work, and Gladiate is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.

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

What moves

What moves from CollectMax to Gladiate

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

Records in CollectMax and their place in Gladiate
RecordIn CollectMaxIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAccounts, each with one or more claims, a status code and links to related accounts.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldDebtors, clients (creditors or forwarders), plaintiffs and other account members.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeld in partLetters and documents are generated per account or claim; stored files not confirmed.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldAccount notes, with colour-coded note indicators.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeEvents sync with Outlook and Google Calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partMaxPlans schedule the documents due on each account.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedTo be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldCollection fee and suit fee invoices to clients, produced by remittance processing.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldA trust bank account with internal client accounts, monitored against overdraft.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partClient-specific user variables and firm-defined status codes.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldLetter and document templates, sent singly or in batches.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 pipelinesTo be confirmedHas a placeLeads and client sign-up.Confirmed in the analysis

What the plans mean

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. CollectMax and Gladiate may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Gladiate, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

CollectMax 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 collections system does not look like a practice system. There is no matter with a client and a bill. There is an account with debtors and claims, a balance that grows with interest, payments that land in trust and a remittance that pays the client. Moving off it means deciding what a matter is before a single record is mapped.

  1. Accounts, debtors and claims

    One CollectMax account can hold several debtors and several claims, and each claim has a reference number that is usually the original creditor’s account number. A destination needs one matter per account or one per claim. The choice affects how balances, documents and court details divide, so it is tested on real accounts before it is fixed.

  2. Five-part claim balances

    A debt is kept as principal, interest, fees, costs and other, and interest can be projected forward. A general practice system has a debtor balance on an invoice and nothing like this. If the destination cannot calculate interest on a claim, the balance at cutover is loaded as a fixed figure with the rate and date noted.

  3. Remittance, not billing

    Debtor payments go into the trust bank account. Remittance processing then pays the client and raises the firm’s invoice for its collection fee, under whichever withholding arrangement that client has. This is the reverse of ordinary legal billing. Each client’s arrangement is recorded in the analysis, since the new system has to reproduce the same split.

  4. Client, forwarder and plaintiff

    The client on an account is either the creditor or a forwarder who sent the debt on, and a plaintiff may be attached separately. Three parties can stand where a practice system expects one client. All three are kept as linked contacts, and the one the firm reports and remits to becomes the client.

  5. Status codes and contact flags

    Status codes show where each claim is in the collection process and when it changed. Accounts also carry flags such as Do Not Contact, bankruptcy or a defending attorney, which stop letters being produced. Those flags protect the firm from contacting someone it must not. They are mapped first and checked on every trial load.

More about moving off CollectMax

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 CollectMax 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 CollectMax: 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 CollectMax, 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. CollectMax 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 CollectMax 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 fromCollectMax
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 CollectMax 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

CollectMax to Gladiate: what firms ask

Can a general practice system run a collections practice?

Only with work. Matters, contacts and documents are no trouble. Interest on claims, payment posting in bulk, remittance to clients and electronic exchange with creditors are collections functions that most general systems lack. The analysis lists which of these the firm uses daily, and that list usually settles what kind of destination is realistic.

What happens to accounts with payment arrangements in progress?

They are the records to watch. Each has a balance, a payment history and a next expected payment. Where the destination takes payment history, it is loaded so the balance can be recalculated, not just stated. On the trial load, a sample of paying accounts is compared with CollectMax, including interest accrued to the day.

Do trust balances for each client carry over?

They are carried as opening balances, client by client. CollectMax keeps many clients’ money in one trust bank account through internal accounts, and the total of those must equal the bank balance on cutover day. That reconciliation is rehearsed on a full trial load first, because the financial cutover is not something to repeat.

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

Most of it does on paper. Emails, notes, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records 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 CollectMax data is loaded into Gladiate?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records 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

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

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