Data migration route
Neos to Rocket Matter migration
Neos is a cloud case management system for personal injury work, and Rocket Matter is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Rocket Matter, often from a separate accounts package.
NeosCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Trust money: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
Rocket MatterCloud- 8 carried
- 5 mapped
What moves
What moves from Neos to Rocket Matter
Each row is a kind of record Neos holds, whether Rocket Matter has a place for it, and what is planned. On this route eight kinds of record carry across and five kinds need mapping.
| 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 placeMatter File # and matter name are required on import. | Carried across |
| ContactsClients, other parties and referrers | HeldParties, providers, counsel, case contacts and related contacts. | Has a placeImported as clients or as other contact types. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldCase Docs tab with sub-tabs, viewable as a list or as folders. | Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails can be tagged to the case file. Outlook is integrated. | Has a place in partEmails can be filed to matters; it does not hold whole mailboxes. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase notes, including Special Notes. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCase calendars, with statute and deadline alerts. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldChecklists and case tasks, which feed staff dashboards. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers on a case, which can create value items. | Has a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices in PDF, Word or LEDES format. Payments through LawPay. | Has a place in partOpen balances are supported; how much invoice history loads is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust requests can be raised and paid through LawPay. | Has a placeBank accounts are created first; ledger history depth is agreed in the analysis. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldUser-defined fields can be added to case tabs. | Has a placeCustom fields and custom pages on contacts and matters. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA document generation wizard merges templates for one case or many. | Has a place in partWord merge templates are rebuilt with the product’s own merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes tab and intake forms. | Has a place in partIntake forms exist; loading open leads is confirmed in the analysis. | Carried with mapping |
What the plans mean
- Carried across
- Rocket Matter has a place for this kind of record. It is loaded there and checked against Neos.
- Carried with mapping
- Rocket Matter holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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 Rocket Matter brings those two sources together. The case records come from Neos. 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 Rocket Matter, 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.
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 Rocket Matter 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 Rocket Matter
This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.
A file number on every matter
Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.
Clients and address-book contacts
A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.
Accounting set-up comes first
Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.
Pick the document store early
Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.
One ledger of record
NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.
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 Rocket Matter. 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 Rocket Matter 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 Rocket Matter 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 Rocket Matter. 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 Rocket Matter
Loaded data is not yet a working system. This is what NewLaw sets up in Rocket Matter, beyond the migration, so that people can work in it from the first day.
Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.
Set-up decisions in Rocket Matter
- Timekeepers, matter owners and the rates each one bills at
- Matter File number format and matter templates by work type
- Bank accounts, chart of accounts and the QuickBooks Online decision
- Custom fields and custom pages for contacts and matters
- Document storage choice and the matter folder naming pattern
- Word merge templates, invoice layouts and intake forms
Questions
Neos to Rocket Matter: 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 Rocket Matter?
Yes. Rocket Matter keeps trust ledgers. Bank accounts are created first; ledger history depth is agreed in the analysis. 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 Rocket Matter?
On paper, yes: each kind of record Neos holds has a place in Rocket Matter. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Neos data is loaded into Rocket Matter?
Emails, billing records, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. 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 Rocket Matter
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 Rocket Matter are the names and marks of their owners, used here only to identify the two systems.
Moving from Neos to Rocket Matter?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.