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

Data migration route

ClinicCases to Lawmatics migration

ClinicCases is a server-based case management system for law school clinics, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.

FromClinicCasesServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Documents: Carried with mapping
  6. Emails: Carried with mapping
  7. Time and expenses: Carried 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
ToLawmaticsCloud
  • 4 carried
  • 3 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ClinicCases to Lawmatics

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

Records in ClinicCases and their place in Lawmatics
RecordIn ClinicCasesIn LawmaticsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases worked by students under supervising staff.Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldHas a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeldDocument storage and organisation on each case.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried 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 partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes are the main working record.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeldHas a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime keeping for the people working each case.Has a place in partTime entries and expenses, where the Time & Billing module is enabled.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeMatter, contact and company fields. A field must exist before data is imported into it.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placePipelines and stages, marketing sources and campaigns.Confirmed in the analysis

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against ClinicCases.
Carried with mapping
Lawmatics 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

People and history move. Files and accounts stay.

A CRM wants to know who the firm knows and what has passed between them. From ClinicCases that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.

A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in ClinicCases or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.

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

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what ClinicCases holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.

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

  3. Trial load

    The data is loaded into Lawmatics as a trial and checked against ClinicCases: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in ClinicCases are frozen for an agreed window, the data is collected a final time and Lawmatics 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

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 toLawmatics

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

Setting up Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

ClinicCases to Lawmatics: 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 Lawmatics?

In part. Files and folders on each matter, added by upload or API, not by the spreadsheet import. The structure in ClinicCases is mapped to what Lawmatics offers and you see the mapping before the load. File dates are carried.

Does everything in ClinicCases have a place in Lawmatics?

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

What has to be decided before ClinicCases data is loaded into Lawmatics?

Documents, emails and time 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 sets the cutover date and how much financial history comes across as live records.

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 Lawmatics are the names and marks of their owners, used here only to identify the two systems.

Moving from ClinicCases to Lawmatics?

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

We reply within one business day.