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

Data migration route

PCLaw to Litify migration

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

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

What moves

What moves from PCLaw to Litify

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

Records in PCLaw and their place in Litify
RecordIn PCLawIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter has a number and a nickname; closed matters get a closed matter number.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 systemHeld in partDocument Manager, when enabled in System Settings, holds documents and PDF bills against matters.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas 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 notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldAppointments, tasks and important dates.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldBillable and non-billable time and matter expenses.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldPre-bills, invoices, payments and receivables.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 balancesHeldClient trust ledgers across multiple trust bank accounts, with three-way reconciliation.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, vendor payments and multiple general bank accounts inside the product.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 automationHeldMerge templates for documents and forms; invoice templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLoaded as intakes.Confirmed in the analysis

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against PCLaw.
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 PCLaw 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 PCLaw, and kept as the record of what was billed and held.

PCLaw 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

PCLaw has been on sale for more than 40 years, and a firm that has used it for a good part of that time has deep books and a long matter list. The move is led by the accounting: trust ledgers, unbilled time and expenses, receivables and the general ledger are taken at a month end and agreed to PCLaw’s own reports. Matter details, contacts and any documents follow, matched on the matter number.

  1. CTREE or SQL Server

    Help, About PCLaw, License shows which database engine the firm is on. CTREE keeps the data as files in a working folder that can be copied. The SQL Server version keeps it in MDF and LDF database files. Either engine may sit behind the same release, so the About screen is checked and the version number is not taken as the answer.

  2. Numbers, years and Enterprise

    Releases were numbered, with PCLaw 13 to 16 covered by one backup guide, and are now named by year. A firm that says it has PC Law 2014 or 2021 is naming a release, not a different product. PCLaw Enterprise is a separate edition that needs full SQL Server. Release and edition are written down at the start.

  3. Nicknames and closed numbers

    Staff find matters by nickname as often as by number, and a closed matter carries a second number from the Closed Matter Register. A destination usually has room for one matter number. The nickname and the closed number are kept as searchable references, or the index to the archive room stops making sense.

  4. The ledger is inside

    Unlike systems that hand the books to Xero or QuickBooks, PCLaw has its own general ledger, vendor payments and bank accounts. If the destination has no ledger, the books move to an accounting package and the practice system takes the matter side. That split is decided in the analysis, with the firm’s accountant involved.

  5. Document Manager is optional

    Documents are only inside PCLaw if Document Manager was enabled in System Settings. Where it was, PDF copies of bills can be saved there against the matter. Firms that never enabled it keep their documents in folders or in another program, and that becomes a further source for the same move.

More about moving off PCLaw

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

  1. Analysis

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

  4. Cutover

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

PCLaw to Litify: what firms ask

Can we move without upgrading PCLaw first?

Usually. The data is read from the release the firm has, provided the program still opens and a backup restores cleanly. An upgrade is only suggested when the installed release cannot be read as it stands, or when the books need a repair that has to be done inside PCLaw.

We are in Canada. Does that change the move?

The product is the same, but the trust rules and tax are not. Canadian firms carry GST, HST or provincial tax on fees and disbursements, and law society trust reports must still be producible for past periods. The old PCLaw is kept read only so those reports can be run after cutover.

Does all our billing history come across?

Open invoices and unbilled work have to, because the firm still bills and collects them. Paid invoices can be loaded in summary where the destination accepts historical bills. Where Document Manager holds PDF copies of bills, those are filed to the matter as well, so a client’s question about an old account can be answered without opening PCLaw.

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

Most of it does on paper. Emails, notes, trust ledgers, the firm’s accounts, custom fields and intake records 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 PCLaw data is loaded into Litify?

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

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

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