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

Data migration route

Salesforce to Gladiate migration

Salesforce is a cloud CRM and intake system, and Gladiate is a cloud case management system for personal injury work. Contacts and intake history move, and open enquiries become leads or cases in Gladiate.

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

What moves

What moves from Salesforce to Gladiate

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

Records in Salesforce and their place in Gladiate
RecordIn SalesforceIn GladiateWhat is planned
ContactsClients, other parties and referrersHeldAccounts and contacts, or person accounts for individuals. Leads are separate.Has a placeClients, leads and referral sources.Carried across
DocumentsFiles stored in or linked from the systemHeld in partSalesforce Files and older attachments linked to records.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails captured to a record are held as activity data.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes on records.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partEvents are activities on records.Has a placeEvents sync with Outlook and Google Calendar.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks are activities on records.Has a placeTasks and task plans.Carried across
Custom fieldsFields and record types the firm added itselfHeldCustom fields and custom objects, plus objects added by installed apps.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partQuote templates.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 pipelinesHeldLeads, opportunities and campaign members.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 Salesforce.
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

Intake history moves. The pipeline is rebuilt.

Intake data is the front end of a case. A lead in Salesforce carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Gladiate has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.

Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Gladiate or in the tool that feeds it.

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

Where the data is now

Salesforce will hand over an entire org as a set of CSV files, one per object, through its Data Export service. Getting the data is rarely the problem. Understanding it is: which objects the firm really used, which fields were added by an app nobody remembers installing, and how records point to one another through their IDs.

  1. The Data Export service

    An administrator can export all data as a zip archive of CSV files, weekly or monthly depending on the edition, with options to include files, attachments and document versions. The archive is deleted 48 hours after it is ready, and a large org produces several zip files. Timing the final export around those limits is part of the cutover plan.

  2. Formula fields are left out

    Formula and roll-up summary fields are always excluded from exports, because they are calculated and not stored. A firm may rely on one without knowing it is a formula, such as a count of referrals from a contact. Those are identified in the analysis and either recalculated in the destination or captured through a report.

  3. Accounts, contacts, person accounts

    Salesforce separates the organisation, an account, from the people at it, contacts. Orgs that deal with individuals may use person accounts, which are both at once and appear in the account data and the contact data. Each client is resolved to one company or one person in the destination, with the record IDs used to avoid loading anyone twice.

  4. Leads are not contacts

    A lead is an enquiry kept in its own object, apart from accounts and contacts. Leads that never progressed are prospects the firm did not take on. They are moved to the destination’s intake area if it has one, kept as a marketing list, or left in the exported files.

  5. Installed apps and legal layers

    If the org runs a legal application built on the platform, the matters, parties and time entries live in that product’s custom objects, and its vendor’s documentation describes them. The move is then planned as a move off that product, with the standard Salesforce objects as supporting data.

More about moving off Salesforce

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 Salesforce 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 Salesforce: 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 Salesforce, a final pass over a weekend picks up what changed since the trial. Salesforce 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 Salesforce 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 fromSalesforce
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 Salesforce 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

Salesforce to Gladiate: what firms ask

How do we get a full copy of our Salesforce data?

From Setup, an administrator with the Weekly Data Export permission runs Data Export and chooses Include all data, ticking the options for files and attachments. Salesforce emails a link to one or more zip files. That copy is taken once for the analysis and again at cutover.

Do our custom objects come across?

They are exported like any other object. Whether they have a home depends on the destination. A custom object that tracks referrals may map to a referral field. One that models something the new system has no idea of is carried as notes or kept in the export files, and the firm sees which before the move.

Do documents from Salesforce 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 Salesforce 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 Salesforce 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

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

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