Data migration route
LegalServer to Clio Manage migration
LegalServer is a cloud case management system for legal aid work, and Clio Manage is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Clio Manage, often from a separate accounts package.
LegalServerCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
Clio ManageCloud- Intake: Kept as a readable archive
- 7 carried
- 3 mapped
- 3 to confirm
- 1 archived
What moves
What moves from LegalServer to Clio Manage
Each row is a kind of record LegalServer holds, whether Clio Manage has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases and matters, with case types configured for each site. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and the other people connected with a case. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored on the case, or linked from SharePoint, Google Shared Drives or Dropbox. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partBuilt-in email, and email sent to a case from Gmail through an integration. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments, events, tasks and deadlines; entries can show in Outlook. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeTasks have a migration template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeeping, used for grant and funder reporting. | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| BillingInvoices, payments and debtor balances | To be confirmedBuilt for free legal services; client invoicing was not confirmed. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldSites add their own fields, forms and processes without code. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldBuilt-in document templates; HotDocs, Docassemble and Gavel are integrations. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldConfigurable client intake, with a poverty level assessment and conflict check. | No placeLeads and intake forms belong in Clio Grow. | Kept as a readable archive |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against LegalServer.
- Carried with mapping
- Clio Manage 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
- Clio Manage has no place for it. It is exported in a format that opens without LegalServer 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
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 Clio Manage brings those two sources together. The case records come from LegalServer. 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 Clio Manage, 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 LegalServer 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 LegalServer is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving LegalServer
Each agency configures its own intake, case types and fields, so a move off LegalServer starts with that site’s configuration, not with a standard list of tables. The data most at risk is the data a commercial practice system never asks for: eligibility answers, funding codes, outcomes and the time recorded against each grant.
Each site has its own shape
Intake processes, case types and data fields are set up by the agency’s own administrators, often over many years. Two programs on the same product can hold quite different records. The analysis reads this site’s configuration first and lists every field that holds data, including ones no current staff member remembers adding.
Time belongs to funders
Timekeeping exists to show funders what their grant paid for, so entries are tied to grants and funding sources, not to a bill. A practice system records time against a matter for invoicing. The funding link has to be carried as its own field, or grant reports for the period before the move cannot be reproduced.
Documents may live elsewhere
LegalServer can store files itself, or link a case to folders in SharePoint, Google Shared Drives or Dropbox. On a site that uses those integrations the documents are not in the case management system at all. Where the files are is established before anything else, because it decides whether they are moved or simply linked again.
Eligibility and outcome data
Intake assesses a client against the poverty level and runs a conflict check, and outcomes are tracked across cases for reporting. These answers justify the service to an auditor. They are carried as fields where the destination allows, and otherwise as a dated intake summary filed on the case.
Feeds from courts and agencies
Some sites receive court data several times a day, create cases from a county system, or send counselling data to HUD. These connections are part of how the office works. Each is listed with what it sends or receives, and a decision is made on whether it is rebuilt, replaced by manual entry, or retired.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what LegalServer holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. 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 LegalServer, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Clio Manage as a trial and checked against LegalServer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LegalServer are frozen for an agreed window, the data is collected a final time and Clio Manage 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 LegalServer as at the cutover date. LegalServer 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 LegalServer 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 LegalServer holds
What is in it, how its records link, and where each piece would sit in Clio Manage. 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
LegalServer to Clio Manage: what firms ask
Can a commercial practice system hold legal aid data?
It can hold the cases, people, notes, documents and time. It will not have funding codes, eligibility screening or funder reports unless they are built with custom fields and reports. The analysis sets out which of those can be rebuilt in the chosen system and which reporting would have to be done outside it.
What happens to cases closed years ago?
Closed cases matter in legal aid for conflict checks and for funder audits. Bringing every case means a returning client or an adverse party is still found. If older cases are left out, their names should still be loaded for conflict searching, and the full record stays in the read-only copy.
Our documents are in SharePoint, not in LegalServer. Must they move as well?
Not necessarily. If LegalServer only links to SharePoint, the files are already in the program’s own Microsoft 365. They can stay where they are and be linked from the new system, or be moved into it. The choice depends on how the destination stores documents and is made in the analysis.
Do trust balances in LegalServer have a place in Clio Manage?
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 LegalServer before the plan is fixed. If Clio Manage 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 Clio Manage has no place for?
On this route that is intake records. They are exported from LegalServer 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 LegalServer data is loaded into Clio Manage?
Time entries, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Billing records, trust ledgers and the firm’s accounts 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 LegalServer and into 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.
LegalServer and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from LegalServer to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.