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

Data migration route

Primafact to Gladiate migration

Primafact is a server-based document management system for litigation work, and Gladiate is a cloud case management system for personal injury work. The move is matching each file in Primafact to its case in Gladiate.

FromPrimafactServer
  1. Matters: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Templates: Carried with mapping
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Custom fields: Confirmed in the analysis
ToGladiateCloud
  • 3 carried
  • 1 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Primafact to Gladiate

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

Records in Primafact and their place in Gladiate
RecordIn PrimafactIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partCases exist as containers for binders, not as matter records with parties and status.Has a placePersonal injury cases.Carried across
DocumentsFiles stored in or linked from the systemHeldPaged documents in binders, with profile fields, searchable text and markup.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails can be imported from Outlook as documents.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldAnnotations and notes attached to documents and pages.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partReview workflow only: an Inbox, team flags and document discussions.Has a placeTasks and task plans.Carried across
Custom fieldsFields and record types the firm added itselfHeldProfile fields, annotation colour labels and team flag labels are set by the firm.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partCase templates set binder structure, coding and permissions for new cases.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping

What the plans mean

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Primafact organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Gladiate before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

Primafact 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

What a firm holds in Primafact is evidence and the work done on it. Moving the documents themselves is the easy part. The value is in how they were arranged into binders and what reviewers wrote on them, and almost no general document system stores an annotation against a page. How that work is preserved has to be written into the plan.

  1. Binders, tabs and sections

    A case’s documents are arranged into binders with tabs and sections, in the order counsel wants them for a brief or production. That order is deliberate. It is carried across as numbered folders or as a tabbed PDF of each binder, so the arrangement can still be read where the destination sorts only by name or date.

  2. Annotations belong to pages

    Reviewers attach annotations to particular pages, with colour labels, and build chronologies from them. A document store has nowhere to put a note tied to page 214. Annotation lists and chronologies are exported as reports and saved to the matter, and highlights are kept by exporting the marked-up PDF.

  3. One document, several binders

    The same document can appear in more than one binder, for example in the productions binder and an expert brief. A file-by-file export would write it out twice. Copies are identified so the destination holds one file, and each binder’s contents are recorded as a list that refers to it.

  4. Profile fields and title aliases

    Each document carries profile fields, which firms use for things like service status, and can show a title alias that differs from its file name. These are the document’s metadata. They are mapped to the destination’s profile or to the file name, with the document date preserved exactly, since chronologies sort on it.

  5. Server, workstations, scan station

    The software is installed in three places, and the firm’s documents are held on its own equipment. Extraction needs the program still installed, because binders and reports are exported through Primafact itself. The old installation is kept until every active case has been checked in its new home.

More about moving off Primafact

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.

Nothing financial lands in Gladiate on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Primafact 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 Primafact: 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

    There is no financial cutover on this route. After a short freeze on changes in Primafact, a final pass over a weekend picks up what changed since the trial. Primafact 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 Primafact 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 fromPrimafact
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 Primafact 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

Primafact to Gladiate: what firms ask

Can annotations move into iManage, NetDocuments or SharePoint?

Not as annotations. Those systems store documents and their profiles, and have no record for a reviewer’s note on a page. The practical answer is to export annotation reports and chronologies as documents, and marked-up PDFs with the highlights visible, and file them with the originals.

Do we need to move closed cases out of Primafact?

Often not. A closed case’s productions have usually been exported already as tabbed PDFs. If those are on the matter in the practice management or document system, the working binders can stay in the old installation, kept read only. Active cases are the ones that need their structure and review work preserved.

Is Primafact a practice management system?

No. It manages the documents in a litigation file and the review work on them, and its feature pages describe no ledger, time recording or client records. Firms run it beside a practice or case management system, and a move usually sends the documents to that system or to a document management product.

Do documents from Primafact keep their folders and dates in Gladiate?

Gladiate stores documents. Filed to the firm’s folder structure. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Primafact have a place in Gladiate?

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

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

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

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