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

Data migration route

Gladiate to SharePoint migration

Gladiate is a cloud case management system for personal injury work, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from Gladiate to SharePoint

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

Records in Gladiate and their place in SharePoint
RecordIn GladiateIn SharePointWhat 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 site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldClients, leads and referral sources in a built-in CRM.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldFiles in a folder structure the firm defines. E-signature is built in.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Microsoft Outlook and Google Calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTask lists and task plans.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
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 placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldThe firm’s own document templates, set up during onboarding.Has a place in partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against Gladiate.
Carried with mapping
SharePoint 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
SharePoint 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Gladiate into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Gladiate.

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 SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 toSharePoint

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 SharePoint. 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

Structure, permissions and handover

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Gladiate to SharePoint: 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 SharePoint?

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 SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, calendar entries, tasks and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, 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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Gladiate to SharePoint?

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

We reply within one business day.