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

Data migration route

LexPI to MyCase migration

LexPI is a case management system for personal injury work, and MyCase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in MyCase, often from a separate accounts package.

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

What moves

What moves from LexPI to MyCase

Each row is a kind of record LexPI holds, whether MyCase 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 LexPI and their place in MyCase
RecordIn LexPIIn MyCaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters move through stages; statute of limitation and other critical dates are held.Has a placeAs cases, with name, number, practice area, open and closed dates and lead attorney.Carried across
ContactsClients, other parties and referrersHeldMatter Members: everyone in a case, with their relationship to it.Has a placePeople and companies load separately and are then linked to cases.Carried across
DocumentsFiles stored in or linked from the systemHeldLexFile attaches documents, scans, photos and video in folders the firm can arrange.Has a placeFiled in folders under each case.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails are listed on the matter; the integration is with Outlook.Has a place in partSaved emails can be filed to a case; it does not hold mailboxes.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldDiary of appointments and deadlines, synchronised with eLaw.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, follow-ups and staff assignments.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime Records are listed among the data on a matter.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partDisbursement tracking and settlement worksheets; hourly invoicing was not confirmed.Has a place in partAn outstanding balance per case is supported; fuller invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeBalances by client and case; the depth of ledger history is agreed first.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a place in partOnly with the MyCase Accounting add-on or a linked QuickBooks file.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeFields are created on cases or contacts before records are loaded.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldLexDraft pleadings, forms and form letters that adapt to the facts of the case.Has a place in partTemplates are rebuilt as Word documents with MyCase merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partReferrals in and out are tracked, and cases can be recorded as rejected.Has a place in partLeads and intake forms exist; loading open leads in bulk is confirmed in the analysis.Carried with mapping

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to MyCase brings those two sources together. The case records come from LexPI. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in MyCase, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

How LexPI is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. LexPI 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. MyCase 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

LexPI was written for one kind of work in one state, and its records show it. A matter holds vehicles, insurance policies, liens, damages and a settlement worksheet, and its calendar is fed by the New York courts through eLaw. Leaving it means finding a home for each of those, and replacing two things that are functions and not data: the pleadings generator and the court feed.

  1. Pleadings stay behind

    LexDraft writes a summons and complaint from the facts on the file, asking questions as it goes, and holds hundreds of New York pleadings and forms. The documents it has produced are files and move with the matter. The logic that produced them does not, so the firm plans how pleadings will be drafted from the first day.

  2. eLaw feeds the diary

    Adjournments and court activity arrive in the diary automatically from eLaw. After the move, existing appearances are loaded as calendar entries with their court details. New ones will only arrive if the destination has its own eLaw connection. If it has none, someone must enter them, and that duty is assigned before go-live.

  3. Settlement worksheets

    The settlement screen works out the figures from the gross or net recovery, disbursements, liens, referral fees and the terms of the retainer, and the result goes in with the closing statement to OCA. The inputs are loaded as separate fields. The worksheet for each settled matter is also saved as a document.

  4. Stages and stalled cases

    Every matter sits in a stage, and the program reports which have been in their current stage too long or have had no activity. The stage and the date it was entered are both carried across. Without the date, the new system cannot tell a case that stalled last year from one that moved yesterday.

  5. Folders that copy the paper file

    Document folders in LexPI can be arranged to mirror the firm’s paper files, and clips can be scans, photographs, spreadsheets or video. That folder layout is kept. Large media files are counted and sized in the analysis, because photographs and video are where document storage limits in a new system are reached first.

More about moving off LexPI

Where it is going

Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.

  1. Every case name is unique

    MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.

  2. Old numbers fit as they are

    The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.

  3. Open or closed, nothing between

    A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.

  4. Practice areas build themselves

    On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.

  5. Lead attorney must exist

    The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.

More about moving into MyCase

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what LexPI holds and how its records link, then agree with you, field by field, where each piece will sit in MyCase. 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 LexPI, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into MyCase as a trial and checked against LexPI: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in LexPI are frozen for an agreed window, the data is collected a final time and MyCase 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 LexPI as at the cutover date. LexPI 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 LexPI 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 fromLexPI
Moving toMyCase

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 LexPI holds

    What is in it, how its records link, and where each piece would sit in MyCase. 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 MyCase

Loaded data is not yet a working system. This is what NewLaw sets up in MyCase, beyond the migration, so that people can work in it from the first day.

A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.

Set-up decisions in MyCase

  • Practice areas and custom fields for cases and contacts
  • Trust and operating bank accounts with opening balances per case
  • Word document templates rebuilt with MyCase merge fields
  • Intake forms and lead pipeline for each practice area
  • User roles and who can open which cases
  • QuickBooks sync or the MyCase Accounting add-on

Questions

LexPI to MyCase: what firms ask

Will our statute of limitations dates be safe?

They are treated as the most important dates on the file. Each is mapped to a date field or calendar entry in the new system, not to a note. On each trial load the limitation dates on open matters are compared with LexPI, and differences are resolved before cutover.

Can we still generate New York pleadings after moving?

Not with LexDraft, which is part of LexPI. The new system’s document automation can be set up with the firm’s own pleadings, using the fields that were migrated. That is implementation work beside the data migration. The firm chooses which documents matter most, and those are built and tested first.

What happens to liens and insurance details?

Liens, insurance policies and vehicles are separate records on a LexPI matter. A personal injury system will have places for them. A general practice system will need custom fields or related records. Which applies is confirmed in the analysis, and Medicare lien details are checked on a sample of matters in every trial load.

Do trust balances in LexPI have a place in MyCase?

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 LexPI before the plan is fixed. If MyCase 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 LexPI have a place in MyCase?

Most of it does on paper. 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 MyCase is kept as a readable archive, and you see which before the move.

What has to be decided before LexPI data is loaded into MyCase?

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

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

Moving from LexPI to MyCase?

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

We reply within one business day.