Data migration route
Tabs3 to Neos migration
Tabs3 is a server-based practice management system, and Neos is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Tabs3Server- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
NeosCloud- Firm accounts: Kept as a readable archive
- 7 carried
- 5 mapped
- 1 to confirm
- 1 archived
What moves
What moves from Tabs3 to Neos
Each row is a kind of record Tabs3 holds, whether Neos has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping, one kind has no place in Neos and is archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldA matter is the part of the Client ID after the decimal point. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partPracticeMaster links documents to clients and contacts. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partPracticeMaster keeps email records in its Journal. | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partNote, phone and research records in the PracticeMaster Journal. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partIn PracticeMaster. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partIn PracticeMaster. | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldIn Tabs3 Billing, with timers in PracticeMaster. | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldIn Tabs3 Billing. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partWith the Trust Accounting module. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partWith the General Ledger and Accounts Payable modules. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partPracticeMaster Areas of Practice carry the firm’s own files and fields. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partDocument assembly in PracticeMaster; statement layouts in Billing. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partTabs3 CRM covers leads and intake and works with PracticeMaster. | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Carried across |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against Tabs3.
- Carried with mapping
- Neos holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- 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.
- Kept as a readable archive
- Neos has no place for it. It is exported in a format that opens without Tabs3 and handed to the firm as a read-only archive.
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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Neos. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Tabs3 has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without Tabs3, and kept as the record of what was billed and held.
Tabs3 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. Neos 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 Tabs3
The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.
One ID for client and matter
A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.
Everything in one directory
The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.
Standard and Platinum
The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.
Figures that are not stored
The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.
Cloud or server
Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.
Where it is going
Arriving in Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Tabs3 and checking each trial against Tabs3.
Analysis
We read what Tabs3 holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 Tabs3, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Neos as a trial and checked against Tabs3: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Tabs3 are frozen for an agreed window, the data is collected a final time and Neos 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 Tabs3 as at the cutover date. Tabs3 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 Tabs3 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 Tabs3 holds
What is in it, how its records link, and where each piece would sit in Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
Tabs3 to Neos: what firms ask
We only have Tabs3 Billing and PracticeMaster. Is that a problem?
No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.
Can we keep the client dot matter numbering?
If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.
How are the modules extracted together?
From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.
Do trust balances in Tabs3 have a place in Neos?
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 Tabs3 before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Neos has no place for?
On this route that is the firm’s accounts. They are exported from Tabs3 in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Tabs3 data is loaded into Neos?
Emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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 Tabs3 and into Neos
Other destinations from Tabs3
Other systems that move into Neos
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.
Tabs3 and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.