Data migration route
ClinicCases data to Full data export
ClinicCases is a server-based case management system for law school clinics, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what ClinicCases holds and keeps it readable and open to queries.
- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Time and expenses: Exported in full
- Emails: Exported with mapping
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
Full data exportFiles- 6 carried
- 1 mapped
- 4 to confirm
What moves
What moves from ClinicCases to Full data export
Each row is a kind of record ClinicCases holds, whether Full data export has a place for it, and what is planned. On this route six kinds of record carry across, one kind needs mapping and four 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 placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | Held | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldDocument storage and organisation on each case. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | Held in partInternal messages between users are kept with the case; outside email is not. | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase notes are the main working record. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks with assignee, due date and status. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime keeping for the people working each case. | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeExtra columns under their original field names. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplate files only; the merge fields in them will not run. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place in partAn enquiries table, where the source tracked leads. | Confirmed in the analysis |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against ClinicCases.
- Exported with mapping
- Full data export 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.
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
Not a new system. A complete copy the firm can query.
Writing ClinicCases out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in ClinicCases as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in ClinicCases stays untouched until the copy in Full data export has been checked.
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 Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what ClinicCases holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything ClinicCases holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against ClinicCases: record counts, totals where ClinicCases holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in ClinicCases, the export is run a final time and checked again. There is nothing to go live. ClinicCases is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Full data export. 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
Structure, permissions and handover
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
ClinicCases to Full data export: 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.
Does the copy in Full data export hold documents from ClinicCases?
Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in ClinicCases as at the export date.
Does everything in ClinicCases have a place in Full data export?
Most of it does on paper. Tasks, 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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before ClinicCases is written out to Full data export?
Emails are exported with mapping, so each mapping is agreed with you first. Tasks, custom fields, templates and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from ClinicCases and into Full data export
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 Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from ClinicCases to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.