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

Data migration route

Intapp to Gladiate migration

Intapp is a cloud specialist tool, and Gladiate is 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.

FromIntappCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Tasks: Carried across
  5. Intake: Carried across
  6. Emails: Confirmed in the analysis
  7. Notes: Confirmed in the analysis
  8. Calendar: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Billing: Confirmed in the analysis
  11. Custom fields: Confirmed in the analysis
  12. Templates: Confirmed in the analysis
ToGladiateCloud
  • 5 carried
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Intapp to Gladiate

Each row is a kind of record Intapp holds, whether Gladiate has a place for it, and what is planned. On this route five kinds of record carry across and seven kinds are confirmed in the analysis.

Records in Intapp and their place in Gladiate
RecordIn IntappIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNew business requests and their approvals, by client and matter.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeld in partClient, engagement and relationship data in Conflicts and DealCloud.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeld in partClient guideline documents and vendor agreements in Intapp Terms.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeEvents sync with Outlook and Google Calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partApproval workflows, tasks and alerts tied to intake and client terms.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldIntapp Time captures time across devices.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partBillstream manages proforma review and approval.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldIntake request forms and workflows are built by each firm.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntapp Intake runs client and matter onboarding; DealCloud holds pipeline.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 Intapp.
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. Intapp 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 Intapp 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 Intapp is kept running until the checks on Gladiate are finished.

Where the data is now

Nobody moves off Intapp as a whole. A firm replaces one product, or changes its practice system and finds that the Intapp products were fed by it. Either way the work starts by listing which products are licensed, what each holds that exists nowhere else, and which records are only copies of data owned by the finance system.

  1. Name the product first

    Intake, Conflicts, Walls, Terms, Time, Billstream and DealCloud each keep different records. A plan to move from Intapp means little until the product is named. The analysis opens with the list of products in use and whether each is on Intapp’s cloud or an earlier installation in the firm’s own environment.

  2. Intake history

    The Intake product holds each new business request with its answers, risk assessment and approvals. That is the firm’s evidence that a matter was opened properly. A practice system may take the client and matter but has no place for the approval trail, which is then kept as a document on the matter or in an archive.

  3. Conflict search records

    Conflicts brings client, engagement and relationship data together for searching and records the clearance of each search. The underlying names come from other systems and move with them. Clearance records do not, and the firm’s risk team decides how long it must stay retrievable and in what form.

  4. Time before it is posted

    The Time product captures time on phones and desktops and hands entries to the billing system. Entries still in draft, or captured but not released, may exist nowhere else. A cut-off is agreed so every timekeeper releases their time before the switch, and a count of unreleased entries is taken on the day.

  5. Walls and who sees what

    Walls sets information barriers once and enforces them across the firm’s other systems. When one of those systems is replaced, the restrictions have to be applied to the new one before any matter is opened to staff. The list of walled matters and their permitted teams is taken out early for that reason.

More about moving off Intapp

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 Intapp 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 Intapp: 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 Intapp, 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. Intapp 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 Intapp 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 fromIntapp
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 Intapp 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

Intapp to Gladiate: what firms ask

We are changing practice management system. What happens to our Intapp products?

They stay, but their connections change. Intake, Conflicts and Time work from the clients, matters and timekeepers in the practice system and write back to it. Each of those feeds is rebuilt against the new system and tested during the trial load, so new matters and time entries have a working route before go-live.

Can Intapp Time entries be moved into a practice system?

Released time normally already sits in the firm’s billing system, so it moves with that system. What needs attention is time still held in the capture tool. Timekeepers release it before the cut-off, and anything left is exported and loaded as unbilled entries against the right matters.

Is DealCloud covered?

DealCloud is Intapp’s relationship management product, used for contacts, pipeline and marketing. Moving it is a CRM migration in its own right. Contacts and their history are mapped to the new CRM or to the practice system’s contact records, and duplicates between the two lists are merged where they can be identified.

Does billing history from Intapp move into 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 Intapp before the plan is fixed. Billing records with no place in Gladiate are kept as reports and invoice copies.

Does everything in Intapp have a place in Gladiate?

Most of it does on paper. Emails, notes, calendar entries, time entries, billing records, custom fields and templates 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 Intapp data is loaded into Gladiate?

Emails, notes, calendar entries, time entries, billing records, custom fields and templates 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

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

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