Data migration route
Open Case Management (OCM) to Litify migration
Open Case Management (OCM) is a server-based case management system for legal aid work, and Litify 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
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
LitifyCloud- 7 carried
- 2 mapped
- 2 to confirm
What moves
What moves from Open Case Management (OCM) to Litify
Each row is a kind of record Open Case Management (OCM) holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, two kinds need mapping and two kinds are confirmed in the analysis.
| Record | In Open Case Management (OCM) | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, each started from an intake. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, adverse parties and contacts on every case, with duplicate merging. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldUploaded files indexed for search, including PDFs and WordPerfect documents. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldShared calendars with iCal feeds. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimeslips on every case. | Has a placeTime entries on the matter. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields, HTML fields and editable menus. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldForm letters and generated documents using configurable template tags. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake with financial and citizenship eligibility, conflict and duplicate checks. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Open Case Management (OCM).
- Carried with mapping
- Litify 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. Open Case Management (OCM) and Litify 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 Litify, 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.
Open Case Management (OCM) 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. Litify 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 Open Case Management (OCM)
Where OCM is self-hosted, the database and the uploaded files are on a server the program or its host controls. That makes collection simple and makes the mapping the real work. The records were designed for legal aid reporting: intakes that may never become cases, eligibility answers, timeslips and the codes that funders count. Each needs a place or a decision.
Intakes that never became cases
An intake is started, screened for financial and citizenship eligibility, checked for conflicts and duplicates, then reviewed and assigned. Many stop before a case is opened. Those records still matter, because a person turned away last year is a conflict check hit this year. They are loaded as contacts with a note, or as closed enquiries.
WordPerfect files in the store
Uploaded documents are indexed for search, and the project documents support for WordPerfect files as well as PDFs. Programs that have run for decades often have both. Files move in their original format. Whether the new system can preview or search a WordPerfect document is tested in the trial load, not assumed.
Menus the program edited
Menus, custom fields and HTML fields can all be changed by the program, so the values on a case come from lists that are local to that site. Every list is exported with its codes and labels. Retired values that still appear on old cases are kept, since deleting them would blank the field on those records.
MegaReport queries
Staff build their own ad hoc reports with a tool called MegaReport, alongside the built-in reports and LSC case service reporting. Saved queries are not data and do not migrate. The ones still used are listed, and each is either rebuilt in the new system or replaced by an export the program can run itself.
Peer transfers between programs
Cases can be transferred to a peer program running the same software. A transferred case has a history that began somewhere else. These are identified in the analysis so that the originating program, the transfer date and any documents that arrived with the case are preserved on the record.
Where it is going
Arriving in Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Open Case Management (OCM) and checking each trial against Open Case Management (OCM).
Analysis
We read what Open Case Management (OCM) holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Open Case Management (OCM), before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Litify as a trial and checked against Open Case Management (OCM): record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Open Case Management (OCM) are frozen for an agreed window, the data is collected a final time and Litify 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 Open Case Management (OCM) as at the cutover date. Open Case Management (OCM) 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 Open Case Management (OCM) 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 Open Case Management (OCM) holds
What is in it, how its records link, and where each piece would sit in Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Open Case Management (OCM) to Litify: what firms ask
We run OCM on our own server. Does that make moving easier?
It makes getting the data out easier, because the database and the uploaded files are under the program’s control and can be copied in full. It does not shorten the mapping or the checking. A complete copy is taken for the trial load, and a second one at cutover after changes are frozen.
We are told OCM has been renamed. Does that force a move?
No one has to move because of a name. The open-source code is still published and receives security and bug fixes, and the commercial version continues as Ciprocity. Whether and when to move is the program’s own decision. If a move is planned, the installed version is identified first.
What happens to closed cases and old intakes?
Both are normally brought across. Legal aid programs rely on old records for conflict checks and funder audits, so leaving them behind saves little. If volume is a concern, the names and case numbers are loaded for every record and the full detail only from a chosen year onwards, with the remainder kept read only.
Do documents from Open Case Management (OCM) keep their folders and dates in Litify?
Litify stores documents. Loaded to the document component and attached to matters. 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 Open Case Management (OCM) have a place in Litify?
Most of it does on paper. Emails and notes 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Open Case Management (OCM) data is loaded into Litify?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and notes 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 Open Case Management (OCM) and into Litify
Other destinations from Open Case Management (OCM)
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.
Open Case Management (OCM) and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Open Case Management (OCM) to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.