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

Data migration route

PerfectLaw to Litify migration

PerfectLaw is a server-based 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.

FromPerfectLawServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Time and expenses: Carried across
  6. Intake: Carried across
  7. Emails: Carried with mapping
  8. Billing: Carried with mapping
  9. Templates: Carried with mapping
  10. Notes: Confirmed in the analysis
  11. Tasks: 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
  • 6 carried
  • 3 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PerfectLaw to Litify

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

Records in PerfectLaw and their place in Litify
RecordIn PerfectLawIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases are managed in AIM, the Attorney’s Information Manager.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldParties are related to matters by defined relationships for conflict checks.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldIts own document management system; reports can be profiled into it.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail profiling tools are listed among its applications.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 deadlinesHeldCalendars and dockets.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldIncludes collections and billing compliance tools.Has 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 balancesHeldTrust history by matter within client, for each trust account.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger and accounts payable, with profit centres.To 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 automationHeldForms and document assembly.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partA matter intake workflow for opening new matters.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 PerfectLaw.
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 PerfectLaw 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 PerfectLaw, and kept as the record of what was billed and held.

PerfectLaw runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Litify is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

PerfectLaw is one database doing the work of four or five products. A firm leaving it is replacing its case management, document store, billing, general ledger and accounts payable at once, often with two or three separate systems. The plan has to say which destination takes which part, and how the links between them, especially client and matter numbers, are kept.

  1. One source, several destinations

    Front office and back office share a database. If the firm is moving to a practice management system plus a separate accounting package, the single source is split in two. Client and matter identifiers must be identical in both destinations, so they are fixed first and every extract is keyed on them.

  2. Matter within client

    Trust history is kept by matter within client, and the rest of the system follows the same client and matter structure. A destination that numbers matters independently of clients needs a rule for combining the two. We settle that rule with the accounts team, since their reports and bank records use the existing numbers.

  3. Scanned invoices and cheques

    The accounts payable side can store scanned supplier invoices and images of signed cheques, linked to vendors, matters and clients. These are financial records, not matter documents. They are counted separately and usually go to the accounting package or a finance archive, with the link to the vendor kept in the file name or index.

  4. Records management by barcode

    PerfectLaw lists records management with barcodes among its front office applications, for tracking physical files. If the firm uses it and the new system has no records module, the file locations are loaded into custom fields on the matter or handed to the records team as a register.

  5. A segmented general ledger

    The general ledger uses multi-segment account numbers and can distribute overhead among profit centres. An accounting package with a flat chart of accounts needs those segments translated into its own tracking categories or classes. The firm’s accountant agrees the new chart before opening balances are prepared.

More about moving off PerfectLaw

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

  1. Analysis

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

  4. Cutover

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

PerfectLaw to Litify: what firms ask

Can everything in PerfectLaw go into one new system?

Sometimes, if the destination includes full accounting. More often the firm ends up with a practice management system and an accounting package, and perhaps a document management system. The analysis lists every PerfectLaw function the firm uses and shows which destination covers it, so nothing is assumed.

What happens to documents in the PerfectLaw DMS?

They are extracted with whatever profile data the document store keeps for them, such as client and matter. In the destination each document is filed to its matter, into a folder derived from the profile where folders are used. Reports that were profiled into the document store are identified, since most are not matter documents.

We are in PerfectLaw’s hosted cloud. Does that change anything?

It changes who provides the copy. A firm with its own server gives us access with its IT provider. A firm in the vendor’s hosted environment asks the vendor for the database and documents. The checks afterwards are the same, and a read-only copy still needs a home once hosting ends.

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

Most of it does on paper. Notes, tasks, 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 PerfectLaw data is loaded into Litify?

Emails, billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, 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

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

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