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

Data migration route

Pika CMS to MyCase migration

Pika CMS is a case management system for legal aid work, and MyCase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in MyCase, often from a separate accounts package.

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

What moves

What moves from Pika CMS to MyCase

Each row is a kind of record Pika CMS holds, whether MyCase has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping and three kinds are confirmed in the analysis.

Records in Pika CMS and their place in MyCase
RecordIn Pika CMSIn MyCaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, opened from an intake.Has a placeAs cases, with name, number, practice area, open and closed dates and lead attorney.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other contacts linked to cases.Has a placePeople and companies load separately and are then linked to cases.Carried across
DocumentsFiles stored in or linked from the systemHeld in partFile upload is documented for the later OCM release; what an older install holds varies.Has a placeFiled in folders under each case.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partSaved emails can be filed to a case; it does not hold mailboxes.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldAppointments and dated reminders.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, which are reminders with a due date.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips recorded against cases.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfTo be confirmedOpen-source code that a program could extend; confirmed per installation.Has a placeFields are created on cases or contacts before records are loaded.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt as Word documents with MyCase merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with eligibility screening comes before a case is opened.Has a place in partLeads and intake forms exist; loading open leads in bulk is confirmed in the analysis.Carried with mapping

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to MyCase brings those two sources together. The case records come from Pika CMS. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in MyCase, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

How Pika CMS is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Pika CMS 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. MyCase 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

A program still on Pika is running open-source software that has since been continued under other names. The first question is which version is installed and who looks after it, because any program was free to change the code. The data is a MySQL database on a server somebody controls, and the work starts by finding out what that particular installation holds.

  1. Which Pika is it

    The names are confusing: Pika, OCM, Open Case Management and Ciprocity are one line of software at different dates. A site that says it uses Pika may be on an old release or on a later one that kept the old name on screen. The version is read from the installation itself before any mapping is planned.

  2. Code the program changed itself

    Because the licence is open, a program or its contractor could add fields, screens and reports directly in the code. Those additions are in no manual. The database is compared table by table with a standard installation, and anything extra is traced to the screen that fills it so its meaning is understood before it is mapped.

  3. A server someone must find

    The application and its MySQL database run on a web server, sometimes in the program’s office and sometimes with a hosting company arranged years ago. Access to that server, and to wherever uploaded files are kept, has to be confirmed early. Staff changes mean the person who set it up has often left.

  4. Funding and problem codes

    Legal services programs code each case by legal problem and by the grant that pays for it, and report to funders from those codes. A general practice system has a matter type and little else. The code lists are carried across as they are, with their history, so that past reporting periods can still be reproduced.

More about moving off Pika CMS

Where it is going

Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.

  1. Every case name is unique

    MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.

  2. Old numbers fit as they are

    The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.

  3. Open or closed, nothing between

    A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.

  4. Practice areas build themselves

    On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.

  5. Lead attorney must exist

    The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.

More about moving into MyCase

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 Pika CMS holds and how its records link, then agree with you, field by field, where each piece will sit in MyCase. 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 Pika CMS, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Pika CMS are frozen for an agreed window, the data is collected a final time and MyCase 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 Pika CMS as at the cutover date. Pika CMS 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 Pika CMS 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 fromPika CMS
Moving toMyCase

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 Pika CMS holds

    What is in it, how its records link, and where each piece would sit in MyCase. 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 MyCase

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

A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.

Set-up decisions in MyCase

  • Practice areas and custom fields for cases and contacts
  • Trust and operating bank accounts with opening balances per case
  • Word document templates rebuilt with MyCase merge fields
  • Intake forms and lead pipeline for each practice area
  • User roles and who can open which cases
  • QuickBooks sync or the MyCase Accounting add-on

Questions

Pika CMS to MyCase: what firms ask

Is Pika the same as OCM and Ciprocity?

They are the same line of software. Pika was the original open-source product. It was continued as Open Case Management, and the current hosted version is called Ciprocity. The record structure is closely related across all three, but an old Pika installation will not have features added later, so each site is assessed as it stands.

Our Pika was customised years ago. Does that matter?

It matters a good deal, and it is manageable. Custom fields and local code changes are found by comparing the database with a standard one. Each is shown to staff who use it, given a destination or marked to stay behind, and included in the trial load so the result can be checked against the old screens.

Can we move from Pika to a commercial practice system?

Cases, contacts, notes and time have places in most systems. Eligibility screening, funding codes and funder reports usually do not. Before choosing, it is worth listing the reports the program must still produce after the move, because that list often decides which kind of system fits.

Do documents from Pika CMS keep their folders and dates in MyCase?

MyCase stores documents. Filed in folders under each case. 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 Pika CMS have a place in MyCase?

Most of it does on paper. Emails, custom fields and templates 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 MyCase is kept as a readable archive, and you see which before the move.

What has to be decided before Pika CMS data is loaded into MyCase?

Intake records are carried with mapping, so each mapping is agreed with you first. Emails, custom fields and templates 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

Pika CMS and MyCase are the names and marks of their owners, used here only to identify the two systems.

Moving from Pika CMS to MyCase?

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

We reply within one business day.