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

Data migration route

LEAP 365 to Gladiate migration

LEAP 365 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.

FromLEAP 365Cloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Intake: Carried across
  6. Templates: Carried with mapping
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Tasks: 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
  • 5 carried
  • 1 mapped
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LEAP 365 to Gladiate

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

Records in LEAP 365 and their place in Gladiate
RecordIn LEAP 365In GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe same electronic matters as the desktop program.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldCards, as in the rest of LEAP.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeldStored in the matter on LEAP’s servers.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeldOnly emails that were saved to a matter.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCritical dates sit on the matter; anything further is confirmed in the analysis.Has a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks and task plans.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTo be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldTo be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldLEAP’s in-built trust accounting.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partLEAP’s office accounting module, or Xero or MYOB through an integration.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partFields come mainly from LEAP’s matter types, with matter tables for repeating data.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldLEAP’s forms library and the firm’s own precedents.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 pipelinesHeldEnquiries are recorded in LEAP CRM.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 LEAP 365.
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 LEAP 365 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 LEAP 365, 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 LEAP 365 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 LEAP 365 is kept running until the checks on Gladiate are finished.

Where the data is now

For a firm on LEAP 365 the migration is a LEAP migration. The browser is only the window; the records sit in LEAP’s cloud and are extracted from there. What differs is the firm’s working habits. Browser-first firms often have people on Macs or at home with no LEAP software installed, so nothing can be gathered from local machines.

  1. One account, two front ends

    LEAP 365 and LEAP Desktop open the same account. A firm with some staff in the browser and others on the desktop program has one set of data, and it is moved once. The matter list a partner sees in Chrome at home is the list the office sees, with the same matter numbers.

  2. No local copies to rely on

    With the browser version there is no installed program holding working copies of documents. Every file has to come from LEAP’s export. We test the export for completeness by counting documents per matter against what LEAP shows on screen, for a sample of large and small files, before the trial load.

  3. Emails that were never saved

    Only correspondence saved to a matter is in LEAP. Emails still sitting in a lawyer’s mailbox are not part of the export, whichever version of LEAP was used. If the firm wants them on the file in the new system, they are saved to the matter before the freeze or handled as a separate mailbox exercise.

  4. Enquiries in LEAP CRM

    LEAP CRM keeps enquiries that have not become matters, with a record of calls and emails and the conflict details taken at first contact. They are not in the matter list. The firm decides whether open enquiries move to the new system’s intake tool and whether old ones are kept at all.

  5. Month end before cutover

    Trust accounting in LEAP includes an end-of-month process with reconciliation and statements. Cutover is timed so that process has been completed in LEAP for the final period. The closing trust balance on each matter is then the figure loaded, and it reads the same in the browser, the desktop program and the reports.

More about moving off LEAP 365

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 LEAP 365 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 LEAP 365: 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 LEAP 365, 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. LEAP 365 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 LEAP 365 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 fromLEAP 365
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 LEAP 365 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

LEAP 365 to Gladiate: what firms ask

We only use LEAP in the browser. Is the move simpler?

The data work is the same, because the records are held by LEAP either way. There is less to do on the firm’s computers, as no program has to be uninstalled. Training can be easier where the new system is also used in a browser, since staff already work that way.

Can we keep using LEAP 365 to look things up afterwards?

Only for as long as the firm’s LEAP agreement allows access. That is read from the agreement before notice is given. If access ends on a fixed date, the records the firm must keep, including trust and billing history, are exported as reports and documents before then and stored where the firm can reach them.

Do our matter numbers change?

They need not. LEAP’s matter number is loaded as the matter number in the new system where that system accepts one. Documents are matched to matters on that number, so it has to be unique. Any duplicates found in the analysis are corrected in LEAP before extraction.

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

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

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

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

Moving from LEAP 365 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.