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

Data migration route

Lawcus to Gladiate migration

Lawcus is a cloud 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.

FromLawcusCloud
  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. Custom fields: Confirmed in the analysis
ToGladiateCloud
  • 6 carried
  • 1 mapped
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Lawcus to Gladiate

Each row is a kind of record Lawcus 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 six kinds are confirmed in the analysis.

Records in Lawcus and their place in Gladiate
RecordIn LawcusIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldShown as cards on boards with a stage, or as a list; numbers come from a saved scheme.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldContacts with custom fields and field groups.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeldFolders in Lawcus, with two-way sync to Google Drive and links to Dropbox, Box or OneDrive.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments logged to a matter through the Gmail or Outlook add-ins.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes and interactions on a matter can be pinned or starred.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldHas a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldNo-code workflows can create tasks when a matter changes.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTo be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldHourly, flat fee and contingency; invoice templates per currency; credit notes.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust balances and a minimum retainer threshold per matter.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields and field groups for contacts and matters.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument automation and reusable invoice templates.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 pipelinesHeldLeads on a Kanban board, with client-facing and internal forms.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 Lawcus.
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 Lawcus 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 Lawcus, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lawcus depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Lawcus is kept running until the checks on Gladiate are finished.

Where the data is now

In Lawcus a matter’s position on a board says as much about it as any field. Stages, boards and the automations attached to them are how a firm on Lawcus knows where every file stands. A move off it has to turn that visual arrangement into something the destination can store, and it has to do so without losing the difference between a lead and a matter.

  1. Stages are the status

    Each board has its own stages, and a matter’s stage is what staff look at to see progress. A conveyancing board and a litigation board will not share stage names. Destinations tend to offer one status list, or a status per matter type. Every board’s stages are mapped separately, and the firm approves the mapping.

  2. Leads sit on boards too

    Prospects are tracked on a Kanban board of their own before they become clients. A lead and a matter can look alike in the interface. The extraction keeps them apart, and leads that were never converted are loaded as intake records or left as an exported list, depending on what the destination offers.

  3. Automations are not data

    No-code workflows send emails, create tasks and produce documents when a matter changes stage or a form comes in. None of that is a record that can be moved. The workflows are documented as rules during the analysis, and the firm chooses which ones to rebuild in the new system’s own automation.

  4. QuickBooks was fed one way

    Lawcus pushes invoices, payments and expenses to QuickBooks Online and takes nothing back. An edit made directly in QuickBooks is therefore unknown to Lawcus. The two can drift apart. Receivables are compared on both sides before cutover, and the firm decides which figure is right where they differ.

  5. More than one currency

    Invoice templates can be set up for clients billed in different currencies. A destination that works in one currency cannot hold those balances as they are. Foreign-currency clients are identified early, and the firm decides whether their history is converted at a stated rate or kept in the old system.

More about moving off Lawcus

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 Lawcus 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 Lawcus: 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 Lawcus, 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. Lawcus 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 Lawcus 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 fromLawcus
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 Lawcus 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

Lawcus to Gladiate: what firms ask

Our documents sync between Lawcus and Google Drive. Which copy is moved?

The Google Drive copy is usually the easier source, because it is in the firm’s own account and the sync keeps the two alike. Lawcus supplies the link between each folder and its matter. A sample of matters is compared on both sides first to confirm nothing is missing from the Drive.

Can our matter numbers be kept?

Yes. Lawcus generates matter numbers from a numbering scheme the firm saved, so the numbers are consistent and can be carried as they are. If the destination produces numbers in another format, the Lawcus number is kept in a reference field and new matters follow the new format.

What happens to forms our clients filled in?

Answers that were saved to fields on a contact or matter are data and move with that record. Forms marked internal are treated the same way. The form designs are specific to Lawcus. If the new system has intake forms, they are rebuilt there from the same questions.

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

Most of it does on paper. Emails, 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 Lawcus 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 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

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

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