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

Moving into a system

Migrating to Litify

Legal case management built on the Salesforce platform for plaintiff firms, insurance defence practices and in-house legal teams. This page sets out what Litify has a place for, what loading a firm’s records into it involves and what has to be set up beyond the data.

What it accepts

What has a place in Litify

Of the fourteen kinds of record that matter to a move, Litify has a place for eleven, three in part. Three could not be confirmed from its maker’s own material. A record with no place there is kept as a readable archive.

  • MattersYesMatters, by case type.
  • ContactsYesLoaded as parties and connected by roles.
  • DocumentsYesLoaded to the document component and attached to matters.
  • EmailsIn partShown on the activity timeline. How old email is loaded is confirmed in the analysis.
  • NotesTo be confirmedFile notes, matter notes and contact notes
  • CalendarYesCalendar events on the matter.
  • TasksYesTo-dos and workflow steps assigned to people
  • Time and expensesYesTime entries on the matter.
  • BillingIn partBilling is part of the product. Loading past invoices is scoped in the analysis.
  • Trust moneyTo be confirmedTrust or client account ledgers and balances
  • Firm accountsTo be confirmedGeneral ledger, office account and payables
  • Custom fieldsYesCustom fields are created before loading.
  • TemplatesIn partTemplates are rebuilt in Litify’s document generation.
  • IntakeYesLoaded as intakes.

Moving into it

Arriving in Litify

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

Beyond the data

Setting up Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

How NewLaw runs it

Four steps, in this order.

Financial records move on most routes, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in the old system and checking each trial against the old system.

  1. Analysis

    We read what the old system holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in the old system, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Litify as a trial and checked against the old system: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in the old system are frozen for an agreed window, the data is collected a final time and Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in the old system as at the cutover date. The old system is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Choose the system the firm is on now. 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

Type a few letters to find it. If it is not listed, type its name anyway.

Moving toLitify

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 your old system holds

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

Where firms come from

Routes into Litify

Each route has a page of its own: what moves, what has no place here and how the move is run.

The system

What Litify is

Litify is a legal platform built on Salesforce. It is sold to plaintiff firms that handle high volumes of intakes and matters, to insurance defence practices, to immigration practices and to corporate legal departments. The product covers intake, matter management, document management and generation, timekeeping and billing, with reporting through Salesforce and an AI layer the company calls Litify ACE.

Each customer works in a Salesforce environment with Litify installed. Intakes and matters are the main records, with parties, roles, tasks, events, time and costs attached, and a case activity timeline that shows what has happened in order. Documents are held in Litify’s document component, Docrio. Nearly every element is configurable, so one firm’s Litify can differ a good deal from another’s.

Kind
Case management
Runs as
Cloud, hosted by its maker
Made by
Litify, LLC
Mainly used in
The United States

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

Litify and the other product names and logos on this page belong to their owners and are used only to identify the systems.

Moving into Litify?

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

We reply within one business day.