Data migration route
MyCase to Neos migration
MyCase is a cloud 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.
MyCaseCloud- 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 MyCase to Neos
Each row is a kind of record MyCase 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 | HeldCalled cases. Each has a unique name, an optional case number, a practice area and an open or closed state. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts (people) and companies are separate record types, linked to cases. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored against cases in folders, with version tracking and unlimited storage. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly emails linked through the Outlook or Gmail add-ins or a forwarding address. | 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 | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCan sync with Google Calendar and Outlook. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks can be created by workflow automation. | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held | 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 | Held | 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 | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partMyCase Accounting is an add-on; a QuickBooks sync is the alternative. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields on cases and on contacts. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldWord-based document templates and automation. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads in a Kanban view, with intake forms that can be embedded on a website. | 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 MyCase.
- 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 MyCase 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 MyCase 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 MyCase, and kept as the record of what was billed and held.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of MyCase 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 MyCase is kept running until the checks on Neos are finished.
Where the data is now
Leaving MyCase
A firm leaving MyCase is moving a set of cases with everything tied to them, and the first job is working out which of those ties the next system can hold. Documents, time, invoices and trust balances have obvious homes. Portal messages, text conversations and the lead pipeline often do not, so each is given a destination or a reason to stay behind before any data is extracted.
Cases, contacts and companies
MyCase says case where most systems say matter, and it keeps people and companies as two separate record types. A destination that has one contact card for both, or that insists on a client record above each matter, needs a rule for which MyCase contact becomes the client when a case has several linked to it.
Case numbers are optional
The case number is a free-text field that a firm can leave empty or fill with a court file number. If the new system wants a unique matter number on every record, the analysis finds the cases with no number or a shared one, and the firm agrees how those are numbered.
Only linked emails are there
Emails reach a case through the Gmail or Outlook add-ins, or by forwarding to a personal MyCase address. Anything nobody linked is still in a mailbox, and emails the software could not match wait in an Unresolved Emails queue. That queue is worth clearing before extraction, because unmatched emails have no case to travel with.
Books may sit elsewhere
Invoices, payments and trust ledgers are inside MyCase. The general ledger is either the MyCase Accounting add-on or QuickBooks fed by a sync. Where QuickBooks is in use, debtor and trust totals are taken from both and compared before cutover, so the opening figures in the new system are ones the bookkeeper recognises.
Messages and texts
Client portal messages and text conversations are saved against the case. Few systems have a matching record type. They are usually carried as a dated note or a single document on each matter, and the firm sees an example of how that reads before deciding whether it is enough.
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 MyCase and checking each trial against MyCase.
Analysis
We read what MyCase 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 MyCase, 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 MyCase: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in MyCase 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 MyCase as at the cutover date. MyCase 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 MyCase 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 MyCase 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
MyCase to Neos: what firms ask
Can we keep our existing matter numbers when we move to MyCase?
Yes. The case number field accepts letters, digits and special characters, so numbers can go in exactly as they are. MyCase does not require the number to follow a pattern. What it does require is a unique case name, so the naming rule usually takes more discussion than the numbering.
We are leaving MyCase. Do our client portal messages come with us?
They can be kept, but rarely as live messages. Most systems have no record that matches a MyCase portal thread, so the messages are carried as dated notes or one document per matter. Whether the destination has anything closer is confirmed in the analysis, and the firm sees a sample first.
What happens to closed cases?
They move as closed, with their closed date, documents and billing history where the destination has a place for it. Some firms bring across only matters closed within a set number of years and keep the older ones in the read-only copy of the old system. That choice is made before the trial load.
Do trust balances in MyCase 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 MyCase 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 MyCase 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 MyCase 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 MyCase and into Neos
Other destinations from MyCase
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.
MyCase and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from MyCase 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.