Data migration route
LexWorkplace to Soluno migration
LexWorkplace is a cloud document management system, 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.
LexWorkplaceCloud- Matters: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SolunoCloud- 1 carried
- 6 to confirm
What moves
What moves from LexWorkplace to Soluno
Each row is a kind of record LexWorkplace holds, whether Soluno has a place for it, and what is planned. On this route one kind of record carries across and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partName, custom matter ID, client, type, location, assigned staff, tags, open and close dates. | Has a placeAs files, with number, area of practice, responsible lawyer and billing settings. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldAny file type, in folders within a matter, with type, status, tags and versions. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | HeldSaved to a matter from Outlook, with their own folders on the matter’s Email tab. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldRich-text Matter Notes, kept beside the matter’s documents and email. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partFirm-defined document types, statuses, tags and matter types. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partTemplates are stored as files in Firm Documents and copied into matters. | 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 LexWorkplace.
- 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 LexWorkplace, 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 LexWorkplace holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LexWorkplace depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to LexWorkplace is kept running until the checks on Soluno are finished.
Where the data is now
Leaving LexWorkplace
A matter can be exported from LexWorkplace as a zip file, with its documents and emails in the folder structure the firm built. That export leaves out three things that usually matter: the matter notes, the matter’s own details, and earlier versions of documents. A full move collects those separately and joins them back to the right matter before anything is loaded elsewhere.
What the matter export omits
Export Matter gives a Documents folder and an Email folder. Matter Notes are not in it, nor are previous versions, nor the matter’s custom ID, client, type, staff and dates. Matter details can be exported to CSV from the matters list. The plan sets out how notes and versions are obtained, and whether older versions are needed at all.
Custom Matter ID is the key
LexWorkplace lets a firm give each matter a custom ID so that it matches the number in the practice management system. Where firms have used it consistently, documents line up with matters in the destination by that number. Where it is blank or free-typed, matters are matched by name and client, and the doubtful ones are listed.
Automatic versioning adds up
By default every save from Word makes a new numbered version, so a heavily edited contract can carry dozens. Firms on manual versioning have fewer, numbered 1.0, 1.1, 2.0. The analysis reports version counts so the firm can choose between bringing all of them, the latest only, or the latest plus the first.
Trash and archive states
Each matter, folder and item is active, archived or in the Trash Bin. Archived content stays in place but is not indexed or searched, and a matter export includes trashed items that have not been permanently deleted. Both need a decision before extraction, or deleted drafts reappear in the new system.
Firm Documents sit outside matters
Templates, policies and other internal files are kept in Firm Documents, which behaves like a matter but belongs to no client. It has no single export button: items are selected and downloaded. It is easy to leave off the list, and it is where the firm’s own templates are kept.
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.
Nothing financial lands in Soluno on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what LexWorkplace holds and how it is organised, then agree with you where each kind of record will sit in Soluno. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Soluno and checked against LexWorkplace: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in LexWorkplace, a final pass over a weekend picks up what changed since the trial. LexWorkplace 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 LexWorkplace 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 LexWorkplace 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
LexWorkplace to Soluno: what firms ask
Does the matter export include our notes and old versions?
No. LexWorkplace’s own help says an exported matter contains documents and email, and does not include Matter Notes, matter details or previous versions of documents. Matter details can be exported to CSV separately. If notes and versions are needed in the next system, they are collected another way, and that is scoped in the analysis.
We use Clio Manage with LexWorkplace. What moves where?
Clio holds the clients, contacts, time, bills and trust records. LexWorkplace holds the documents, emails and notes, linked matter to matter. If both are being replaced, the two are extracted separately and joined on the matter. If only one is changing, the link to the other has to be rebuilt against the new matter numbers.
Do documents from LexWorkplace keep their folders and dates 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 LexWorkplace before the plan is fixed. Documents that have no place in Soluno are exported into folders by client and matter.
Does everything in LexWorkplace have a place in Soluno?
Most of it does on paper. Documents, emails, notes, tasks, custom fields and templates 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 LexWorkplace data is loaded into Soluno?
Documents, emails, notes, tasks, custom fields and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from LexWorkplace 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.
LexWorkplace and Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from LexWorkplace 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.