Data migration route
Neos to Soluno migration
Neos is a cloud 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.
NeosCloud- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: 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
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SolunoCloud- 5 carried
- 8 to confirm
What moves
What moves from Neos to Soluno
Each row is a kind of record Neos holds, whether Soluno has a place for it, and what is planned. On this route five kinds of record carry across and eight kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases laid out in tabs, with a Management tab for fee and referral details. | Has a placeAs files, with number, area of practice, responsible lawyer and billing settings. | Carried across |
| ContactsClients, other parties and referrers | HeldParties, providers, counsel, case contacts and related contacts. | Has a placeEach contact is numbered; a file must have a primary contact. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldCase Docs tab with sub-tabs, viewable as a list or as folders. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | HeldEmails can be tagged to the case file. Outlook is integrated. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes, including Special Notes. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCase calendars, with statute and deadline alerts. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldChecklists and case tasks, which feed staff dashboards. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers on a case, which can create value items. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices in PDF, Word or LEDES format. Payments through LawPay. | Has a place | Carried across |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust requests can be raised and paid through LawPay. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldUser-defined fields can be added to case tabs. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldA document generation wizard merges templates for one case or many. | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes tab and intake forms. | 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 Neos.
- 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 Neos, 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 Neos 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 Neos 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 Neos is kept running until the checks on Soluno are finished.
Where the data is now
Leaving Neos
A firm leaving Neos is leaving a cloud system whose data sits in a database dedicated to that firm. The structure runs tab by tab, and each tab is in effect a table. Many Neos firms came from Needles or Trialworks, so the data often carries conventions two systems old, and the analysis has to read those as well.
A database per firm
Assembly holds each firm’s records in a separate Azure SQL database. For a migration that means the data set is self-contained, with nothing shared with other customers. How a copy is obtained is arranged with the firm at the start, and the copy and the document files are taken at the same point in time.
Value items hold the money
Bills, costs, time and settlement entries are value items on the Value tab, with transactions beneath them for payments. A general system splits those across disbursements, time, invoices and receipts. Each value code is mapped to one of them, and the case totals are compared before and after.
Fields inherited from Trialworks
When a Trialworks firm is converted to Neos, some standard fields land in user-defined fields and in document sub-tabs named after the old tabs. A firm that has been through that carries two layers of structure. Both are read, so a field that looks custom is recognised as the old system’s standard field.
Checklists and calendars
Work in progress is split between checklist items and case calendar entries, and dashboards are built from both. Open checklist items become tasks in the destination. Calendar entries become events. The two are counted separately in the trial load, because losing either leaves a fee earner with an empty list on the first morning.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Neos 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 Neos, 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 Neos: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Neos are frozen for an agreed window, the data is collected a final time and Soluno goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Neos 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 Neos 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 Neos 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
Neos to Soluno: what firms ask
We have seen NEOS Web and NEOS DB listed. Are they different from Neos?
Assembly’s own site describes a single product, Neos, used in a browser, with each firm’s records in a dedicated Azure SQL database. Some software lists show NEOS Web and NEOS DB as separate entries. Which system a firm actually holds, and where its data sits, is identified at the start of the analysis.
We are on Needles. Is Neos just an upgrade?
No, it is a migration. Needles keeps its data in a SAP ASE database on the firm’s server and Neos uses Azure SQL in the cloud, so records and documents are converted, not upgraded in place. Assembly says the case logic is the same, which shortens the mapping compared with a move elsewhere.
Can Neos replace our accounting system?
Not the general ledger. Neos records case money as value items, raises invoices and trust requests, and takes payments through LawPay, and it links to QuickBooks Desktop or Online for the books. A firm moving from a system with built-in accounting plans a QuickBooks set-up as part of the same project.
Do trust balances in Neos have a place in Soluno?
Yes. Soluno keeps trust ledgers. Balances are loaded by matter and agreed to the trust report from Neos as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in Neos have a place in Soluno?
Most of it does on paper. Documents, emails, notes, calendar entries, tasks, 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 Neos data is loaded into Soluno?
Documents, emails, notes, calendar entries, tasks, 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 Neos 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.
Neos and Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from Neos 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.