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

Data migration route

LexPI to NetDocuments migration

LexPI is a case management system for personal injury work, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromLexPICase management
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Templates: Carried with mapping
  5. Tasks: Confirmed in the analysis
  6. Trust money: Confirmed in the analysis
  7. Firm accounts: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Billing: Kept as a readable archive
  6. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 2 mapped
  • 4 to confirm
  • 6 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LexPI to NetDocuments

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

Records in LexPI and their place in NetDocuments
RecordIn LexPIIn NetDocumentsWhat 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 place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldMatter Members: everyone in a case, with their relationship to it.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldLexFile attaches documents, scans, photos and video in folders the firm can arrange.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails are listed on the matter; the integration is with Outlook.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldDiary of appointments and deadlines, synchronised with eLaw.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, follow-ups and staff assignments.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeld in partTime Records are listed among the data on a matter.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partDisbursement tracking and settlement worksheets; hourly invoicing was not confirmed.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.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 partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partReferrals in and out are tracked, and cases can be recorded as rejected.No placeKept as a readable archive

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against LexPI.
Carried with mapping
NetDocuments 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.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without LexPI and handed to the firm as a read-only archive.

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from LexPI is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces LexPI for matters and billing, or into an archive.

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. NetDocuments 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 into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what LexPI holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into NetDocuments and checked against LexPI: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in LexPI, a final pass over a weekend picks up what changed since the trial. 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 toNetDocuments

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

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

LexPI to NetDocuments: 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 NetDocuments?

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 NetDocuments turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records NetDocuments has no place for?

On this route that is contacts, notes, calendar entries, time entries, billing records and intake records. They are exported from LexPI in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

Matters and templates are carried with mapping, so each mapping is agreed with you first. Tasks, trust ledgers, the firm’s accounts and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from LexPI to NetDocuments?

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

We reply within one business day.