Data migration route
Clio Manage to Neos migration
Clio Manage 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.
Clio ManageCloud- 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 Clio Manage to Neos
Each row is a kind of record Clio Manage 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 | HeldOpen, Pending or Closed, with a display number built from a firm-wide numbering scheme. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldPerson and company contacts; related contacts link other parties to a matter. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored under contacts and matters in folders, with version history. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook as email logs, or forwarded to a matter and stored as EML files. | 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 | HeldMatter notes and contact notes. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime entries and expense entries are both called activities. | 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 | HeldBills move from draft through approval to unpaid and paid. | 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 | HeldTrust funds can be held at client level or matter level. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partClio Accounting is a separate Clio product, documented for the US and Canada. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldMatter and contact custom fields, shared with Clio Grow. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates with merge fields, made from Word, Excel, PowerPoint and PDF files. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partLead pipeline and intake forms are in Clio Grow, a companion product. | 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 Clio Manage.
- 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 Clio Manage 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 Clio Manage 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 Clio Manage, 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 Clio Manage 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 Clio Manage is kept running until the checks on Neos are finished.
Where the data is now
Leaving Clio Manage
Leaving Clio Manage is mostly a question of what comes out and in what form. Clio’s export page produces spreadsheets of contacts, matters, notes, tasks, calendar entries and time, and balances come from reports. Documents and billing history are not in those spreadsheets, so they are collected separately and joined back to the right matters.
The display number can change
A matter’s display number is built from a firm-wide scheme: matter number, client name, year and other parts in a chosen order. An administrator can change the scheme and apply it to every existing matter. The number in the export may therefore differ from the one on older letters. We check the Client Reference field as well.
Trust held at client level
Clio lets a firm hold trust funds against the client as a whole, not only against a matter. Many trust ledgers elsewhere are strictly per matter. Each client-level balance then has to be allocated to a matter before cutover, and the accounts team makes that allocation in Clio so the closing report already shows it.
Activities and communications
Time entries and expense entries are both called activities and export as separate lists. Filed emails and phone logs are communications. An email forwarded to a matter’s Maildrop address is stored as an EML file, while one filed from Outlook is an email log. The analysis counts each kind, since they land in different places.
Documents may sit outside Clio
Files can be stored in Clio itself or in a connected service. With the OneDrive for Business integration, for example, Clio creates a root folder with a subfolder for every client and matter. Before planning the document move we establish which store each office has been saving to, and whether both hold files.
Draft bills at cutover
A bill in Clio is a draft, pending approval, unpaid or paid, and a draft does not yet count towards the client’s balance. Before the final collection the accounts team approves or discards every draft. The debtor figure taken across is then the one on Clio’s accounts receivable report, with no half-finished bills behind it.
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 Clio Manage and checking each trial against Clio Manage.
Analysis
We read what Clio Manage 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 Clio Manage, 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 Clio Manage: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Clio Manage 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 Clio Manage as at the cutover date. Clio Manage 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 Clio Manage 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 Clio Manage 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
Clio Manage to Neos: what firms ask
Can our matter numbers stay the same when we leave Clio?
The destination decides. If it accepts a supplied matter number, the Clio display number is loaded as it stands. Because Clio’s scheme can include the client’s name, some firms take the chance to shorten it. Where the new system insists on its own numbering, the Clio number is kept in a reference field.
Does our billing history come out of Clio?
Time and expense entries export as lists, and outstanding balances come from the accounts receivable report. Whether the new system can hold past invoices as invoices depends on that system. Where it cannot, we agree with the firm how the history is kept: as PDF copies on each matter, or in the archived Clio data.
We also use Clio Grow. Is that a separate job?
It is a separate product with its own data, so it is scoped separately. Matters already converted from Grow exist in Clio Manage and move with it. What remains in Grow is the pipeline: leads not yet hired, intake forms and signed engagement documents. The analysis shows how much of that the firm still needs.
Do trust balances in Clio Manage 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 Clio Manage 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 Clio Manage 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 Clio Manage 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 Clio Manage and into Neos
Other destinations from Clio Manage
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.
Clio Manage and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from Clio Manage 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.