Data migration route
Ciprocity data to Full data export
Ciprocity is a cloud case management system for legal aid work, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Ciprocity holds and keeps it readable and open to queries.
- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported with mapping
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
Full data exportFiles- 8 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Ciprocity to Full data export
Each row is a kind of record Ciprocity holds, whether Full data export has a place for it, and what is planned. On this route eight kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.
| Record | In Ciprocity | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases with problem codes, funding codes, assignments, closing codes and outcomes. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldOne contact can appear on many cases in different roles; aliases are kept. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldA documents browser on each case, with OCR run on scanned uploads. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | Held in partInbound email from staff accounts threads into the case; SMS messages are kept too. | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes are one kind of activity on the case. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldAppointments and ticklers on a shared calendar, with iCal and Office 365 sync. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, and workflow rules that create them. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime slips with activity type and funding source; optional supervisor approval. | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partNo client invoicing described; a grants manager keeps funder ledgers. | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeA trust transactions table; ledger reports can be kept as PDF beside it. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a place in partJournals and account balances, where the source held a general ledger. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and case tabs built by the program’s administrator. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly from .docx and RTF templates, form letters and docassemble. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldPrescreen, eligibility against poverty guidelines, duplicate and conflict checks. | Has a place in partAn enquiries table, where the source tracked leads. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against Ciprocity.
- Exported with mapping
- Full data export 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
Not a new system. A complete copy the firm can query.
Writing Ciprocity out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Ciprocity as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Ciprocity is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Ciprocity will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Ciprocity
Ciprocity gives each program its own instance and database, so the data to be moved belongs to one customer and nobody else’s is mixed in. The record design is specific to legal aid. People are contacts with roles on cases, work is a single stream of activities, and nearly everything is coded for a funder. A destination outside legal aid needs most of that translated.
Roles belong to the case
A contact holds the name, phone and address. Whether that person is the client, the opposing party or opposing counsel is recorded on the case, and one contact can hold different roles on different cases. Systems that file a contact as a client or as an other party need a rule for people who have been both.
One stream of activities
Notes, time slips, ticklers and appointments are all activities and share one history on the case. A destination system will split them into file notes, time entries, tasks and calendar events. Each activity type is mapped separately, and the trial load is checked by counting each type per case, not just the total.
Closed means a date
A case counts as closed when Date Closed is filled in, and closing also records a closing code and an outcome. Changing the status alone does not close it. Cases with a closed-looking status and no date are found in the analysis and put right, or they will arrive in the new system as open work.
Three assignment slots
Each case has a Primary Counsel, a co-counsel and a third assignee that is labelled Case Manager unless the program renamed it. Pro bono attorneys and referral recipients can also be recorded. A destination with one responsible lawyer per matter needs somewhere for the others, usually as related staff or a custom field.
Locked and approved time
Older time periods are locked so that months already reported to funders stay closed, and where approval is used, approved entries cannot be edited in the ordinary way. That state is part of the record. Time is loaded with its funding source and its approval status so a past grant report can be matched to the hours behind it.
Where it is going
Arriving in Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Ciprocity holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Ciprocity holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against Ciprocity: record counts, totals where Ciprocity holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Ciprocity, the export is run a final time and checked again. There is nothing to go live. Ciprocity is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Ciprocity 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 Ciprocity holds
What is in it, how its records link, and where each piece would sit in Full data export. 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
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
Ciprocity to Full data export: what firms ask
Our contacts appear on dozens of cases. Will they be duplicated?
They should arrive once each. A Ciprocity contact is a single record linked to every case it has a role on, so the load creates the contact first and then the links. Duplicates that already exist are a separate matter. A merge pass before extraction is worthwhile for those.
Can ethical walls be carried across?
The walls themselves are a security setting in Ciprocity and cannot be copied into another product. The list of who is walled off from which case can be. It is extracted with the cases and used to set restrictions in the new system before any user logs in, then tested with an account that should be blocked.
What about the HUD, VAWA and immigration modules?
These are optional modules with their own fields and reports, switched on per program. Their data sits on the case and is moved as fields. The reporting they produce, such as HUD 9902 submissions, is a function of the software. If the destination cannot produce it, that reporting needs another home before cutover.
Does the copy in Full data export hold trust ledgers from Ciprocity?
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 Ciprocity before the plan is fixed.
Does everything in Ciprocity have a place in Full data export?
Most of it does on paper. Trust ledgers and the firm’s accounts 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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before Ciprocity is written out to Full data export?
Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. Trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Ciprocity and into Full data export
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.
Ciprocity and Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Ciprocity to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.