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

Data migration route

Pika CMS to LexWorkplace migration

Pika CMS is a case management system for legal aid work, and LexWorkplace is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromPika CMSCase management
  1. Documents: Carried across
  2. Notes: Carried across
  3. Matters: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
  7. Templates: Confirmed in the analysis
ToLexWorkplaceCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Time and expenses: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in LexWorkplace
  • 2 carried
  • 1 mapped
  • 4 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Pika CMS to LexWorkplace

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

Records in Pika CMS and their place in LexWorkplace
RecordIn Pika CMSIn LexWorkplaceWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, opened from an intake.Has a place in partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields.Carried with mapping
ContactsClients, other parties and referrersHeldClients, opposing parties and other contacts linked to cases.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
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 to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeOn the matter’s Email tab, in their own folders.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeldAppointments and dated reminders.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, which are reminders with a due date.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips recorded against cases.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedOpen-source code that a program could extend; confirmed per installation.Has a place in partOld categories can become document types, statuses or tags.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partStored as files in Firm Documents.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with eligibility screening comes before a case is opened.No placeKept as a readable archive

What the plans mean

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. LexWorkplace has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Pika CMS is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that LexWorkplace cannot hold goes to whatever replaces Pika CMS for matters and billing, or into an archive.

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

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace 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 it is organised, then agree with you where each kind of record will sit in LexWorkplace. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into LexWorkplace and checked against Pika CMS: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Pika CMS, a final pass over a weekend picks up what changed since the trial. 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 toLexWorkplace

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

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

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

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

LexWorkplace stores documents. Filed to a matter or to Firm Documents, in folders. 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 LexWorkplace has no place for?

On this route that is contacts, calendar entries, time entries and 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 LexWorkplace?

Matters are carried with mapping, so each mapping is agreed with you first. Emails, tasks, custom fields and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Moving from Pika CMS to LexWorkplace?

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

We reply within one business day.