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

Data migration route

Pika CMS to Clio Manage migration

Pika CMS is a case management system for legal aid work, and Clio Manage is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Clio Manage, 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 with mapping
  8. Emails: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
  10. Templates: Confirmed in the analysis
ToClio ManageCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 6 carried
  • 1 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Pika CMS to Clio Manage

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

Records in Pika CMS and their place in Clio Manage
RecordIn Pika CMSIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, opened from an intake.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other contacts linked to cases.Has a placePeople and companies, with related contacts linked to matters by a separate template.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 under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldAppointments and dated reminders.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, which are reminders with a due date.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips recorded against cases.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedOpen-source code that a program could extend; confirmed per installation.Has a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with eligibility screening comes before a case is opened.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Pika CMS.
Carried with mapping
Clio Manage 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
Clio Manage has no place for it. It is exported in a format that opens without Pika CMS 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

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 Clio Manage 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 Clio Manage, 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. Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

Pika CMS to Clio Manage: 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 Clio Manage?

Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. 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 Clio Manage has no place for?

On this route that is intake records. They are exported from Pika CMS 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 Pika CMS data is loaded into Clio Manage?

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

Moving from Pika CMS to Clio Manage?

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

We reply within one business day.