Moving off a system
Migrating from ClinicCases
Open-source, web-based case management written for law school clinics, with case notes, student journals and time keeping; now discontinued. This page sets out what ClinicCases holds, what moving off it involves and where its records can go.
Where it can go
Routes from ClinicCases
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep7 of 11 kinds of record have a place
Centerbase7 of 11 kinds of record have a place
Clio Manage7 of 11 kinds of record have a place
MyCase7 of 11 kinds of record have a place
Rocket Matter7 of 11 kinds of record have a place
SimpleLaw6 of 11 kinds of record have a place
Smokeball7 of 11 kinds of record have a place
SurePoint Finance Enterprise4 of 11 kinds of record have a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box3 of 11 kinds of record have a place
Dropbox3 of 11 kinds of record have a place
Google Drive3 of 11 kinds of record have a place
OneDrive3 of 11 kinds of record have a place
Server drives3 of 11 kinds of record have a place
SharePoint6 of 11 kinds of record have a place
Sync.com3 of 11 kinds of record have a place
What it holds
The records ClinicCases keeps
Fourteen kinds of record matter to a move. ClinicCases keeps seven of them, one in part, and four could not be confirmed from its maker’s own material.
- MattersYesCases worked by students under supervising staff.
- ContactsYesClients, other parties and referrers
- DocumentsYesDocument storage and organisation on each case.
- EmailsIn partInternal messages between users are kept with the case; outside email is not.
- NotesYesCase notes are the main working record.
- CalendarYesAppointments, court dates and deadlines
- TasksTo be confirmedTo-dos and workflow steps assigned to people
- Time and expensesYesTime keeping for the people working each case.
- BillingNoNot in the project’s feature list.
- Trust moneyNoNot among the features the project lists.
- Firm accountsNoNo accounting functions are listed by the project.
- Custom fieldsTo be confirmedFields and record types the firm added itself
- TemplatesTo be confirmedPrecedents, document templates and automation
- IntakeTo be confirmedLeads, enquiries, intake forms and pipelines
Moving off it
Leaving ClinicCases
ClinicCases has been discontinued, and its author advises clinics still using it to consider another system. The software sits on a server the law school runs, which means the database and the documents are within reach. What needs thought is the material a law firm system has no idea of: student journals, a large roll of former students as users, and messages kept inside the case.
Student journals
Students write journals in the system and supervisors read and comment on them. A journal is a teaching record, not a client record, and it may fall under the school’s student privacy rules. The clinic decides early whether journals are archived by the school, exported for each supervisor, or left in the read-only copy.
Hundreds of former students
Every semester adds users who work a few cases and then leave. Their names are on the case notes and time they recorded. The new system does not need a licence for each of them, but the authorship must survive. Former students can be loaded as inactive users or written into the note text.
Messages inside the case
The messaging system was built so that discussion about a case stays with the case and off personal email. Those threads are part of the history a supervisor relies on. Few systems have an equivalent record. They are normally carried as dated notes on the matter, in order, with sender and recipients named.
The server it runs on
The published requirements are Linux, Apache, MySQL and PHP 5.2 or higher, and development has stopped. Some installations will be on server software the university’s IT team wants retired. A full copy of the database and the document folder, taken early, means the move does not depend on the old server staying up.
The system
What ClinicCases is
ClinicCases is an open-source case management system designed for law school clinics, written by Judson Mitchell and published under the MIT licence. Its website now states that the product has been discontinued after seventeen years, and the code repository says development has stopped and that users should consider moving to another system.
It is a PHP and MySQL application installed on a Linux web server, usually one run by the law school, and used in a browser. Cases hold contacts, case notes, documents and calendar events. Around them sit things only a teaching clinic needs: a journal for each student that supervisors read and comment on, and an internal messaging system.
- Kind
- Case management, law school clinics
- Runs as
- On the firm’s server or a hosted server
- Made by
- Judson Mitchell (Three Pipe Problem, LLC)
- Mainly used in
- The United States
- Also known as
- Clinic Cases
- Status
- Discontinued
How NewLaw runs it
Four steps, in this order.
Financial records move on most routes, so the balances are rehearsed before the real cutover.
Analysis
We read what ClinicCases holds and how its records link, then agree with you, field by field, where each piece will sit in the new system. 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 ClinicCases, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into the new system as a trial and checked against ClinicCases: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in ClinicCases are frozen for an agreed window, the data is collected a final time and the new system 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 ClinicCases as at the cutover date. ClinicCases is kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Choose where the ClinicCases data is going, or tell us you have not decided. 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 ClinicCases holds
What is in it, how its records link, and where each piece would sit in the new system. 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.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
- Actionstep
- Box
- Centerbase
- Clio Manage
- Dropbox
- Filevine
- Full data export
- Gladiate
- Google Drive
- iManage Cloud
- Lawmatics
- LexWorkplace
- Litify
- Microsoft SQL Server
- MyCase
- Neos
- NetDocuments
- OneDrive
- QuickBooks Online
- Rocket Matter
- Server drives
- SharePoint
- SimpleLaw
- SmartAdvocate
- Smokeball
- Soluno
- SQLite
- SurePoint Finance Enterprise
- Sync.com
Questions
Moving off ClinicCases: what firms ask
ClinicCases is discontinued. How long can we stay on it?
The software keeps running as long as its server does, but development has stopped. An update to the server’s operating system or PHP version can leave it unable to run. A sensible order is to take a full copy of the database and documents now, then choose the new system without a deadline forcing the choice.
Do student time records need to come across?
That depends on what the clinic uses them for. If hours are reported for course credit or to a funder, they are loaded against each case with the student’s name and the date. If they were only a teaching aid, a summary per student per semester is often enough, and the detail stays in the archive.
Can a law firm practice system work for a clinic?
For the cases, yes: clients, notes, documents and deadlines are the same work. The teaching side is where it differs. Journals, supervisor review and a new intake of users every semester are not things a firm system expects, so the clinic should decide how each will be handled before picking a destination.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
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.
ClinicCases and the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off ClinicCases?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.