Data migration route
ClinicCases to Gladiate migration
ClinicCases is a server-based case management system for law school clinics, and Gladiate is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
GladiateCloud- 4 carried
- 7 to confirm
What moves
What moves from ClinicCases to Gladiate
Each row is a kind of record ClinicCases holds, whether Gladiate has a place for it, and what is planned. On this route four kinds of record carry across and seven kinds are confirmed in the analysis.
| Record | In ClinicCases | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases worked by students under supervising staff. | Has a placePersonal injury cases. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeClients, leads and referral sources. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocument storage and organisation on each case. | Has a placeFiled to the firm’s folder structure. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partInternal messages between users are kept with the case; outside email is not. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes are the main working record. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeTasks and task plans. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime keeping for the people working each case. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLeads and client sign-up. | Confirmed in the analysis |
What the plans mean
- Carried across
- Gladiate has a place for this kind of record. It is loaded there and checked against ClinicCases.
- 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.
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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. ClinicCases and Gladiate may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Gladiate, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
ClinicCases 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. Gladiate 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 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.
Where it is going
Arriving in Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.
Analysis
We read what ClinicCases holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Gladiate and checked against ClinicCases: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
After a short freeze on changes in ClinicCases, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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
Tell us what is in ClinicCases 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 ClinicCases holds
What is in it, how its records link, and where each piece would sit in Gladiate. 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 Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
ClinicCases to Gladiate: 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.
Do documents from ClinicCases keep their folders and dates in Gladiate?
Gladiate stores documents. Filed to the firm’s folder structure. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in ClinicCases have a place in Gladiate?
Most of it does on paper. Emails, notes, tasks, time entries, custom fields, templates and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Gladiate is kept as a readable archive, and you see which before the move.
What has to be decided before ClinicCases data is loaded into Gladiate?
Emails, notes, tasks, time entries, custom fields, templates and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from ClinicCases and into Gladiate
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.
ClinicCases and Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from ClinicCases to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.