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

Data migration route

PracticePanther to Litify migration

PracticePanther is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromPracticePantherCloud
  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. Emails: Carried with mapping
  9. Billing: Carried with mapping
  10. Custom fields: Carried with mapping
  11. Templates: Carried with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PracticePanther to Litify

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

Records in PracticePanther and their place in Litify
RecordIn PracticePantherIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters belong to a contact and are Open, Pending or Closed. Numbering is one firm-wide sequence.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldA contact can be a company holding several people. Prospects are contacts with a tag.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldStored in the account, or synced with Box, Dropbox, Google Drive or OneDrive.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails archived by the Gmail or Outlook add-in, or sent to a MailSync address.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldSyncs with Google and Outlook calendars; court rules through LawToolBox.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow templates create tasks and events.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldHas a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partOperating accounts and a chart of accounts come with the PantherAccounting Plus plan.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields on contacts and matters, which can be grouped.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldUploaded Word templates filled from merge fields.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms create or update contacts; prospects are tracked with tags.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 PracticePanther.
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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from PracticePanther has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without PracticePanther, and kept as the record of what was billed and held.

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

Where the data is now

PracticePanther is flexible about how a firm files things, and each firm has used that freedom differently. One uses tags for practice areas, another for referral sources, a third for both. Leaving it starts with reading how this particular account was set up: what the tags mean, what Pending was used for, and whether clients were entered as people or as companies.

  1. Contacts hold several people

    A contact can be one person, or a company with a primary contact and others added beneath it. Systems that keep organisations and individuals as separate cards need each company contact split apart, with the links kept. The person who receives the invoices is not always the primary contact, so billing addresses are checked as part of this.

  2. One number sequence

    Automatic matter numbers run in a single sequence across the firm and cannot restart for each client. Contacts can be numbered the same way. A destination that uses a client number followed by a matter number needs new numbers generated, and the PracticePanther number is kept on each record as a reference.

  3. What Pending means here

    Matters have three statuses: Open, Pending and Closed. Firms use Pending for different things. For some it is a prospect who has not signed, for others a file waiting on a court. The firm confirms its own meaning, and pending matters are mapped to leads, open matters or a custom status accordingly.

  4. Emails arrive by MailSync

    Every contact and every matter has its own MailSync address, and an email copied to that address is attached with its attachments. The Gmail and Outlook add-ins do the same from the inbox. Some emails are therefore attached to a contact and no matter. Those need a rule for where they go.

  5. Tags carry the meaning

    Tags mark contacts as clients, prospects or professional contacts, and firms add their own for lead source, practice group or anything else they report on. A destination may offer matter types, categories and custom fields in their place. Each tag in use is listed with a count, and the firm decides what it becomes.

More about moving off PracticePanther

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 PracticePanther and checking each trial against PracticePanther.

  1. Analysis

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

  4. Cutover

    Changes in PracticePanther 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 PracticePanther as at the cutover date. PracticePanther 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 PracticePanther 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 fromPracticePanther
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 PracticePanther 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

PracticePanther to Litify: what firms ask

We use PantherAccounting Plus. What extra has to be planned?

It adds the operating side. With that plan the firm keeps a chart of accounts, journal entries and bank reconciliations in PracticePanther as well as trust. Those need a destination that does accounting, or a separate package. Without the plan, only trust and billing balances have to be carried.

Our documents sync to Box. Where are the real files?

In both places. The sync puts the files in the firm’s Box account as well as in PracticePanther. Whether the two agree is checked in the analysis. Often the Box account is the simplest source for the files, with PracticePanther telling us which matter each folder is for.

Will intake form submissions come across?

Where the answers a client gave on an intake form were written into contact fields and custom fields, they move with the contact. Form designs do not transfer. They are rebuilt in the new system’s own form tool, if it has one, using the same questions.

Do trust balances in PracticePanther 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 PracticePanther 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 PracticePanther have a place in Litify?

Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 PracticePanther data is loaded into Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and the firm’s accounts 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

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

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