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

Data migration route

Gladiate to NetDocuments migration

Gladiate is a cloud case management system for personal injury work, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromGladiateCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Templates: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Notes: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Time and expenses: Confirmed in the analysis
  8. Billing: Confirmed in the analysis
  9. Trust money: Confirmed in the analysis
  10. Firm accounts: Confirmed in the analysis
  11. Custom fields: Confirmed in the analysis
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 2 mapped
  • 8 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Gladiate to NetDocuments

Each row is a kind of record Gladiate holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, three kinds have no place in NetDocuments and are archived and eight kinds are confirmed in the analysis.

Records in Gladiate and their place in NetDocuments
RecordIn GladiateIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldPersonal injury cases with coverage, liability and medical data.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClients, leads and referral sources in a built-in CRM.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldFiles in a folder structure the firm defines. E-signature is built in.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Microsoft Outlook and Google Calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTask lists and task plans.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldThe firm’s own document templates, set up during onboarding.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient sign-up, questionnaires and lead nurturing.No placeKept as a readable archive

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Gladiate.
Carried with mapping
NetDocuments 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.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without Gladiate and handed to the firm as a read-only archive.

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Gladiate is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Gladiate for matters and billing, or into an archive.

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

Where the data is now

Gladiate keeps an injury firm’s cases, client communications and marketing contacts together, so a move off it touches more than the case list. The structured injury data needs a home in the destination. So do the things most case systems lack: survey responses, scheduled client updates and the state of each medical record request.

  1. Medical record request status

    Requests to providers for records and bills are generated and followed up inside the product. At any moment a firm has many in flight. The open requests are listed at cutover with provider, date sent and what is outstanding, and loaded as tasks or a tracking list so the chasing carries on.

  2. Surveys and questionnaires

    Clients answer questionnaires for the case and surveys about their medical providers and the firm’s service. The answers are client evidence and marketing data at once. Questionnaire answers go to the case as fields or a saved document. Survey results are exported for the firm, as few destinations have a place for them.

  3. Referral sources and past clients

    The CRM side holds referral sources, former clients and the marketing campaigns sent to them. If the destination has no marketing module, those contacts still come across with their type and source. Campaign history is exported as a report, and the firm decides whether a separate marketing tool takes over.

  4. Scheduled client updates

    Automatic case updates go to clients on a schedule. When the old system is frozen those messages stop, and clients notice. The schedule and wording are recorded before cutover, and either an equivalent is switched on in the new system at go-live or the firm tells clients to expect a gap.

More about moving off Gladiate

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Gladiate holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments and checked against Gladiate: 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 Gladiate, a final pass over a weekend picks up what changed since the trial. Gladiate 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 Gladiate 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 fromGladiate
Moving toNetDocuments

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 Gladiate holds

    What is in it, how its records link, and where each piece would sit in NetDocuments. 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 NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Gladiate to NetDocuments: what firms ask

Does Gladiate handle time recording or trust accounting?

The vendor’s public material describes case management, client communication and marketing for injury firms. It does not describe time billing or trust ledgers. A firm that depends on either asks the vendor directly, and the answer decides whether an accounting package runs alongside.

Can we bring our closed cases into Gladiate?

That is confirmed with the vendor during onboarding, because its public pages do not say how history is loaded. The firm decides how far back to go. Former clients are also a marketing list in Gladiate, which is a reason to bring at least the client and the outcome of each closed case.

What do we lose if we move from Gladiate to a general system?

Mostly the client-facing automation: scheduled updates, surveys and the record request process. The case data moves. Those features are rebuilt with the destination’s own tools, replaced by a separate product, or dropped. The firm sees that list before deciding, together with any fields that have no home.

Do trust balances in Gladiate have a place in NetDocuments?

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 Gladiate before the plan is fixed. If NetDocuments turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records NetDocuments has no place for?

On this route that is contacts, calendar entries and intake records. They are exported from Gladiate in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Gladiate data is loaded into NetDocuments?

Matters and 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

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

Moving from Gladiate to NetDocuments?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.