Data migration route
Neos to Centerbase migration
Neos is a cloud case management system for personal injury work, and Centerbase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Centerbase, 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
- Billing: Carried across
- Trust money: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
CenterbaseCloud- 10 carried
- 3 mapped
What moves
What moves from Neos to Centerbase
Each row is a kind of record Neos holds, whether Centerbase has a place for it, and what is planned. On this route ten kinds of record carry across and three 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 placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | HeldParties, providers, counsel, case contacts and related contacts. | Has a placeClients, related parties and prospects. | 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 placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | 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 saved to matters; mailboxes stay in Microsoft 365. | 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 place | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices in PDF, Word or LEDES format. Payments through LawPay. | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Carried across |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust requests can be raised and paid through LawPay. | Has a placeMultiple trust and retainer accounts per matter or client. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldUser-defined fields can be added to case tabs. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA document generation wizard merges templates for one case or many. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes tab and intake forms. | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Carried across |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Neos.
- Carried with mapping
- Centerbase 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 Centerbase 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 Centerbase, 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 Centerbase 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 Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
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 Centerbase. 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 Centerbase 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 Centerbase 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 Centerbase. 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
Neos to Centerbase: 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 Centerbase?
Yes. Centerbase keeps trust ledgers. Multiple trust and retainer accounts per matter or client. 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 Centerbase?
On paper, yes: each kind of record Neos holds has a place in Centerbase. 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 Centerbase?
Emails, custom fields and templates 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 Centerbase
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 Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Neos to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.