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

Data migration route

PracticeMaster to Litify migration

PracticeMaster is a server-based case management system, and Litify is a cloud one. The records line up case for case, and the detail is in the fields and stages.

FromPracticeMasterServer
  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. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Notes: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PracticeMaster to Litify

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

Records in PracticeMaster and their place in Litify
RecordIn PracticeMasterIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient file mirrored with Tabs3 Billing, one record per Client ID.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 systemHeldDocument Management records link files to a client or contact, with check-out and versions.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldEmail records in the Journal, created through the Outlook integration.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 notesHeldNote, phone call and research records in the Journal.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldFirm-wide calendar with Outlook integration and calendar plan templates.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks and reminders on the calendar.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTimer records and fees that pass to Tabs3 Billing.Has a placeTime entries on the matter.Carried across
Custom fieldsFields and record types the firm added itselfHeldAreas of Practice with the firm’s own files and fields.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly with Word or HotDocs, WorkFlows and calendar plan templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partTabs3 CRM handles leads and intake and passes them to PracticeMaster.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 PracticeMaster.
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. PracticeMaster 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.

PracticeMaster 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

PracticeMaster is the part of Tabs3 that looks most like other practice systems, and the part firms have customised most. Contacts, calendar and journal records move in a familiar way. The detail is in the Areas of Practice the firm built, the documents it linked, and the WorkFlows it depends on, none of which have the same shape in another product.

  1. Areas of Practice are tables

    Each Area of Practice has its own files, and firms add files and fields through File Maintenance. A probate area might hold assets and heirs, a family area children and hearings. These can hold many rows for one matter. Every file is listed with its row counts, and each needs a home or a decision.

  2. The Journal mixes record types

    Timer records, phone calls, emails, research and notes are all stored in one Journal file, told apart by a record type. Destinations usually split those into time entries, emails and file notes. Journal records are sorted by type on the way out, so a timer record already billed is not loaded a second time as a note.

  3. Documents are linked, with versions

    The Document Management file links documents to a client or contact, with check-out, check-in and versions. Each record is only the link, and the document is a file on the firm’s storage. PracticeMaster has its own verify function for these links, and it is run before extraction so broken ones are known.

  4. Template paths by practice area

    Document assembly templates sit in a Template Path for each Area of Practice, by default a DOCS folder under that area, and may be Word or HotDocs templates. Their merge codes refer to PracticeMaster fields. Templates are rebuilt against the new system’s fields, starting with the ones produced most often.

  5. WorkFlows and calendar plans

    WorkFlows fire when records are added or changed, and calendar plan templates lay down a series of dated events. Events already created come across as calendar entries. The automation itself is described and rebuilt with the destination’s own tools, because rules do not transfer between products.

More about moving off PracticeMaster

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

  1. Analysis

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

  4. Cutover

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

PracticeMaster to Litify: what firms ask

Do emails saved from Outlook come across?

Emails saved through the Outlook integration become journal records on the client. They are loaded to the matter as emails where the destination has an email record, otherwise as dated notes with the message saved as a file.

We want to keep PracticeMaster and replace billing. Is that possible?

The two are tied by mirrored client files and only integrate when installed together. Replacing Billing alone breaks the flow of fees from PracticeMaster. If the plan is to split them, the analysis sets out the manual steps that would stand in for the link, and what they cost in staff time.

What happens to conflict searching?

Conflict searching in PracticeMaster reads the fields the firm marked for it, across clients, contacts and linked documents. After the move, searches run in the new system over the migrated contacts and matters. Names that lived only in free text or old documents are worth a check, since they may not be indexed the same way.

Do documents from PracticeMaster keep their folders and dates in Litify?

Litify stores documents. Loaded to the document component and attached to matters. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in PracticeMaster have a place in Litify?

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

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

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

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