Data migration route
Pika CMS to SurePoint Finance Enterprise migration
Pika CMS is a case management system for legal aid work, and SurePoint Finance Enterprise is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SurePoint Finance Enterprise, often from a separate accounts package.
- Matters: Carried across
- Contacts: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SurePoint Finance EnterpriseCloud- 4 carried
- 7 to confirm
What moves
What moves from Pika CMS to SurePoint Finance Enterprise
Each row is a kind of record Pika CMS holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route four kinds of record carry across and seven 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 place | Carried across |
| ContactsClients, other parties and referrers | HeldClients, opposing parties and other contacts linked to cases. | Has a place | 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. | To be confirmed | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldAppointments and dated reminders. | Has a placeCalendar entries and dockets. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, which are reminders with a due date. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimeslips recorded against cases. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | To be confirmedOpen-source code that a program could extend; confirmed per installation. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake with eligibility screening comes before a case is opened. | To be confirmed | Confirmed in the analysis |
What the plans mean
- Carried across
- SurePoint Finance Enterprise has a place for this kind of record. It is loaded there and checked against Pika CMS.
- 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise, 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. SurePoint Finance Enterprise 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 SurePoint Finance Enterprise
Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.
Entities and tax IDs first
The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.
History has to balance
Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.
E-billing detail on time entries
For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.
Dockets as well as appointments
Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.
Cost recovery codes
Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.
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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise
Loaded data is not yet a working system. This is what NewLaw sets up in SurePoint Finance Enterprise, beyond the migration, so that people can work in it from the first day.
The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.
Set-up decisions in SurePoint Finance Enterprise
- Entity structure, tax IDs and the chart of accounts
- Bank and trust accounts with reconciliation set-up
- Timekeeper rates, classifications and task code sets
- Pre-bill approval steps and client billing rules
- LEDES e-billing formats for each corporate client
- Management and compensation reports the partners use
Questions
Pika CMS to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Pika CMS before the plan is fixed. Documents that have no place in SurePoint Finance Enterprise are exported into folders by client and matter.
Does everything in Pika CMS have a place in SurePoint Finance Enterprise?
Most of it does on paper. Documents, emails, notes, tasks, custom fields, templates and intake records 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise?
Documents, emails, notes, tasks, custom fields, templates and intake records 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 SurePoint Finance Enterprise
Other destinations from Pika CMS
Other systems that move into SurePoint Finance Enterprise
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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.
Moving from Pika CMS to SurePoint Finance Enterprise?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.