Data migration route
Ciprocity to Gladiate migration
Ciprocity is a cloud case management system for legal aid work. Gladiate is a case management system for personal injury work, run the same way. 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
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
GladiateCloud- 6 carried
- 1 mapped
- 7 to confirm
What moves
What moves from Ciprocity to Gladiate
Each row is a kind of record Ciprocity holds, whether Gladiate has a place for it, and what is planned. On this route six kinds of record carry across, one kind needs mapping and seven 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 placePersonal injury cases. | Carried across |
| ContactsClients, other parties and referrers | HeldOne contact can appear on many cases in different roles; aliases are kept. | Has a placeClients, leads and referral sources. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldA documents browser on each case, with OCR run on scanned uploads. | Has a placeFiled to the firm’s folder structure. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partInbound email from staff accounts threads into the case; SMS messages are kept too. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldNotes are one kind of activity on the case. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldAppointments and ticklers on a shared calendar, with iCal and Office 365 sync. | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers, and workflow rules that create them. | Has a placeTasks and task plans. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime slips with activity type and funding source; optional supervisor approval. | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | Held in partNo client invoicing described; a grants manager keeps funder ledgers. | To be confirmed | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and case tabs built by the program’s administrator. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly from .docx and RTF templates, form letters and docassemble. | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldPrescreen, eligibility against poverty guidelines, duplicate and conflict checks. | Has a placeLeads and client sign-up. | Carried across |
What the plans mean
- Carried across
- Gladiate has a place for this kind of record. It is loaded there and checked against Ciprocity.
- Carried with mapping
- Gladiate 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. Ciprocity and Gladiate 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 Gladiate, 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Ciprocity depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Ciprocity is kept running until the checks on Gladiate are finished.
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 Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.
Analysis
We read what Ciprocity holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. 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 Gladiate and checked against Ciprocity: 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
After a short freeze on changes in Ciprocity, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Ciprocity 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 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 Gladiate. 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 Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
Ciprocity to Gladiate: 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.
Do trust balances in Ciprocity have a place in Gladiate?
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. If Gladiate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Ciprocity have a place in Gladiate?
Most of it does on paper. Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 Gladiate is kept as a readable archive, and you see which before the move.
What has to be decided before Ciprocity data is loaded into Gladiate?
Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 Ciprocity and into Gladiate
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 Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from Ciprocity to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.