Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

ClinicCases data to SQLite

ClinicCases is a server-based case management system for law school clinics, and SQLite 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.

FromClinicCasesServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Time and expenses: Exported in full
  6. Documents: Exported with mapping
  7. Emails: Exported with mapping
  8. Tasks: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
  10. Templates: Confirmed in the analysis
  11. Intake: Confirmed in the analysis
ToSQLiteFiles
  • 5 carried
  • 2 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ClinicCases to SQLite

Each row is a kind of record ClinicCases holds, whether SQLite has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping and four kinds are confirmed in the analysis.

Records in ClinicCases and their place in SQLite
RecordIn ClinicCasesIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases worked by students under supervising staff.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldHas a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocument storage and organisation on each case.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
EmailsEmails saved to matters or to the storeHeld in partInternal messages between users are kept with the case; outside email is not.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldCase notes are the main working record.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldHas a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime keeping for the people working each case.Has a placeA table of time and expense entries.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns added to the table they belonged to.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedNo placePrecedent files are kept in folders, not in the database.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeAn enquiries table, where the source tracked them.Confirmed in the analysis

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against ClinicCases.
Exported with mapping
SQLite 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 SQLite 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 SQLite has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

More about moving off ClinicCases

Where it is going

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

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.

  1. Analysis

    We read what ClinicCases holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything ClinicCases holds is in scope unless you take it out.

  2. 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.

  3. Trial export

    The data is written to SQLite 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromClinicCases
Moving toSQLite

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what ClinicCases holds

    What is in it, how its records link, and where each piece would sit in SQLite. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

SQLite 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.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

ClinicCases to SQLite: 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 SQLite hold documents from ClinicCases?

In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without ClinicCases.

Does everything in ClinicCases have a place in SQLite?

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 SQLite is kept as a readable archive, and you see which before the move.

What has to be decided before ClinicCases is written out to SQLite?

Documents and 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.

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.

How we do itDiscovery to rollout, step by step

ClinicCases and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from ClinicCases to SQLite?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.