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

Data migration route

Neos to Gladiate migration

Neos and Gladiate are each 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.

FromNeosCloud
  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 Neos to Gladiate

Each row is a kind of record Neos 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 Neos and their place in Gladiate
RecordIn NeosIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with a Management tab for fee and referral details.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeldParties, providers, counsel, case contacts and related contacts.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeldCase Docs tab with sub-tabs, viewable as a list or as folders.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeldEmails can be tagged to the case file. Outlook is integrated.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes, including Special Notes.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCase calendars, with statute and deadline alerts.Has a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldChecklists and case tasks, which feed staff dashboards.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers on a case, which can create value items.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices in PDF, Word or LEDES format. Payments through LawPay.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partTrust requests can be raised and paid through LawPay.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldUser-defined fields can be added to case tabs.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldA document generation wizard merges templates for one case or many.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 pipelinesHeldIntakes tab and intake 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 Neos.
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. Neos 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.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Neos 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 Neos is kept running until the checks on Gladiate are finished.

Where the data is now

A firm leaving Neos is leaving a cloud system whose data sits in a database dedicated to that firm. The structure runs tab by tab, and each tab is in effect a table. Many Neos firms came from Needles or Trialworks, so the data often carries conventions two systems old, and the analysis has to read those as well.

  1. A database per firm

    Assembly holds each firm’s records in a separate Azure SQL database. For a migration that means the data set is self-contained, with nothing shared with other customers. How a copy is obtained is arranged with the firm at the start, and the copy and the document files are taken at the same point in time.

  2. Value items hold the money

    Bills, costs, time and settlement entries are value items on the Value tab, with transactions beneath them for payments. A general system splits those across disbursements, time, invoices and receipts. Each value code is mapped to one of them, and the case totals are compared before and after.

  3. Fields inherited from Trialworks

    When a Trialworks firm is converted to Neos, some standard fields land in user-defined fields and in document sub-tabs named after the old tabs. A firm that has been through that carries two layers of structure. Both are read, so a field that looks custom is recognised as the old system’s standard field.

  4. Checklists and calendars

    Work in progress is split between checklist items and case calendar entries, and dashboards are built from both. Open checklist items become tasks in the destination. Calendar entries become events. The two are counted separately in the trial load, because losing either leaves a fee earner with an empty list on the first morning.

More about moving off Neos

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 Neos 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 Neos: 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 Neos, 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. Neos 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 Neos 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 fromNeos
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 Neos 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

Neos to Gladiate: what firms ask

We have seen NEOS Web and NEOS DB listed. Are they different from Neos?

Assembly’s own site describes a single product, Neos, used in a browser, with each firm’s records in a dedicated Azure SQL database. Some software lists show NEOS Web and NEOS DB as separate entries. Which system a firm actually holds, and where its data sits, is identified at the start of the analysis.

We are on Needles. Is Neos just an upgrade?

No, it is a migration. Needles keeps its data in a SAP ASE database on the firm’s server and Neos uses Azure SQL in the cloud, so records and documents are converted, not upgraded in place. Assembly says the case logic is the same, which shortens the mapping compared with a move elsewhere.

Can Neos replace our accounting system?

Not the general ledger. Neos records case money as value items, raises invoices and trust requests, and takes payments through LawPay, and it links to QuickBooks Desktop or Online for the books. A firm moving from a system with built-in accounting plans a QuickBooks set-up as part of the same project.

Do trust balances in Neos 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 Neos 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 Neos 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 Neos 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

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

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