Data migration route
LexPI to Soluno migration
LexPI is a case management system for personal injury work, and Soluno is a cloud accounting and billing system. Only names and any financial records have a place in a set of books, so little of this moves.
LexPICase management- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SolunoCloud- 4 carried
- 10 to confirm
What moves
What moves from LexPI to Soluno
Each row is a kind of record LexPI holds, whether Soluno has a place for it, and what is planned. On this route four kinds of record carry across and ten 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 placeAs files, with number, area of practice, responsible lawyer and billing settings. | Carried across |
| ContactsClients, other parties and referrers | HeldMatter Members: everyone in a case, with their relationship to it. | Has a placeEach contact is numbered; a file must have a primary contact. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLexFile attaches documents, scans, photos and video in folders the firm can arrange. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| 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. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldDiary of appointments and deadlines, synchronised with eLaw. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, follow-ups and staff assignments. | To be confirmed | Confirmed in the analysis |
| 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 | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeGeneral ledger; history is loaded into open periods that are then closed in order. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldLexDraft pleadings, forms and form letters that adapt to the facts of the case. | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partReferrals in and out are tracked, and cases can be recorded as rejected. | To be confirmed | Confirmed in the analysis |
What the plans mean
- Carried across
- Soluno 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
Little of this belongs in the accounts.
Soluno is an accounting package. It takes customers, suppliers, invoices and ledger entries, and has no place for documents, case notes, calendars or leads. From LexPI, that usually leaves the contact list, loaded as customers, and any financial records it happens to keep. The table above shows which. This is a small job, and it is better to say so plainly before a firm plans around it.
Loading customers into an accounting system has consequences a contact list elsewhere does not. Every customer can be invoiced, so duplicates and half-complete records turn into billing mistakes. The list is cleaned and matched against the customers already in Soluno before anything is added. The rest of what LexPI holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.
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. Soluno 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 Soluno
Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.
Numbers for contacts and files
Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.
Groups before files
File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.
Periods must be open
Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.
Closed matters need zero balances
A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.
Documents live beside it
Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.
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 Soluno. 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 Soluno 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 Soluno 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 Soluno. 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 Soluno
Loaded data is not yet a working system. This is what NewLaw sets up in Soluno, beyond the migration, so that people can work in it from the first day.
Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.
Set-up decisions in Soluno
- Chart of accounts, bank accounts and opening financial periods
- File, billing and rate groups with their default arrangements
- Contact and file numbering format, set firm-wide or by contact
- User groups and what each group may see or do
- Task and activity codes and each lawyer’s shortcuts
- Link to NetDocuments or to Actionstep practice management
Questions
LexPI to Soluno: 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 Soluno?
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 Soluno 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 Soluno?
Most of it does on paper. Documents, emails, notes, calendar entries, 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 Soluno is kept as a readable archive, and you see which before the move.
What has to be decided before LexPI data is loaded into Soluno?
Documents, emails, notes, calendar entries, 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.
Other routes
Other routes from LexPI and into Soluno
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 Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from LexPI to Soluno?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.