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

Data migration route

LexPI to SurePoint Finance Enterprise migration

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

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

What moves

What moves from LexPI to SurePoint Finance Enterprise

Each row is a kind of record LexPI holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route five kinds of record carry across and nine kinds are confirmed in the analysis.

Records in LexPI and their place in SurePoint Finance Enterprise
RecordIn LexPIIn SurePoint Finance EnterpriseWhat 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 placeCarried across
ContactsClients, other parties and referrersHeldMatter Members: everyone in a case, with their relationship to it.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldLexFile attaches documents, scans, photos and video in folders the firm can arrange.To be confirmedConfirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partEmails are listed on the matter; the integration is with Outlook.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldDiary of appointments and deadlines, synchronised with eLaw.Has a placeCalendar entries and dockets.Carried across
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.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partDisbursement tracking and settlement worksheets; hourly invoicing was not confirmed.Has a placeCarried across
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger and payables, by entity.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldLexDraft pleadings, forms and form letters that adapt to the facts of the case.To be confirmedConfirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partReferrals in and out are tracked, and cases can be recorded as rejected.To be confirmedConfirmed in the analysis

What the plans mean

Carried across
SurePoint Finance Enterprise has a place for this kind of record. It is loaded there and checked against LexPI.
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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise, 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. SurePoint Finance Enterprise 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

Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.

  1. Entities and tax IDs first

    The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.

  2. History has to balance

    Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.

  3. E-billing detail on time entries

    For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.

  4. Dockets as well as appointments

    Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.

  5. Cost recovery codes

    Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.

More about moving into SurePoint Finance Enterprise

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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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 toSurePoint Finance Enterprise

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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise

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

The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.

Set-up decisions in SurePoint Finance Enterprise

  • Entity structure, tax IDs and the chart of accounts
  • Bank and trust accounts with reconciliation set-up
  • Timekeeper rates, classifications and task code sets
  • Pre-bill approval steps and client billing rules
  • LEDES e-billing formats for each corporate client
  • Management and compensation reports the partners use

Questions

LexPI to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?

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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise?

Most of it does on paper. Documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields, templates 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.

What has to be decided before LexPI data is loaded into SurePoint Finance Enterprise?

Documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields, templates 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

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

Moving from LexPI to SurePoint Finance Enterprise?

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

We reply within one business day.