Data migration route
ClinicCases to SharePoint migration
ClinicCases is a server-based case management system for law school clinics, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
- Documents: Carried across
- Matters: Carried with mapping
- Contacts: Carried with mapping
- Emails: Carried with mapping
- Notes: Carried with mapping
- Calendar: Carried with mapping
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SharePointCloud- Time and expenses: Kept as a readable archive
- 1 carried
- 5 mapped
- 4 to confirm
- 1 archived
What moves
What moves from ClinicCases to SharePoint
Each row is a kind of record ClinicCases holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, five kinds need mapping, one kind has no place in SharePoint and is archived 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 place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| ContactsClients, other parties and referrers | Held | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldDocument storage and organisation on each case. | Has a placeFiles in libraries, with columns and versions. | 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. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase notes are the main working record. | Has a place in partAs documents, or as rows in a notes list if one is built. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | Held | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place in partPossible as a list; no legal workflow built in. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime keeping for the people working each case. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns and content types on libraries and lists. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as files; templates can be offered from a library. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against ClinicCases.
- Carried with mapping
- SharePoint 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
- SharePoint has no place for it. It is exported in a format that opens without ClinicCases 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from ClinicCases into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in ClinicCases.
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. SharePoint 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 SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what ClinicCases holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint 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
There is no financial cutover on this route. After a short freeze on changes in ClinicCases, a final pass over a weekend picks up what changed since the trial. 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 SharePoint. 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
SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
ClinicCases to SharePoint: 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 SharePoint?
SharePoint stores documents. Files in libraries, with columns and versions. 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.
What happens to records SharePoint has no place for?
On this route that is time entries. They are exported from ClinicCases 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 ClinicCases data is loaded into SharePoint?
Matters, contacts, emails, notes and calendar entries are carried 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 which closed matters and how many versions of a document are in scope.
Other routes
Other routes from ClinicCases and into SharePoint
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 SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from ClinicCases to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.