Data migration route
Pika CMS to Sync.com migration
Pika CMS is a case management system for legal aid work, and Sync.com is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
- Documents: Carried across
- Notes: Carried with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
Sync.comCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 1 mapped
- 3 to confirm
- 6 archived
What moves
What moves from Pika CMS to Sync.com
Each row is a kind of record Pika CMS holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, six kinds have no place in Sync.com and are archived 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. | No placeA matter is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldClients, opposing parties and other contacts linked to cases. | No place | Kept as a readable archive |
| 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 placeFiles and folders within the path limit; some file types are skipped by the apps. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldAppointments and dated reminders. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, which are reminders with a due date. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimeslips recorded against cases. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmedOpen-source code that a program could extend; confirmed per installation. | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as ordinary files. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake with eligibility screening comes before a case is opened. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against Pika CMS.
- Carried with mapping
- Sync.com 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
- Sync.com 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Pika CMS into Sync.com means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Sync.com does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Pika CMS.
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. Sync.com 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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Pika CMS holds and how it is organised, then agree with you where each kind of record will sit in Sync.com. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Sync.com 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.
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
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 Sync.com. 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
Structure, permissions and handover
Sync.com is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
Pika CMS to Sync.com: 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 Sync.com?
Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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 Sync.com has no place for?
On this route that is matters, contacts, calendar entries, tasks, 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 Sync.com?
Notes 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Pika CMS and into Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Pika CMS to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.