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

Data migration route

Pika CMS to Neos migration

Pika CMS is a case management system for legal aid work, and Neos is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.

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. Intake: Carried across
  8. Time and expenses: Carried with mapping
  9. Emails: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
  11. Templates: Confirmed in the analysis
ToNeosCloud
  • 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 Neos

Each row is a kind of record Pika CMS holds, whether Neos 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 Neos
RecordIn Pika CMSIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, opened from an intake.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other contacts linked to cases.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.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 placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.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 placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, which are reminders with a due date.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips recorded against cases.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.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 placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt for Neos document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with eligibility screening comes before a case is opened.Has a placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Pika CMS and Neos may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Neos, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Pika CMS and checking each trial against Pika CMS.

  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 Neos. 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 Neos 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 Neos 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

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

Neos stores documents. Case Docs tab, organised in sub-tabs. 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 Neos?

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 Neos 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 Neos?

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

Moving from Pika CMS to Neos?

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

We reply within one business day.