Data migration route
Pika CMS to Filevine migration
Pika CMS is a case management system for legal aid work, and Filevine is a cloud case management system. The records line up case for case, and the detail is in the fields and stages.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Intake: Carried with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
FilevineCloud- 6 carried
- 2 mapped
- 3 to confirm
What moves
What moves from Pika CMS to Filevine
Each row is a kind of record Pika CMS holds, whether Filevine has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and three kinds are confirmed in the analysis.
| Record | In Pika CMS | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, opened from an intake. | Has a placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, opposing parties and other contacts linked to cases. | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partFile upload is documented for the later OCM release; what an older install holds varies. | Has a placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld in the activity feed of the project. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a placeHeld as notes in the activity feed. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments and dated reminders. | Has a placeDeadlines and calendar events. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, which are reminders with a due date. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimeslips recorded against cases. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmedOpen-source code that a program could extend; confirmed per installation. | Has a placeCustom sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake with eligibility screening comes before a case is opened. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Pika CMS.
- Carried with mapping
- Filevine 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 Filevine 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 Filevine, 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. Filevine 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
Leaving Pika CMS
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.
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.
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.
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.
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.
Where it is going
Arriving in Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
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 Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Filevine 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.
Cutover
Changes in Pika CMS are frozen for an agreed window, the data is collected a final time and Filevine 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Pika CMS holds
What is in it, how its records link, and where each piece would sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Pika CMS to Filevine: 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 Filevine?
Filevine stores documents. Docs section with folders. Templated project folders can be set per type. 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 Filevine?
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 Filevine 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 Filevine?
Time entries and 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.
Other routes
Other routes from Pika CMS and into Filevine
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Pika CMS and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Pika CMS to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.