Data migration route
LexPI to SimpleLaw migration
LexPI is a case management system for personal injury work, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.
LexPICase management- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SimpleLawCloud- 8 carried
- 2 mapped
- 4 to confirm
What moves
What moves from LexPI to SimpleLaw
Each row is a kind of record LexPI holds, whether SimpleLaw has a place for it, and what is planned. On this route eight kinds of record carry across, two kinds need mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters move through stages; statute of limitation and other critical dates are held. | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldMatter Members: everyone in a case, with their relationship to it. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLexFile attaches documents, scans, photos and video in folders the firm can arrange. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails are listed on the matter; the integration is with Outlook. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldDiary of appointments and deadlines, synchronised with eLaw. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, follow-ups and staff assignments. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime Records are listed among the data on a matter. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partDisbursement tracking and settlement worksheets; hourly invoicing was not confirmed. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeGeneral ledger stays in QuickBooks or another accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldLexDraft pleadings, forms and form letters that adapt to the facts of the case. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partReferrals in and out are tracked, and cases can be recorded as rejected. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against LexPI.
- Carried with mapping
- SimpleLaw 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 SimpleLaw 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 SimpleLaw, 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. SimpleLaw 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
Leaving LexPI
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what LexPI holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into SimpleLaw as a trial and checked against LexPI: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LexPI are frozen for an agreed window, the data is collected a final time and SimpleLaw 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what LexPI holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
LexPI to SimpleLaw: 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 SimpleLaw?
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 SimpleLaw 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 SimpleLaw?
Most of it does on paper. Emails, 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before LexPI data is loaded into SimpleLaw?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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.
Other routes
Other routes from LexPI and into SimpleLaw
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
LexPI and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from LexPI to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.