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

Moving off a system

Migrating from 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 holds, what moving off it involves and where its records can go.

Where it can go

Routes from Litify

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

What it holds

The records Litify keeps

Fourteen kinds of record matter to a move. Litify keeps eleven of them, one in part, and three could not be confirmed from its maker’s own material.

  • MattersYesMatters, with parties, calendar events, tasks, time and costs attached.
  • ContactsYesParties, connected to intakes and matters through roles.
  • DocumentsYesHeld in Litify’s document component, with tags, versions and templates.
  • EmailsIn partEmails appear on the case activity timeline. Mailboxes stay in the mail system.
  • NotesTo be confirmedFile notes, matter notes and contact notes
  • CalendarYesCalendar events on the matter and the activity timeline.
  • TasksYesTasks, including those generated by matter plans.
  • Time and expensesYesTimekeeping, with time entries tied to the matter.
  • BillingYesBilling and eBilling, aimed chiefly at insurance defence work.
  • Trust moneyTo be confirmedTrust or client account ledgers and balances
  • Firm accountsTo be confirmedGeneral ledger, office account and payables
  • Custom fieldsYesFields are added through Salesforce configuration.
  • TemplatesYesDocument templates with conditional logic. Matter plans automate tasks.
  • IntakeYesIntakes with questionnaires, lead scoring and marketing source tracking.

Moving off it

Leaving Litify

A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.

  1. Parties and roles

    A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.

  2. Intakes become matters

    An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.

  3. Documents sit beside the records

    Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.

  4. Injury detail in related records

    Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.

  5. Automation stays behind

    Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.

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

How NewLaw runs it

Four steps, in this order.

Financial records move on most routes, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Litify holds and how its records link, then agree with you, field by field, where each piece will sit in the new system. 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 Litify, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Litify are frozen for an agreed window, the data is collected a final time and the new system 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 Litify as at the cutover date. Litify 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 where the Litify data is going, or tell us you have not decided. 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 fromLitify

Not decided yet is a fine answer.

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

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

After the move

Setting up the system you move to

A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.

Questions

Moving off Litify: what firms ask

Do we need a Salesforce administrator to get our data out?

Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.

Are our documents included when Litify data is exported?

Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.

We are moving to Litify. Who does the configuration?

Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.

Where to start

Still deciding where to move?

Choose the system before you plan the move, and see where AI fits once your data is in it.

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 off Litify?

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

We reply within one business day.