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

Data migration route

CasePacer to Litify migration

CasePacer is a cloud case management system for personal injury work. Litify is a case management system, run the same way. The records line up case for case, and the detail is in the fields and stages.

FromCasePacerCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried across
  7. Intake: Carried across
  8. Templates: Carried with mapping
  9. Emails: Confirmed in the analysis
  10. Notes: Confirmed in the analysis
  11. Billing: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Custom fields: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 1 mapped
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CasePacer to Litify

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

Records in CasePacer and their place in Litify
RecordIn CasePacerIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with master cases connecting related mass tort claims.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldHas a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldCloud storage reached through CP Hub as a mapped drive. CP Link tracks versions.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedEmail integration is advertised. What is stored against a case was not confirmed.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes and an activity log on each case.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar inside the case, with Outlook syncing.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask workflows that run automatically.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense tracking by case.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument templates and task workflows.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake is part of the case workflow. Clients complete smart forms in CP Direct.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against CasePacer.
Carried with mapping
Litify 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

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. CasePacer and Litify 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 Litify, 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 CasePacer 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 CasePacer is kept running until the checks on Litify are finished.

Where the data is now

A CasePacer move is a personal injury or mass tort data set leaving a cloud system: cases, parties, insurers, treatment and settlement figures, and a large volume of documents. The size of the docket matters more than the number of users, because a mass tort firm can hold thousands of near-identical claims under a handful of master cases.

  1. Master cases and their claims

    A mass tort is held as a master case with the individual claims connected beneath it. That connection is what lets the firm see one litigation as a whole. Each destination models this differently, as related matters, a project or a group, so the structure is agreed first and the claims are loaded against it.

  2. Files seen through CP Hub

    Staff open documents through CP Hub, a mapped drive in File Explorer, so the folder layout they see is the working structure. That layout is recorded case by case before extraction, and the folder a document sat in is kept, since paralegals find medical records and pleadings by where they were filed.

  3. Version history in CP Link

    CP Link keeps versions of a document as it is edited. Whether earlier versions can be extracted, and whether the destination keeps versions at all, is settled in the analysis. Where they cannot be carried as versions, the current one is loaded and the earlier ones are filed beside it with a dated name.

  4. Client uploads from CP Direct

    Clients send photos, videos and documents from their phones through CP Direct, and answer questionnaires that write straight into the case. Those uploads arrive without a firm naming convention. They are marked as client-supplied in the new system, so evidence from the plaintiff is not mixed in with correspondence the firm produced.

More about moving off CasePacer

Where it is going

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.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, 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 CasePacer and checking each trial against CasePacer.

  1. Analysis

    We read what CasePacer 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 CasePacer, 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 CasePacer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in CasePacer 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 CasePacer as at the cutover date. CasePacer 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 CasePacer 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 fromCasePacer
Moving toLitify

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

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

Questions

CasePacer to Litify: what firms ask

How are master cases handled in a system that has no such thing?

The claims become ordinary cases and the connection is rebuilt with whatever the destination offers: a related-matter link, a group field, or a parent record. Reports that ran across the whole litigation are rebuilt on that link. The trial load is checked by counting claims under each master case on both sides.

Will the folders we see in File Explorer look the same afterwards?

The folder names and the documents in them can be reproduced. How staff reach them will change, because the mapped drive belongs to CasePacer. Some destinations offer a desktop sync or a document add-in, and others work only in the browser. That difference is shown to the firm before it chooses, not after.

Do closed cases have to move?

No. Settled cases can come across in full, come across as a summary with their documents, or stay in an export the firm keeps. The usual test is how often a closed case is reopened for a lien query or a later claim. That choice is the firm’s, and the scope is written down before the trial load.

Do trust balances in CasePacer have a place in Litify?

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 CasePacer before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in CasePacer have a place in Litify?

Most of it does on paper. Emails, notes, billing records, trust ledgers, the firm’s accounts 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before CasePacer data is loaded into Litify?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, billing records, trust ledgers, the firm’s accounts and custom fields are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

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

Moving from CasePacer to Litify?

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

We reply within one business day.